Mozilla, don't be evil

Whatever was being passed around at Mozilla Corp when this was considered... It wasn't good shit. Trust me, I'm an expert if it comes to stupid ideas under the influence.

I mean... how stoned do you have to be to think it was a good idea to force users to use ONE single DNS over HTTPS provider, called cloudflare, who has their own agenda...

...consisting of supporting and proudly servicing ponzi operators (JustBeenPaid/Profitclicking/AdClickExpress/whatever their name is now, I stopped my investigation on them in 2013), scammers and other low life scum.

What could go wrong... or rather, what could possibly be imagined to go wrong if you look just an inch further than the tip of your nose?

I guess I'll need to compile FF from source from now, after removing the offending parts, just to make SURE I don't end up at the local "Indefinitely sustainable wealth scheme" instead of devrant.

Step aside coffee, that's a job for beer. Or a blunt.

@dontbeevil

Use Brave. I'll leave that here

#hooli

Can't we set the dns provider ourself?

@dontbeevil

+

@dontbeevil

https://blog.ungleich.ch/en-us/cms/...

@starwatcher nice it can be deactivate.

Mozilla has long been a bunch of assholes making war on their users. Fuckfox. And then these wankers wonder why their user share plummets.

So... Chrome basically doing the same, but with google dns is any better?

I mean... Dns is flawed and there should be some security, but by adding https (and thus tcp) in the mix, directly going to a name server instead of using your local resolver (on your computer) requires quite some bandwith/ressources...

Plus wouldn't that render the hosts file obsolete? Damn, I want to be able to overwrite some domains (like stuff for local dev or to test things before moving a domain...)

I'm out of the loops, what's happening?

.

@Wack are you sure it's gonna override our local hostfile?

@lumy no, but I'm guessing, that it's going to ignore it.

Traditionally an application just queried the local resolver for a dns entry. If instead the app chooses to bypass the local resolver, which checks the host file and otherwise queries the resolver given by the dhcp server or set manually I see no way (unless Firefox reads the hosts file itself) to still preserve this.

Sure they could read it themself but on some installations they might not have rights to read it...

I'm lost

Mozilla tries to add DNS over HTTPS: https://blog.nightly.mozilla.org/20...

Maybe CloudFlare just supports DoH ?

@NotFound Ok, they does