Can we just like, build a new protocol for an alternative web? Maybe something that's way easier/more accessible to create sites for? Cause it's starting to look like http is an evolutionary dead end since it got taken over by megacorps

@eniko Wait, so due to corporate licensing I can't telnet on port 80 any more? 🙀 Or openssl s_client… or nghttp2 as the case may be?

What's the angle to justify "dead end", here, given… open (IETF) standards? (Admittedly, HTTP/2 is based on SPDY from Google, but it **is** an IETF standard, now. As is HTTP/3 relying on QUIC for connection establishment; or lack thereof. A neat trick.)

@alice the web integrity thing Google is pushing and which they've already pushed into their codebase despite opposition that saw them having to lock basically all discussion down. If it's not this it's gonna be some other user hostile bullshit and eventually they're gonna ram it through and it'll become the most laughable "standard" ever devised. Better to just start over with a protocol that inherently protects users from big data and makes ad-driven models impossible

@eniko

> …it'll become the most laughable "standard" ever devised…

Sorry, had to come back and quip: so… like DeCSS? Or any other mechanism based on "secret numbers"? Such standards are never long for the world. They might zombie shuffle, but the inefficacy (my gods, that's a real word!) of the mechanism makes it instantly obsolete.

My father invented an Apple ][ disk copy protection mechanism in the shower which was broken in that month's Dr. Dobb's. Broken before it was used even once.