Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

A Readable Specification of TLS 1.3

davidwong.fr

Post reply on HN
Print view View original

21–27 of 27 posts

Re: A Readable Specification of TLS 1.3

#21

Post by reeeeee »

southerntofu wrote: post #17

Seriously, when will people stop using some cyberfascist firewall like Cloudflare? Usually it's only companies doing shit like that but here on HN i see a number of personal blogs hidden behind Recaptcha. Do you realize that makes your websites actually UNUSABLE by many people ? Don't have Javascript? Go fuck yourself. Using tor? Go fuck yourself. Scrapping the HTML to produce some nice indieweb interaction on your o…

Why is CloudFlare a cyberfascist firewall? If it is because you refuse to use JS? well too bad for you.

CloudFlare takes a strong position on freedom, and I admire them for it: https://www.wired.com/story/free-speech-issue-cloudflare/

Re: A Readable Specification of TLS 1.3

#22

Post by yosamino »

reeeeee wrote: post #21
southerntofu wrote: post #17

Seriously, when will people stop using some cyberfascist firewall like Cloudflare? Usually it's only companies doing shit like that but here on HN i see a number of personal blogs hidden behind Recaptcha. Do you realize that makes your websites actually UNUSABLE by many people ? Don't have Javascript? Go fuck yourself. Using tor? Go fuck yourself. Scrapping the HTML to produce some nice indieweb interaction on your o…

Why is CloudFlare a cyberfascist firewall? If it is because you refuse to use JS? well too bad for you. CloudFlare takes a strong position on freedom, and I admire them for it: https://www.wired.com/story/free-speech-issue-cloudflare/

Harbouring, enabling and protecting criminals is not "a strong position on freedom" - try to report a scamming site to them and see how they deal with it. Spoiler: They will not, and because it's behind their firewall, you'll be unable to find out who else to send an abuse complaint to.

Re: A Readable Specification of TLS 1.3

#23

Post by tgragnato »

lol768 wrote: post #20
southerntofu wrote: post #17

Seriously, when will people stop using some cyberfascist firewall like Cloudflare? Usually it's only companies doing shit like that but here on HN i see a number of personal blogs hidden behind Recaptcha. Do you realize that makes your websites actually UNUSABLE by many people ? Don't have Javascript? Go fuck yourself. Using tor? Go fuck yourself. Scrapping the HTML to produce some nice indieweb interaction on your o…

What's the alternative if you want to be able to handle DDoS attacks? Something like OVH's VAC?

Isn’t the main feature for blogs on Cloudflare the free global CDN cache?

Re: A Readable Specification of TLS 1.3

#24

Post by crispyambulance »

I'll never understand why rfc's, arguably the underpinnings of internet technology, are styled to appear as TYPEWRITTEN pages in HTML. Seriously. Literal pages of typewritten text, on the web.

I mean, they take significant effort to devise these standards and write them up, presumably with modern tools, AND THEN force weird typewriter CSS upon them? It looks awful. I can't understand it.

Re: A Readable Specification of TLS 1.3

#25

Post by bonyt »

crispyambulance wrote: post #24

I'll never understand why rfc's, arguably the underpinnings of internet technology, are styled to appear as TYPEWRITTEN pages in HTML. Seriously. Literal pages of typewritten text, on the web. I mean, they take significant effort to devise these standards and write them up, presumably with modern tools, AND THEN force weird typewriter CSS upon them? It looks awful. I can't understand it.

I assume this is because they’re published as plain text files. The HTML is styled to look the same as the plain text versions, including diagrams made assuming a fixed-width font.

https://tools.ietf.org/rfc/rfc793.txt

Plain ASCII text is a very compatible format, and probably will be for a very long time. For example, if you were to pipe this to a TCP socket on modern printer on port 9100 unchanged, it’ll likely print out roughly correct.

Re: A Readable Specification of TLS 1.3

#26

Post by ComodoHacker »

crispyambulance wrote: post #24

I'll never understand why rfc's, arguably the underpinnings of internet technology, are styled to appear as TYPEWRITTEN pages in HTML. Seriously. Literal pages of typewritten text, on the web. I mean, they take significant effort to devise these standards and write them up, presumably with modern tools, AND THEN force weird typewriter CSS upon them? It looks awful. I can't understand it.

This low-tech format ensures the specs remain readable and unambiguous.

Imagine you've lost most of web technology after a nuclear apocalypse or something and have to recreate it from specs. You have no software guaranteed to render HTML correctly and completely. (We don't have it even now BTW.) It's like bootstrapping a compiler toolchain on an entirely new architecture. You have to start with assembly, and it looks awful.

Re: A Readable Specification of TLS 1.3

#27

Post by crispyambulance »

bonyt wrote: post #25
crispyambulance wrote: post #24

I'll never understand why rfc's, arguably the underpinnings of internet technology, are styled to appear as TYPEWRITTEN pages in HTML. Seriously. Literal pages of typewritten text, on the web. I mean, they take significant effort to devise these standards and write them up, presumably with modern tools, AND THEN force weird typewriter CSS upon them? It looks awful. I can't understand it.

I assume this is because they’re published as plain text files. The HTML is styled to look the same as the plain text versions, including diagrams made assuming a fixed-width font. https://tools.ietf.org/rfc/rfc793.txt Plain ASCII text is a very compatible format, and probably will be for a very long time. For example, if you were to pipe this to a TCP socket on modern printer on port 9100 unchanged, it’ll likely pri…

OK, I see, but they provide three different formats: ASCII, PDF, and HTML.

If there's a zombie apocalypse and we end up raiding the computer history museum for 80 column line-printers, sure, it makes sense to select the ASCII version to make print outs so that we could rebuild the internet.

But for the HTML version? Come on! Freshen it up a bit.

Post reply on HN