hey @Mozilla is it normal for @firefox to connect to these 16 hosts when i merely launch it?
is there any easy way to make @firefox only connect to the hosts i actually want it to?
@jz @Mozilla that #DRM thing is really unfortunate. But it was a w3c decision, so this bad thing had been standardised. And of Mozilla would not have implemented it, they would now have probably -20% market share/users, because everyone who wants to use #netflix would immediately switch to another browser.
@rugk @jz @Mozilla That is wrong. W3C, but in fact more probably WHATWG at first, has made a standard how to operate DRM. You can implement this code with no DRM problem. To finally read DRM content, you need a bit more, and that is the DRM code, that must be proprietary to be "efficient". Firefox uses Adobe stuff and Google Widevine, without this the web standard is not enough to read real DRM content foundable on the Web.
The reality is just people want to "read" DRM and w3c or okay whatwg paved the way. EFF e.g. criticized it and left the w3c or whatwg (don't remember which):
And Firefox also uses Googles #Widevine FYI.
@hyde_stevenson @jz @Mozilla If you want alternative browsers, I'm working on a couple ("Odysseus" and "Rhapsode") and I'm also aware of:
* Epiphany/GNOME Web (WebKitGTK)
* Midori (WebKitGTK)
* Dillo (custom FLTK engine)
* NetSurf (custom engine)
And I must say for captive portals and software updates at least, I prefer leaving that to the OS rather than applications.
Google safe browsing is also in there, so you can explain that too.
Telemetry etc. can e.g. also be disabled in the settings.
@jz @Mozilla I think it is really unfair. There are things like captive portal detection, the H264 plugin updating itself or Safebrowsing. Most users probably want those features. They don't seem to be used for tracking.
Please understand that many programs need to connect to many different hosts to work correctly and that isn't used for tracking purposes nor for delivering backdoors, etc.
Please understand that not everybody is happy with the browser connecting willy-nilly to random stuff without the user's consent or knowledge.
Where to connect and when should be part of the onboarding process on installation or first launch.
We're not doing users any favours by conditioning their behaviour in negative ways.
I know what most of those are, but still not happy about shit connecting to stuff I didn't ask it to connect to.
Yes, I disable "safe browsing" *and* update checks.
@jz @Mozilla Sadly this kind of thing is not new: https://framasphere.org/posts/f977a980c65f013517542a0000053625 (french) I guess GNU IceCat and the fork by Trisquel GNU/Linux are less worse. There is of course also the Tor Browser that I hope they removed nasty things. There is also the solution to use simple text browser, it limits websites, but it is efficient and consume far less resources. There are also some web browsers that use other engines, but not sure for security as "modern" web engines are so enormous and often fixed.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!