$ finger johnc@idsoftware.com
No retweets, no likes, no notifications, no HN frontpage, but John Carmack kept writing them, and we kept reading. Even without any amplification dynamics, it was still engaging.I've tried the same now, 30 years after my last finger. It wasn't even installed on Ubuntu by default. I had to install it, and expectedly:
$ finger johnc@idsoftware.com
finger: connect: Connection timed outI still remember a book about the internet I got in the early 90s... it was a couple of hundred pages, and then in the last chapter there was one paragraph in a section about new technology for something called "the World Wide Web".
For years I would be frustrated at people who would conflate the internet and The World Wide Web. I gave up on that years ago, though.
As far as i understood, NSA has access to the encrypted communication on the internet so all bets are off. They '"collaborate" with certificate issuers, they monitor all big internet nodes in the "west" and all relevant software is produced in their jurisdiction.
It's not that HTML forces well-meaning creators to add complexity, size, or user-hostile behavior; it's that an ecosystem that permits such behavior eventually becomes swamped by adtech and other user-hostile content for financial gain. The problem is that this content drowns out organic, human-centric content.
Having said that, while format restrictions (to plaintext, markdown, gemtext, HTML without JavaScript) do help mitigate the damage somewhat by making tracking harder, I doubt they are sufficient: even text-only forums can become overrun with spam, ads, bots, and propaganda if they lack suitable moderation.
Ultimately folks who want to browse a web of authentic human content need to combine format restrictions with blocklists and web-of-trust tools. Browser plugins, reader mode, and customized search engines can already get us partway there, but there are still gaps.
Perhaps a "Simple Web" spec could be created to audit a site and verify its privacy and simplicity protections. Things like "Cookies only for auth", "No JS" or "low JS", "No ref tracking in or out", "No tracking pixels", etc.
Notably missing Safari and WebKit
I've been using this browser since around 2000. I think some HN commnters would be syrprised at how much of the www I can digest using this program. They wouldn't believe it was possible
I use localhost TLS forward proxies for HTTPS. Breaking TLS turns out to be an excellent method for blocking ads and telemetry, in addition to DNS and "ad blockers"
People like to pretend that Google and other so-called "tech" companies have killed off HTTP
It may be true depending on one's www usage, but I see evidence that HTTP still alive
When their "business model" is collecting data from and about unsuspecting computer users, it makes sense for these companies to want the transmissions encrypted. If users saw what is being sent over the wire to these companies they might be upset. If competitors saw it then they might use the data themselves. Too much data collection... I digress
There are bands of vocal "tech" workers who try to drown out any mention of HTTP. Others try to make fun of FTP
But both are still being used in a variety of places, whether it's by CAs themselves^1, Google, e.g., for autocomplete^2 or even the NY Times^3 or MSN
Anyway, the point is that these companies may try to kill off usage of certain protocols where it suits them, e.g., remember FTP in the web browser. But the protocols still survive and people still use them, even if it's only the "tech" workers themselves, and others in small numbers
1.
http://ocsp.globalsign.com/ca/gsatlasr3dvtlsca2026q2
http://secure.globalsign.com/cacert/gsatlasr3dvtlsca2026q2.c...
http://crl.globalsign.com/ca/gsatlasr3dvtlsca2026q2.crl
2.
http://clients1.google.com/complete/search?client=heirloom-h...
3.
via Fastly
https://raw.githubusercontent.com/rezmoss/cloud-provider-ip-...
> Chrome alone controls roughly 73% of global desktop browser market share.
> More and more, the webdevs of the world test and develop for Chrome only.
> It doesn't need to be this way. https:// is not the only way to connect and interface with the Internet
These are completely unrelated concepts! Google/Chrome doesn't control HTTP nor HTTPS. There is nothing wrong with the protocols, you can just make your website plaintext file if you like.