5/25/2026 at 6:33:54 PM
it should probably link to this: https://mullvad.net/en/blog/exit-ip-fingerprinting-between-v...which is the blog post, rather than a list of exit servers
related to this post: https://news.ycombinator.com/item?id=48143880
by john_strinlai
5/25/2026 at 8:48:55 PM
That blog post is a perfect example of when RFC5737 should be used.by Arrowmaster
5/26/2026 at 5:20:35 AM
Nice. But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples. One of those "standards" that have been a great idea, but lack practical relevance.by usr1106
5/26/2026 at 3:44:47 PM
> But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples.How does that matter? The point isn't that the reader should know that "oh, this is a reserved address". The point is that there should be no room for the address that's actually being used by someone to end up being used incorrectly just because it showed up in some random documentation.
Much like how you probably wouldn't be thrilled if your phone number was used as an example in some random documentation somewhere.
by scbrg
5/26/2026 at 5:53:39 AM
> But unfortunately these addresses are hard to remember and "nobody" recognizes them when reading examples.Mmm.
It's pretty easy to put three IPv4 /24s on a sticky note on your monitor. I think it's not unfair to say that if one can remember every fact related to one's job, then one has a job with a very, very small scope.
Also, this is another great reason to use IPv6. The v6 documentation prefix is '2001:db8::/32'... plenty of space for example subnets and easy to remember.
by simoncion
5/26/2026 at 10:25:46 AM
For me it's the opposite: I usually misremember 192.0.0.0/8 as being entirely private, so for 192.0.2.0/32, I usually assume that the example given is supposed to be a private v4 address/network.by lxgr
5/26/2026 at 8:16:18 AM
Anyone who writes technical documentation about networking knows the key ranges, and at least TEST-NET-1 (192.0.2/24) is pretty easy to remember. You only gotta look it up a few times, instead of being sloppy and justifying so with “no one cares anyway”.It partly because attitudes like that is why software is a mess. Too few people care about correct semantics, everyone is satisfied with whatever sticks. From lists for sets, to tag soup instead of markup, and so on - all the way to modern code slop.
</rant>
by drdaeman
5/25/2026 at 9:14:46 PM
On a side note, buttons icons on this page won't load without javascript. I cannot comprehend what would justify such decision.by Insimwytim
5/25/2026 at 9:46:14 PM
Without justifying it, the reason is simple. They are using a front end framework (bootstrap) that many developers use/understand that also supports 99.9% of browsers.Running a browser without javascript that you still want graphics to display (so not a screenreader or text-based-browser), is part of the .1% they are willing to disappoint.
Do I think it is overkill? Sure. Do I still use jQuery at work even though the vast majority of its once handy features are now baked into JS in the browser by default? Of course.
by jermaustin1
5/26/2026 at 4:33:55 AM
How do you jump straight from JS to screen reader or text based browser? What happened to HTML+CSS viewer? Isn't reading an RFC the perfect poster child for an activity that ought to consist of viewing a noninteractive document?by fc417fc802
5/27/2026 at 6:43:36 AM
> What happened to HTML+CSS viewer?S in https stands for "script". /s
by hulitu
5/25/2026 at 11:40:04 PM
It’ll be a run-on effect of whatever framework they are using, and they very justifiably don’t want to bother catering to you. Having JS disabled in 2026 and complaining about sites not behaving is simply a performative act.by UqWBcuFx6NV4r
5/26/2026 at 12:45:15 PM
2015: It's a SPA blog because my employer forced me to do it that way, I didn't want it.2026: It's a SPA blog because I very justifiably don't want to bother catering to you. Having JS disabled in 2026 and complaining about sites not behaving is simply a performative act.
by GoblinSlayer
5/26/2026 at 1:34:24 AM
It’s basic self defense. Who runs around the web in 2026 allowing random JS? Might as well be licking seats on the subway.by lazide
5/26/2026 at 9:13:19 AM
> Who runs around the web in 2026 allowing random JS?Within a rounding error, 100% of people on the internet.
by Telaneo
5/26/2026 at 7:11:49 PM
It’s a lot higher pct when you count vpns with JS filtering, ad blockers, etc.by lazide
5/27/2026 at 12:33:34 AM
Even then, they're using disallow lists. If you go on a random web page with novel JS, then that'll still be run.The only people working of allow lists are the people running NoScript and the like, and those truly aren't running random JS. But those people are a rounding error compared to the greater internet.
by Telaneo
5/26/2026 at 2:02:13 AM
If you trust your browser it's fine, and if you don't then both CSS and SVG are significantly more risky.by lmm
5/26/2026 at 4:07:43 AM
This isn't true at all.Anything SVG does maliciously, it does by containing JavaScript, so SVG's worst case is a subset of JS's.
by margalabargala
5/26/2026 at 4:30:54 AM
Remind me again what the ratio of browser sandbox escapes coupled with full RCE is between JS, CSS, and SVG?by fc417fc802
5/26/2026 at 2:16:01 AM
> then both CSS and SVG are significantly more risky.how???
by sysguest
5/26/2026 at 6:00:17 AM
>and they very justifiably don’t want to bother catering to youConsidering they are one of the very few sites and VPNs that allow sign up without JS your claim is verifiably false. They also collaborate with and develop there own tor browser fork which has the highest rate of non JS user.
by akimbostrawman
5/26/2026 at 12:30:24 AM
[flagged]by sroussey
5/26/2026 at 8:27:07 AM
What "buttons icons"? When I set the "javascript.enabled" preference in Firefox 151 to "false" and reload the page for RFC 5737, I get a "Javascript disabled? Blah blah blah blah." complaint near the top of the page. I do not get* the useless-to-me "document history" bar graph at the top
* the automatic switch to Dark Mode(TM) that I don't care about
* functional pull down menus at the very tippy top of the page that are entirely unrelated to RFCs that I give zero shits about
The "without javascript" version of the page seems to me to be otherwise identical. Amusingly, the "Email authors", "IPR", & etc buttons switch to the pages they reference notably faster with Javascript disabled.
What broken things were you seeing that I haven't mentioned? Were you using Chrom(e|ium)? Safari?
by simoncion
5/26/2026 at 3:57:04 PM
> I set the "javascript.enabled" preference in Firefox 151 to "false" and reload the pageDo it the other way around - disable javascript first, clear cache/open incognito (maybe close/open browser after that just for good measure), then go to the page.
If you load it with javascript first - buttons icons stay loaded after you disable it.
by Insimwytim
5/27/2026 at 5:29:14 AM
The only thing that I don't do in Firefox's "Private Browsing" mode is play a handful of stupid little in-browser games that save progress in a cookie or whatever. I even have Firefox set up to open in "Private Browsing" by default. Here's what I did just now:1) Quit Firefox
2) Opened Firefox
3) Visited 'about:config'
4) Set 'javascript.enabled' to 'false'
5) Quit Firefox
6) Opened Firefox
7) Re-visited 'about:config' and verified that 'javascript.enabled' is still set to 'false'
8) Visited <https://datatracker.ietf.org/doc/rfc5737/>
It's still exactly like I reported it was. The "Manage browsing data" thing accessed through Firefox's regular settings dialog doesn't indicate that there is any data saved by any ietf.org subdomain, and when I watch the Network pane, a ctrl+shift+f5 reload of the RFC5737 page indicates that the page loads everything from an ietf.org subdomain... so the saved resources from one of the like eight domains in that list aren't relevant.
by simoncion
5/28/2026 at 9:46:16 PM
Fascinating.I use NoScript, not 'javascript.enabled' setting.
I checked more closely and here is what appears to be missing:
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://static.ietf.org/dt/12.65.2/ietf/bootstrap-icons.5b9cac4e.woff. (Reason: CORS request did not succeed). Status code: (null).
Bootstrap icons. Block javascript - icons won't load.
Allow javascript - icons load.
Block javascript again - icons load, unless tab is closed and then opened again.
This behavior has been observed previously.I tried to selectively block css to see how it's tied to javascript.
Block javascript, block css from static.ietf.org - icons won't load, page layout is broken.
Allow javascript, block css from static.ietf.org - the icons won't load, layout is fine.
Evidently, with javascript blocked, layout css loads fine, but bootstrap icons only able to load when javascript is not blocked.'javascript.enabled' setting seem to has no effect on icons. However, unlike NoScript, it does not provide any domain separation/granularity.
by Insimwytim
5/26/2026 at 4:03:39 AM
Are you in 2006 or 2026?by ernsheong
5/25/2026 at 7:03:06 PM
The page already contains link to both of these resourcesby opem
5/25/2026 at 7:26:06 PM
right. but one of those resources contains much more context than the other, making it much more suitable for the submission link.by john_strinlai
5/26/2026 at 8:35:24 AM
The post you preferred was submitted before. And had not much new information. The rollout was the news. The link was correct.by pseudalopex