Why did they take about:config from us?
Why did they take about:config from us?
Looks like they ran out of space on their build machine.
Having WebRTC enabled can be dangerous for other reasons. You could be seeding a torrent unknowingly just by visiting a website. This can turn into a freaking disaster if you live in country like Germany.
It's a shame that browsers don't ask you for WebRTC like they do with webcams.
Only to a webserver and thanks to CORS not to any webserver. There is no benefit for a website doing that - unlike with sharing a torrent to other internet users.
The problem with torrents is that they are actively watched by "Abmahnanwälte" (lawyers who make a living by suing copyright offenders).
> And it's going to be hard to hold you liable for data uploads that someone else initiated and you didn't know about
yeah good luck with that. All they see is your IP and then you can try to explain how this happened and how you are totally innocent.
What do you mean? I'm running the latest firefox nightly from the play store and I can see the about:config...
They took it away in Stable because changing some settings may disconnect GeckoView from the application containing it and they can't have that.
I run Beta for this reason. Nightly is too unstable for me so I had to give up custom addon lists to bypass Mozilla's outdated whitelist (they were only available in nightly for a while, I believe that's in Beta now).
Mozilla doesn't trust you to use their precious software right and they'll take away your toys if it considers you to be playing with them wrong. I still like Mozilla over Google, Microsoft, and Apple, but it's really hard to be a fan of Firefox when they pull shit like this.