51–60 of 113 posts
Earlier quoted context omitted.
I don't think there's a single reason to use a text-based browser in a production environment.
browsing through SSH
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
I think my terminal's font is breaking the v2 graphs because the unfilled braille dots aren't blank rather unfilled circles. The v3 version doesn't work as my terminal doesn't support images. On my Windows box it actually does work surprisingly well with the official curl binary and the graph looks great but the weather emoji mess up alignment towards the end. I think these kinds of inconsistencies are the reason som…
Yes it's super slow, but many of the criticisms are missing the point. This enables browsing over SSH when you have low bandwidth. The heavy internetting is done on the remote machine (like a cloud VM for example) using blazing fast data center internet. A personal example may explain why I love this. For several years I lived in rural Alaska where the fastest internet one could buy was $120 a month (I think) and a b…
- ublock origin
- you can disable web fonts to cut bloated page sizes in half
Beyond that it gets progressively more difficult:
- squid isn't that useful, even with a fair amount of configuration for various reasons. Weird but true.
- SSL makes the Internet less cacheable.
- replacing multi-image icon menus with one map is helpful
- using a real mouse with your notebook can make it feel less painful.
(Most of these techniques I used either in Bali, or using a netbook in Calif.)
Yes it's super slow, but many of the criticisms are missing the point. This enables browsing over SSH when you have low bandwidth. The heavy internetting is done on the remote machine (like a cloud VM for example) using blazing fast data center internet. A personal example may explain why I love this. For several years I lived in rural Alaska where the fastest internet one could buy was $120 a month (I think) and a b…
But what does this do that links via ssh doesn’t already do?
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
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
[0] https://github.com/chubin/wttr.in/blob/4eedafb81356e62b9f1c8...
Yes it's super slow, but many of the criticisms are missing the point. This enables browsing over SSH when you have low bandwidth. The heavy internetting is done on the remote machine (like a cloud VM for example) using blazing fast data center internet. A personal example may explain why I love this. For several years I lived in rural Alaska where the fastest internet one could buy was $120 a month (I think) and a b…
But what does this do that links via ssh doesn’t already do?
I should really pick that up again.
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.