11–20 of 113 posts
Must check. In my console only Raspberry-pi I use elinks to browse and scrape web info.
Earlier quoted context omitted.
Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.
Ah, noted. Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!
see some previous discussion https://news.ycombinator.com/item?id=17487552
Earlier quoted context omitted.
Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.
Ah, noted. Must check and see if w3m and lynx have evolved to cope with the modern JavaScript web!
It seems to be incredibly slow which kind of defeats the purpose of having a text-based browser to begin with. I'm not sure, but it looks like it's taking the output of a headless Firefox and turning it into ascii. If that's the case I'd rather stick with something like Lynx, etc.
The point is when you have a connection with limited bandwidth. In such cases you can host browsh in the cloud and connect to it with ssh/mosh. You get a much better experience than text based browsers at a limited bandwidth. It's great for such cases - I use it when hiking / working away from good internet.
" Browsh is currently maintained and funded by one person. If you'd like to see Browsh continue to help those with slow and/or expensive Internet, please consider donating. "
It’s good to see terminal-based browsers are still being developed. I used to use w3m and lynx back in the day, and found them to be very useful at times (such as only having a GPRS signal available - makes browsing on a “full fat” browser impossible). Paired with screen (though I guess mosh would be a good option these days) to enable a resumable session in case the network dropped, of course.
Note that this isn't a "true" terminal-based browser. It's built on a WebExtension running in Firefox that renders out the DOM as text to a Go-based CLI client. It's not a browser engine running in your terminal, it's more of a VNC over TTY.
curl https://v2.wttr.in/London
curl https://cheat.sh/rsync
curl https://v3.wttr.in
https://github.com/chubin/awesome-console-servicesThis is really interesting, I'll have to play around it. I've been browsing news sites with "links" a lot more lately as it usually just gets me the content I want and it does so very fast. No ads, no popups, no JS - just the content. I could achieve the same thing with noscript and a few other extensions but those generally still aren't as fast and simple as links.
If people are looking for an actual modern take on text based browsing, I would refer them to the work of Igor Chubin. curl https://v2.wttr.in/London curl https://cheat.sh/rsync With a supported terminal: curl https://v3.wttr.in And also: https://github.com/chubin/awesome-console-services