I know it doesn't break EVERY customisation available, because I used it the Australis Nightly with addons. But in regards to the theme... and? Anytime ANY piece of software that allows themes makes ANY changes it has the possibility to break existing themes. That's been known since forever, and Firefox is no different.
Originally Posted by JX8p
If the theme is unmaintained then you had to know that eventually it would stop working, well now's that time.
If the theme IS maintained then shame on the developer of that theme for not making an Australis version. This wasn't a big 'shock' change, this has been known about MONTHS and has been able to be played around with since last year. Hell, they even made special versions of the nightlies available last year that were current-nightly + australis so that those who were interested, and developers, could start playing around with it and figuring it out.
Blocking plugin enumeration is major plus
Preventing websites from being able to enumerate plugins denies malicious "browser fingerprinters" a key piece of information used to track you even after you toss your cookies and your Flash cookies. I've taken to keeping all plugins disabled and turning them on only to actually use them to limit fingerprintablity. I will test this against Panoptickick when Firefox 29 has been out long enough to prevent the useragent from coming up as rare.
Note that now sites can't enumerate (ie list) every plugin installed, but they still can query for specific plugins and their version. So this would help with fingerprinting only if you have some non-common plugin installed.
Originally Posted by Luke
I'd expect sites like panopticlick to just get an huge list of existing plugins. In fact, they probably have one already, since they can just get it from browsers that allow fingerprinting.
This means plugins should still be disabled except when actually used
Thanks for the update. There are certain other considerations in masking a browser: First of all, if you use the common tactic of having a browser report it is running under Windows, be sure not to allow ANY plugins and not to use Gstreamer for HTML5 video playback unless Firefox does not report how it plays back HTML5. I do not know if Firefox will identify the backend used for HTML5 playback right now, so I let it report that it is running under Linux. Torbrowser reports itself as Windows, the useragent comes up as matching that of one in 155 browsers. Firefox on Ubuntu by default comes up with a useragent string matching one in 885, still not very unique by itself, but there's a lot more information to worry about. Plugins, fonts, and HTTP accept headers are the worst culprits.
Originally Posted by Spittie
Fonts are greatly reduced as a fingerprintable item when Java is not installed and Flash is kept disabled until it has to be used.
I take it back.
Originally Posted by Ferdinand
I am running a ton of tabs (multiple hundreds) and the memory use generally tends to hover around the same amount.
However, i noticed that closing a few tabs i have brought the total back down to only about +5-10%, which is probably within the margin of error.
So i think i just happened to have a few extra busy tabs open causing most of what i saw.