Dear IETF: Are you fucking kidding me?
To get an RFC .txt file I must allow Cloudflare and Google tracking?
Are you serious? This is wrong on all OSI layers!
@MacLemon CloudFlare everywhere!
@lanodan Thanks for sharing. I do have my local RFC backup as well. (Not really current though to be honest.)
Still… the IETF must not block users in any way. (“must not” to be interpreted as defined in RFC 2119.)
@TerrorBite Thanks for the update! :-D
@MacLemon works fine via tor 😉
@M0YNG That connection was via Tor.
@MacLemon hmm, I am using the tor browser, if that helps.
Just tried. No cloudflare, no captcha, just txt (also html). Both Torbrowser and direct without any extra allowance in uMatrix and nothing blocked. No other domain.
Ah true, https connects to 220.127.116.11 which is CLOUDFLARENET
dig www.ietf.org a
IN A 18.104.22.168
@MacLemon I just checked; ftp still works to that address.
(I think that is the only way I have ever read an rfc, to be honest. Well, no, I have read them via links - but always mirrored, I believe. I believe the only way I've gone to the ietf website was via ftp. Thus my concern: was my traditional method now not working? And, no, it still does.)
@laggard You may want to check to whose IPs that hostname resolves to…
@epi I don't mind them using a CDN, but I do mind them blocking legitimate requests via their CDN.
chaos.social – a Fediverse instance for & by the Chaos community