The failure that is the selectable of DEFAULT APPLICATION BEHAVIOR panel
Anybody that uses this product and is paying attention over many years knows that the point of departure between a product that was configurable for the benefit of the USER as opposed to the BD usurping real control....knows that the DEFAULT APPLICATION BEHAVIOR panel tells the whole tale.
For years USERS could choose to BE ASKED what to do when a new application was demanding access to the internet. The options were
BLOCK ALL REQUESTS
GRANT ALL REQUEST
ASK ME TO MAKE THE DECISION
A number of years ago BD designers decided the USER would have to live with the idiocy that is the current DEFAULT APPLICATION BEHAVIOR panel. The USERS now have the following choices
AUTOMATIC
BLOCK ALL REQUESTS
GRANT ALL REQUEST
Of which anyone with an IQ over 80 knows, that is really only two (2) choices......BLOCK all requests or leave it up to BD to GRANT all requests or those that that BD thinks is best. The reason for this change is as plain as the nose on your face, just think about it.
And it gets worse than that. If one elects to BLOCK EVERYTHING with the idea that USERS will visit the FIREWALL page and repair those BLOCK EVERYTHING applications that we want to RETURN TO ACCESS, well that has been laid to waste as well. Why? The FIREWALL panel has been bifurcated into two parts.......APPLICATION ACCESS and RULES. That changed harkened the end of any really meaningful or EFFICIENT user control over what gets to the internet without allot of blind digging around. And the USERS? Well BD is really hoping that YOU do not notice.
A common complaint by USERS is that when an alert on the APPLICATION ACCESS panel informs the USER that say your BROWSER has been blocked and the USER says "lets fix that" and opens up that alerts line to get to the now DESTROYED FUNCTIONALITY found in the blue "VIEW APPLICATIONS RULE" that they will be generically dumped into the RULES side. Dumped at the TOP OF THE PAGE and NOT at the specific APPLICATION line in question (heck that line might not ever even be found!) but at the TOP OF THE RULES page.
Bit Defender....This is a terrible design that can only be a massive design mistake or on purpose.
- When APPLICATION ACCESS alerts that access for a particular program is denied TAKE US DIRECTLY TO THAT "denial" line so the USERS can fix it and DO THAT WITHOUT LEAVING the APPLICATION ACCESS side.
- DO not dump us at the top of the RULES page and make us blindly go through the endless inefficient dumping of panels to finally find the REFUSED line. The rules panel is a mess and has been a mess FOR YEARS.
- There is now way to sort all the USERS individual items by DATE, TYPE, ACTION. It is as crude as can be requiring the most inefficient process of dumping arrows all the way down to the actual application that we are working with.
- When we are working to set rules for complicated apps RETURN US THE OUR LAST LOCATION so that we can provide access or deny access WITHOUT STARTING AT....wat for it...selecting the DRIVE LETTER.
- EVERYTHING on the APPLICATIONS SIDE is not available to be denied. It hasn't been for years. IF BD has something that they do not want to be part of the DEFAULT APPLICATION BEHAVIOR electability pool, than state it as such. EVERYTHING else is USER controlled.
- CHANGE BACK TO DEFAULT APPLICATION PANEL THAT ALLOWS US TO BE ===ASKED EVERY TIME A NEW APPLICATION SEEKS INTERNET ACCESS==== AUTOMATIC can disappear unless you want to tell us what that even means.
Users are neither so stupid not to notice these unproductive (at best ) changes nor are we interested in working so hard on rules TO GET TO THE EXACT APPLICATION DESCRIPTION LINE that is at the heart of our CHANGING ACCESS. Its just the opposite, we notice and are growing concerned about the seeming inability to control our own programs access. The whole of DEFAULT APPLICATION BEHAVIOR is a clear and unambiguous view as to the actual respect BD has for USERS interest and ability to make our own decisions on BD.
One of the TOP TEN complete product design failure, this problem needs to actually be fixed... FIX THE DEFAULT APPLICATION BEHAVIOR or have your best spokesperson explain to us all why we, the USERS, cannot be asked to review AND DECIDE each and every request as we did for YEARS.
