Comment by 1vuio0pswjnm7

I use a modified, "modern" text-only browser that compiles to 1.4 MB static binary after I remove some multilanguage encodings

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-...