There's no JS support, but a good chunk of CSS is implemented, and images are displayed using terminal graphics if your terminal supports it.
You can try it out by passing a URL to `euporie-notebook`.
[1] https://github.com/joouha/euporie/blob/dev/euporie/core/ft/h...
Please don't complain about tangential annoyances—e.g. article or website formats, name collisions, or back-button breakage. They're too common to be interesting.
https://git.sr.ht/~bptato/chawan/tree/master/item/.gitignore
https://git.sr.ht/~bptato/chawan/tree/master/item/.gitmodule...
https://git.sr.ht/~bptato/chawan/tree/master/item/Makefile
https://git.sr.ht/~bptato/chawan/tree/master/item/README.md
To view raw substitute blob for tree
https://git.sr.ht/~bptato/chawan/blob/master/README.md
Actually Github has become recently more difficult to browse with the text-only browser I use. They keep messing with the HTML and breaking this simple structure.
I just download the .zip files and browse offline.
ocaml, f#, clojure, zig, raku, array language --> insta follow
rust, smalltalk , lisp/scheme --> 50-50
python --> boooo , not gonna follow
If you only have a 3kbps internet connection tethered from a phone, then it's good to SSH into a server and browse the web through, say, elinks. That way the server downloads the web pages and uses the limited bandwidth of an SSH connection to display the result. However, traditional text-based browsers lack JS and all other modern HTML5 support. Browsh is different in that it's backed by a real browser, namely headless Firefox, to create a purely text-based version of web pages and web apps. These can be easily rendered in a terminal or indeed, ironically, in another browser. Do note that currently the browser client doesn't have feature parity with the terminal client.If I have firefox installed, I'd just use it!
On the website the following use-case is mentioned: > run firefox remotely in order to "significantly reduce bandwidth and thus both increase browsing speeds and decrease bandwidth costs."
Another use-case would be running firefox on a remote server with just enough power while using ssh on a smaller, weaker, device (raspbery pi like, an old smartphone with termux, very old hardware, ...).
It's hard to build a browser engine, especially if you intend to support a seemless modern web experience (and thus with javascript, unlike all the text-browsers out there). Some even argue it's not possible to build a modern web browser engine anymore [1].
I think it's the point for browsh to rely on another piece of software that will focus on just that (headless firefox).
Browsh is described as a "text-based browser", but under the hood, a more technical accurate way to summarize it would be "a software to stream a remote firefox in your terminal". The concept (and why it saves bandwitch) is detailed on the docs section "What is browsh?" [2].
[1] https://drewdevault.com/2020/03/18/Reckless-limitless-scope.... [2] https://www.brow.sh/docs/introduction/