Implementing DNS-over-HTTPS in javascript so my web app can request resolution from its own resolver directly and it can’t be blocked by your adblockers

@wxcafe *adds this toot to the reasons why he wants to stop doing web dev*

@codl half convinced it was the main motivation behind doh in the first place tbh

@wxcafe i don't see why they'd need it to be a standard to do this

@codl easier to do it once it’s running everywhere and there’s no way to block it without breaking everything I guess? Also like with every open source thing, if it’s a standard you can offload the code development costs

@wxcafe in-browser ad blockers can and would block every open DoH resolver

@codl well what if I, youtube.con, refuse to work until I can resolve my ad network over doh? Currently I can’t because it might just be that your resolver is shit and actually can’t resolve the ad network but over doh? If I can’t speak to my resolver I know it’s because you’re blocking it

@codl idk I mean there’s probably ways to block it that would work but it’s another step in the race towards making it more difficult I guess

@wxcafe i'm confused now. i thought you were saying that it was unblockable because there would be a lot of random 3rd party resolvers

youtube is a bad example because the same company runs the website and the ad network, they already know very well if you're blocking ads

but also there's no reason to assume that if you can't reach a DoH server it's because it was blocked. dns isn't the only protocol that can fail in poor network conditions

@codl im not convinced of that honestly. like before it could be that someone up in the chain was blocking port 53, but now it definitely can't be because it's just https so it has to be the user who's blocking it, and the web app can just refuse to work

I'm not really talking about the number of 3rd party resolvers, more the fact that right now if a web app starts talking dns it's trivial to block I guess

@wxcafe who.. blocks port 53.. also how does someone manage to resolve a website fine if port 53 is blocked

@codl lots of people block port 53 at the border (i.e. only a specific (filtered) resolver is allowed to dns out of the network)

@wxcafe oh

wait you meant if a web app used a custom resolver? they can't do that

@wxcafe right. but there is no difference between a web page talking DoH to its special resolver and a web page asking its server "hey, which ip is the ad server at" without a standard protocol. it's not like DoH is enabling a new thing, unless you also assume that most open DoH resolvers won't be blocked in ublock and others

@codl well the difference is I don't have to dev both the server part and the client part because they're standards so there already are libraries for both I guess

@wxcafe honestly today it's easier to make a scrappy web service that spits out a hard coded ip address than to set up one of the standard compliant DoH resolvers. but fair enough


great, now you have to patent it and charge billions of dollars for it so no one uses it

@wxcafe hmm, I’m not sure if you can connect to an IP and set the Host header from a client-side request… but this is an evil plan and I love it

@ticky if you can't now you probably will be able to in a javascript framework 6 months from now

@ticky @wxcafe well you couldn't do that in JS code in a regular webpage but i'm willing to bet you could do that in a WebExtension :thinkhappy:

@Eramdam @wxcafe please instal this extension to by pass your ad blocker plugin or we can’t show this web page 🙏🏼

@ticky @wxcafe
Please install this extension for exclusive bonuses and goodies and features*

* ᴅᴏɴ'ᴛ ᴡᴏʀʀʏ ᴀʙᴏᴜᴛ ᴛʜᴇ ʙʀᴏᴀᴅ ᴘᴇʀᴍɪꜱꜱɪᴏɴꜱ, ᴡᴇ'ʀᴇ ɴᴏᴛ ᴇᴠɪʟ, ᴘʀᴏᴍɪꜱᴇ

Sign in to participate in the conversation

This is a mastodon instance for social justice activists, LGBTQIA+ people, and activists in general See the Goals and technical details, and Rules and privacy policy pages for more information