Haven't you white listed your admin's IP address? If you do you'll notice that it bypasses ALL rules intended to stop hackers.
Your tone is unnecessarily hostile and shows lack of imagination for different needs.
Some of my client's content writers travel and write from the road. A lot are not tech savvy, since their are writers and editors and not web developers.
The fact is, locking out someone for ONE instance of mistyped username, which is what WordFence's current options do, is simply bad design.
WordFence is a great plugin and I don't hesitate to recommend it, but I'm sure they'd want to know of simple ways to make it easier for users to manage their security. And allowing us to specify usernames that are either automatically denied login or blocked on the IP level would not add much at all--it could be one line in a database + a handful of lines in the code--while it would basically make them an almost perfect security plugin.
I have found a balance and have written my own code, but the point is to help WordFence know what users want and to explain different aspects of user needs and real-world use to give the WordFence folks the data to decide whether they want to add/update their features. I don't really understand what your problem is with that.
