We just didn't want to risk and turn it on by default in the first release.
It is now 2 months since the release and we've got loads of different reports on issues caused by Stealth Mode.
So now we know which stealth mode options are likely to cause troubles.
In the next version we will change some of stealth mode options to fix it.
1. Blocking third party cookies
It may sometimes cause troubles with websites authorization. Especially when the website uses some complex multi-domain authorization.
So, in the next AG version, instead of simply blocking third-party cookies we will introduce a new option: self-destructing cookies. Third party cookies lifetime will be limited by N minutes (user defined, 30 minutes by default).
2. Hiding user agent
We have made a mistake here. By default we use some hard coded user agent of a chromium/linux browser. This may mess with some websites functionality. For instance, when you use IE11 and set this option on, youtube starts complaining on your browser.
Instead of this we should use the user agent of the same browser/OS, but strip it from everything non-standard.
3. Hiding IP address
We now use some hardcoded IP address of some TOR node. This IP address is often blacklisted.
So, we should not use a TOR node IP by default. Also user should be able to set any IP manually.
4. There is no easy way to disable stealth mode only for a website
This is just wrong. There should be an easy way to turn stealth mode off for a website without disabling other modules.
In the next version we will introduce a simple configurable whitelist.