Rich Felker@MMRnmd @nixCraft The alternative is just turning it off (or rather, leaving it off/not responding to the nag to turn it on in the official FF binary).
It's really harmful to the ecosystem that this is not explained clearly every time Mozilla does something stupid like this.
It ends up driving people to Chrome & Chrome reskins where, unlike with Firefox, you *can't* just turn-off/leave-off the misfeatures.
All GNU social JP content and data are available under the