Why Privacy+ and BetterPrivacy Don't Delete All LSOs Rated 5 out of 5 stars
What most people, even those writing these add-ons, do not know--or in BetterPrivacy developer's case, refuse to believe--is that there are two locations (for each user profile on the computer) where Web sites store Flash cookies (LSOs). By default, most LSO removers only check the "#SharedObject" subfolder in Macromedia's "Flash Player" folderWhichever. There is another location in the "Flash Player" folder, "macromedia.com\support\flashplayer\sys", where LSOs are also stored. This also happens to be the location where the Global Settings LSO resides, which was created when you went to Macromedia's Settings page. When someone running Firefox with either BetterPrivacy or Privacy+ visits a site that sets an LSO, the LSO is placed in the folder that BetterPrivacy or Privacy+ are NOT monitoring. BetterPrivacy is set by default to monitor the "#SharedObjects" folder, and I assume that Privacy+ is written to check the same folder. If the preferences are changed to check the #SharedObjects folder, then the LSOs will be placed in the "sys" folder. If it is set to check the "sys" folder, then LSOs will be set in the #SharedObjects folder.
The only way to circumvent that trick is to set BetterPrivacy to monitor the entire Macromedia folder. The problem is that when BetterPrivacy deletes the LSOs, it will also delete the Global Settings LSO placed in the "sys" folder. Also, every Web site that you go to will overwrite your Global Settings LSO and replace it with the settings that the site owner wants you to have. The solution to both problems is simple. Right click the "settings.sol" LSO immediately after configuring your Global Settings on Macromedia's Web page. Click Properties, and then tick the "Read Only" option, making the LSO a Read Only file. That will prevent another Web site from replacing it with their own settings. However, you might find afterward that the site has written a "settings.sxx" file in the "sys" folder or created a subfolder and put its own "settings.sol" file in that subfolder. If you use BetterPrivacy and protect the "sys" folder where the Global Settings LSO is stored, it will also protect any files that a Web site places in that folder. For some strange reason, the developer of BetterPrivacy provided the option to protect the folder instead of the individual file. The result is that the user still has to delete some LSOs by hand. Even unchecking the option "Do not delete Flash player default cookie" does nothing. Even with that option unchecked, BetterPrivacy will still delete the default (Global Settings) LSO. "Protecting" the entire folder combined with making the file "Read Only" is the only solution that actually keeps the Global Settings LSO from being deleted or overwritten.
That's why Privacy+ fails to delete so many LSOs.