> Text-based browsers and modern HTML, no success story in sight. Given the progress we see in web technologies, the gap will only widen, so much so that w3m and its friends might fall into oblivion.
This is a fun article and the conclusion is very real.
People shit on Gemini:// because “The web can support text documents”. They say this as if they are actually proposing a real solution. It’s true that the web _can_ support lightweight content (IE5 on Windows 3.1- I was there man), but the problem is that it _won’t_ because it consistently chooses not to. If you’ve ever tried to actually perform this experiment of running the web in text mode you will quickly realize how futile it truly is. Every step you take on a well meaning site like lite.cnn.com is just one click away from transferring you to a bloated SPA app that renders a blank screen on a text-based browser. You can disable JavaScript, or disable images or whatever hoops you want to jump through (increasingly hidden with every FireFox release that goes by) but that’s not going to actually work long term. The web is too extensible and feature hungry to support text based content. It’s better to just use the web for the usual cool shit like WASM and WebRTC or whatever and admit that no one can help themselves and no amount of awareness is going to make the cookie consent banners go away.
Let’s take Gemini more seriously because it already has adoption and it works and it’s not perfect but it sure as fuck isn’t substack.
Gemini is my go to now when I need a recipe. Pick a recipe site, any recipe site, and its guaranteed to be the most painful experience on mobile, and slightly less painful on a laptop experience you have on the web. Pure fucking trash. And if you happen to be a recipe publisher who does this and is reading this, fuck you.
Enter Gemini. It consistently can give me a text only version of the recipe that I can copy into a notes app if I want with zero pain. Zero. Now I have my own set of "wtf are you doing Gemini" and "why are you halucinating on this request" experiences at work with Gemini, but recipe extraction.. the goat.
One of my favorite pieces of software is edbrowse[0]. Perhaps surprisingly, I find it quite useful:
- Main developer is blind, so accessibility has priority;
- Easily scriptable; think automating captive portal clickthroughs;
- Reading articles (e.g. Wikipedia) feels closer to reading a book;
- It even supports JavaScript to a degree!
- The affordances of line-oriented editing carry over nicely.
In particular, when using line-oriented interfaces, it's quite natural to build up a small collection of context-dependent snippets from documentation, source code, sample code, whatever. Putting a small collage of these on the screen is effortless and an experience I do miss with other UI paradigms.
The main developer appears to tinker on the project daily and is quite nice to chat with over on libera's #edbrowse. The project does have a small, dedicated following, but I wish more people knew about it!
> The history directory contains information on the history of edbrowse, how it came to be and what it is trying to accomplish. This includes a wikipedia article, written in markup. It was deleted by the wikipedia maintainers, for lack of sources. If edbrowse is described in a book or mainstream magazine in the future, perhaps this article can be reintroduced
> Main developer is blind, so accessibility has priority;
Never thought about it before, but doing development work as a blind person sounds extremely impressive.
Vision is just such a fast and easy way to acquire information. Without it, it seems quite difficult to check your existing code, easily read prior documentation, take notes, and just various other conveniences that one take for granted.
I'm sure there are various tools and methods to ameliorate these problems, but still.
I think you nailed the drive behind my ~3 decades of Emacs use: "I can get at all the text" (possibly above the customization/automation benefits despite this being the "advanced" pov above "it's just a text editor isn't it?"
The top comment in the article mentions it, but chawan[1] is really quite neat. Many sites are still have their quirks (or may be broken), but I think it's the closest I've seen a text browser approximate a "real" browser. The support for CSS, JS, and images (depends on your terminal) is already quite impressive even if imperfect. To my knowledge it's an actual browser implementation rather than "cheating" by using an existing browser like browsh (which is still quite cool).
Sadly and disgustingly, I fired up lynx last night and found out that Google will not allow you to search with it anymore. I guess this change happened a few months ago and there was an HN thread about it[0], but I hadn't noticed until now.
Going to altavista still works great (even though it just redirects you to yahoo ;)
For many, if not most, of the sites I regularly visit, text based browsers work surprisingly fine. My main complaint is actually the structure of the html. In many cases sites could improve massively, if they moved navigation to below the actual content. Having a large vertical menu taking up the entire screen as the first thing you see is slightly annoying.
Best thing about sites that works in TUI browser is that it can also work in Tor Browser "Safest" mode. In fact to those who are saying that these text based website are anti feature. I would argue that it is a safety feature to be able to browse and work in Tor Browser "Safest" mode. In fact ALL web page should strive to work in "Safest" mode, and only throw in bells and whistles when needed. As one can see just by turn on JS the site is NO longer really safe.
For the (small, noncommercial) sites I help with, we've always had at least a ‘jump to content’ link at the very top, hidden by CSS, dating back to when lynx was my main browser. In practice today, it's more for people using screen readers.
w3m's marketshare has always been nonexistent. It already has been in oblivion. Having a GUI is key to making a good web browser that will be used by people.
They could be used in bloody fast AI crawling and browse, for example dynamic webbased finetuning which involves non-static content: I think GET requests are safe in this matter.
You do not need much more than a semantic 2D table with proper navigation ids. Does wonders with basic HTML forms. You can augment it with a simple CSS in order to give to it a nice look. A troubling issue is "border" in semantic tables: they are a semantic information, not style, it should not be deprecated.
Tested edbrowse javascript, hardly anything works. Maybe the edbrowse developer should get closer to netsurf libraries and work there on quickjs support.
I had an idea once for connecting an old 8-bit computer to the modern web by connecting to a text-based web browser running on another device using the terminal. Maybe one day when I find more time.
The note that someone told them DataList might be bad for accessibility is the first I'm hearing of it. Does anyone know what is meant by this?
This reminds me of a problem I've been having with some accessibility issues: maybe, sometimes, occasionally, the accessibility problems a site has aren't the authors' fault but the fault of the folks writing the screen reader software. I've tried using screen reader software and it is an awful experience. It's nearly impossible to create a good experience for screen readers because they are all their own, unique microcosm of unstandardized garbage and bugs.
> When viewing a web page in a text-based browser, you essentially get plain HTML, no CSS, no JS. There is some “styling”, a result of the elements’ semantics, but don’t expect anything fancy, we are down to colors, indentation, and centered text.
I think it might be offtopic but is there any way that there are minimalist browsers which can work on let's say vps's but I wouldn't need to host a complete vnc server or set up with the debugging port magic of puppeteer or chrome
I think browsh which is a text based web browser is the most recommended for something like this but browsh doesnt map things 1 to 1 and there are still some issues. I wish if there was a simple browsh alternative which could use new image protocols in terminal (I think kitty protocol or other comes to my mind) to basically act as a complete browser.
Does anyone know of anything like this? I sometimes like the idea of just leaving a tab completely open 24x7 on a vps, I feel like there can be interesting data which can happen because of it. Thoughts?
Having to navigate to and from online plain text files (usually .txt) I like a browser to recognize addresses with or without HTTP and see them as links. It's a surprisingly tricky feature to find in browsers (right click, grab and ask, etc.). I wrote a tiny browser to do just that for the command line and it's cute and all, but I'm anxious to interview all the browsers in here to see which have this ability.
If websites removed all CSS and JS, they could still provide almost all the worthwhile content that's currently available, and browsers could become user agents again.
39 comments
[ 4.4 ms ] story [ 59.9 ms ] threadThis is a fun article and the conclusion is very real.
People shit on Gemini:// because “The web can support text documents”. They say this as if they are actually proposing a real solution. It’s true that the web _can_ support lightweight content (IE5 on Windows 3.1- I was there man), but the problem is that it _won’t_ because it consistently chooses not to. If you’ve ever tried to actually perform this experiment of running the web in text mode you will quickly realize how futile it truly is. Every step you take on a well meaning site like lite.cnn.com is just one click away from transferring you to a bloated SPA app that renders a blank screen on a text-based browser. You can disable JavaScript, or disable images or whatever hoops you want to jump through (increasingly hidden with every FireFox release that goes by) but that’s not going to actually work long term. The web is too extensible and feature hungry to support text based content. It’s better to just use the web for the usual cool shit like WASM and WebRTC or whatever and admit that no one can help themselves and no amount of awareness is going to make the cookie consent banners go away.
Let’s take Gemini more seriously because it already has adoption and it works and it’s not perfect but it sure as fuck isn’t substack.
Enter Gemini. It consistently can give me a text only version of the recipe that I can copy into a notes app if I want with zero pain. Zero. Now I have my own set of "wtf are you doing Gemini" and "why are you halucinating on this request" experiences at work with Gemini, but recipe extraction.. the goat.
The main developer appears to tinker on the project daily and is quite nice to chat with over on libera's #edbrowse. The project does have a small, dedicated following, but I wish more people knew about it!
[0]:https://github.com/edbrowse/edbrowse
Never thought about it before, but doing development work as a blind person sounds extremely impressive.
Vision is just such a fast and easy way to acquire information. Without it, it seems quite difficult to check your existing code, easily read prior documentation, take notes, and just various other conveniences that one take for granted.
I'm sure there are various tools and methods to ameliorate these problems, but still.
[1] https://chawan.net/
> inline images inside the terminal
Now I'm confused
Going to altavista still works great (even though it just redirects you to yahoo ;)
[0] https://news.ycombinator.com/item?id=45201692
Popover seems to be a way to do popup that you can't really block. Also having content you want to hide?
This has some use cases. Besides, keeping content from users was already present in HTML through the practice of not sending it to the user.
w3m's marketshare has always been nonexistent. It already has been in oblivion. Having a GUI is key to making a good web browser that will be used by people.
Tested edbrowse javascript, hardly anything works. Maybe the edbrowse developer should get closer to netsurf libraries and work there on quickjs support.
https://github.com/fathyb/carbonyl
These browsers are cool but I didn't know about browsh [1]. That one is also really cool. Thanks!
[1]: https://www.brow.sh/
This reminds me of a problem I've been having with some accessibility issues: maybe, sometimes, occasionally, the accessibility problems a site has aren't the authors' fault but the fault of the folks writing the screen reader software. I've tried using screen reader software and it is an awful experience. It's nearly impossible to create a good experience for screen readers because they are all their own, unique microcosm of unstandardized garbage and bugs.
So go fork and fix an open source browser to your satisfaction.
Reminds me of Gemini protocol. https://gemini.circumlunar.space/
I think browsh which is a text based web browser is the most recommended for something like this but browsh doesnt map things 1 to 1 and there are still some issues. I wish if there was a simple browsh alternative which could use new image protocols in terminal (I think kitty protocol or other comes to my mind) to basically act as a complete browser.
Does anyone know of anything like this? I sometimes like the idea of just leaving a tab completely open 24x7 on a vps, I feel like there can be interesting data which can happen because of it. Thoughts?
[0] https://github.com/fathyb/carbonyl