Default Privacy Settings in Abrowser
As has been discuessed on other forum topics there is a file under /usr/lib/abrowser/browser/defaults/preferences/vendor-abrowser.js
This file changes default settings in abrowser such as privacy and UI settings. It seems like many of the privacy settings that are altered using this file cause issues with a fair amount of issues with different web sites.
If you're a technical person you can go into the abrowser settings or even into this file and make the changes that are negatively affecting the site you're trying to use. If you're not a technical user you are left thinking that abrowser isn't working or is a piece of junk.
I suggest that instead of making the changes quietly through this file why can't we do an extension instead? This extension could activate all of the settings that help protect privacy and make the user aware that it's on and it can cause problems with sites, but then allow them to turn it off when wanted/needed.
This is done by some helpful checkboxes in about:icecat , the default homepage in Icecat. Which if what jxself and others have said here is true, is to be the default browser in Trisquel 7.0.
According to Ruben himself earlier on Reddit, abrowser will still be the default browser - Icecat will be in the repo as an alternative.
I hope he won't mind me quoting his message here:
"Both work around the main problems in Firefox: that it recommends non-free software and that the trademark license restricts distribution for a fee and distribution of modified versions unless the name is changed. Abrowser follows the latest Firefox versions, while IceCat follows the latest ESR (v31 at the moment) version.
Abrowser, other that saner default settings to improve privacy, is pretty much Firefox and should provide a quite "neutral" browsing experience.
IceCat on the other hand includes more aggressive freedom and privacy features:
- LibreJS blocks non-free JS scripts. It is experimental by now, so use it with caution.
- SpyBlock (a customized Adblock) filters any well known privacy trackers, and in private browsing it blocks all third-party requests. Self-served ads should be preserved.
- Https-everywhere redirects you to https versions of websites
- Anti-fingerprinting measures have been set, like spoofing the user-agent, the referrers, and many other details.
Those features provide a much improved privacy, but with a not so neutral browser experience as a tradeoff, meaning that some websites may break or behave weirdly. This will improve when LibreJS gets more stable.
Because of those reasons *Abrowser will be the default browser in Trisquel 7*, while IceCat will be an optional installation available in the repos (also available in T6)."
I think it's a bad decision to maintain both browsers separately.
For those who need 'more aggressive privacy features' it's a piece of cake installing a few addons.
Why is ruben wasting resources like that? Meanwhile the release for belenos takes forever.
"I think it's a bad decision to maintain both browsers separately. For those who need 'more aggressive privacy features' it's a piece of cake installing a few addons."
Not if you knew the entire back story. This is the most optimal decision under the circumstances.
Yeah, then would you mind telling us or is this backstory some kind of secret?
I think it would be easier for people to understand this way.
I'd rather not repeat back channel stuff without the permission of those involved which I don't have and probably won't be able to get. Suffice it to say that the primary intent of my comment was that condemning the decision based only on the surface and when you don't have all of the facts is probably not the best. There are obviously reasons this particular setup was chosen. It's the most optimal setup under the circumstances, and doesn't necessarily result in duplication of effort given the infrastructure that's been made for maintaining the software. :)
Hmm I understand that you can't tell, but again I think it's not a good way to communicate with the userbase - if there is criticism just to state that there is some kind of reason but we won't tell.
I really hope that the whole communication between developer and user will improve in the future.
It's one of trisquel's biggest flaws.
I am a member!
Consider that the person who said it isn't necessarily withholding information. jxself simply doesn't know if it would be alright to release that info. Communications hasn't been the strong point here, but there are some improvements in the new system that should enable people to contribute more easily.
Thanks for the quote, just over two hours old too :). Personally I've found Icecat with both LibreJS and the Anti-Tracking disabled works with one site Abrowser doesn't. But I note the current Abrowser in Belenos betalooks for a nonexistent about:abrowser for its default homepage, so maybe it's going to have something similar. Maybe not obviously, but there's a chance.
The original announcement was that IceCat will replace Abrowser.
I like the checkbox theme Ruben used:
https://upload.wikimedia.org/wikipedia/commons/4/48/GNU_IceCat_31.png
For those wondering if Ruben is really working hard or not:
http://git.savannah.gnu.org/cgit/gnuzilla.git/
About to install Icecat-31.2.0-esr on a couple of Freedom desktops just to check out the performance, one running Debian GNU/kFreeBSD and another with openBSD. Most GNU/Linux test distros require over 70 about:config setting changes to gain an acceptable level of privacy and security with Gecko-based browsers.
BTW, Debian GNU/kFreeBSD runs Xfce-4.10 as the default desktop and doesn't use the Linux kernel. Just pure GNU userland with freeBSD kernel. Ahhh... true Freedom under the WTFPL - wtfpl.net
Live Free & Do Good Things!
Please excuse this for not being 100% on-topic, but it really doesn't need a new thread: I'd just like to say that, despite the extra work involved (thank you!), I am elated to learn that Abrowser will still be with us for several more years. There's something about Abrowser's generic look that appeals to me, especially since Ice Weasel's constant morphing ended up settling with a different elemental mascot. I know and accept that Abrowser will be phased out, eventually, but might it be possible to retain its unique name and icon as an optional package, add-on, or the like?