3 ms·
"Regarding the images that have been stripped, ask yourself: Did the photo really contribute much to the article?" Not for me. I have been using a text-only b
by 1vuio0pswjnm7 5y ago
"Regarding the images that have been stripped, ask yourself: Did the photo really contribute much to the article?"
Not for me. I have been using a text-only browser to read the www for over 20 years. The keyword here is "read". I do not need graphics to read text.
Ocassionally I get a glimpse of the type of images that users of graphical browsers would see when reading articles and I am often shocked by how little these images add to the text. In a remarkable number of cases, they are just garbage "filler". As if the publisher was "required" to use some images. Perhaps use of images has some effect on users' response to advertising.
What's more is that in cases of true photojournalism, by a reputable media outlet, where I do want to look at the photos, I often find I can extract the URLs and download the images, for offline viewing, easier with non-graphical clients than if I am using a graphical browser. Viewing images is one thing, but I would not want to rely on a graphical browser for downloading them to view offline.
On today's www, I think graphics are overrated. They have a place, but they are routinely being used in situations used when they are not truly necessary. In a surprisingly large number of cases, they do not add anything except distraction.
- hammyhavoc 5y agoMost articles feature an image so that they can be gain more attention on social media via OpenGraph metadata for the image. That and most ways of presenting the articles on these sites are usually very visual. What browser do you use? It sounds like bliss.
- 1vuio0pswjnm7 5y agoI like to think I have tried them all. I wish there were more to try. I settled on links, original and optional graphics. The later is the one found in BSD/Linux package repositories. Compiles fast, source is relatively small. All prior versions are available. Can make the must-have changes myself. No need to rely on anyone else. FWIW, links has the best HTML tables support of any text-only browser I have tried. As an HTML reader links has worked well for me for a long time. I guess compared with an advertising-supported browser that is impossible to control,^1 links could be "bliss", depending on how much one values speed, control and avoiding ads. 1. I can compile an OS, including a customised kernel and hundreds of robust, reliable and secure programs, in less time and with fewer resources than I could compile one of the popular browsers. (By comparison, I do not consider popular browsers to be robust, reliable nor secure. In practice, customisation by users is only possible with "permission" from a company. These oversized programs do not belong to users.)
- gnubison 5y agoI’m sure you’ve already heard of this, but for anyone who hasn’t: check out Gemini, a protocol and format (gemtext) that might appeal to users with this philosophy.
- 1vuio0pswjnm7 5y agoFrom gemini.circumlunar.space: "Overview Gemini is a new internet protocol which: Is heavier than gopher Is lighter than the web Will not replace either Strives for maximum power to weight ratio Takes user privacy very seriously" <--- Yet it REQUIRES user to send plaintext hostnames over the wire With HTTPS, sending the hostname in plaintext over the wire ("SNI") is a problem that can be worked around. However, per the Gemini protocol specification, SNI is mandatory, not optional, even when there is no virtual hosting. That is bad design. Does Gemini provide any workarounds. Why not. At present, I only need to send plaintext hostname over the wire for a minority of HTTPS sites. Most sites do not require it. One shared hosting provider, Cloudflare, even offers encrypted SNI, which works fine while encrypted Client Hello (ECH) is being finalised. AFAICT, the SNI problem will eventually be fixed in HTTPS. Making SNI mandatory, i.e., no option to disable it, is against the philosophy of user control. One of the reasons I use links and other non-graphical clients plus a local TLS proxy, instead using of a popular browser, is because the popular browsers do not permit the user to disable the sending of plaintext hostnames over the wire. Not all HTTPS sites require SNI, in fact most do not require it, yet popular browsers send hostnames in plaintext to every website. From a user perspective, that is stupid. Gemini is arguably worse because it codifies this stupidity into the protocol, thereby ensuring people will write clients that send hostnames in plaintext over the wire to every site and servers that will reject TLS negotiation without SNI. If there is only one Gemini site on an IP address, then it makes no sense to send the hostname in plaintext over the wire.