#brow6el — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #brow6el, aggregated by home.social.
-
User base of #linux #terminal #graphical #webbrowser #brow6el asked if it would be possible to use it for preview of #html messages and attachments in #aerc mail client. Proof of concept of html pager for aerc is on its way.
-
User base of #linux #terminal #graphical #webbrowser #brow6el asked if it would be possible to use it for preview of #html messages and attachments in #aerc mail client. Proof of concept of html pager for aerc is on its way.
-
User base of #linux #terminal #graphical #webbrowser #brow6el asked if it would be possible to use it for preview of #html messages and attachments in #aerc mail client. Proof of concept of html pager for aerc is on its way.
-
User base of #linux #terminal #graphical #webbrowser #brow6el asked if it would be possible to use it for preview of #html messages and attachments in #aerc mail client. Proof of concept of html pager for aerc is on its way.
-
User base of #linux #terminal #graphical #webbrowser #brow6el asked if it would be possible to use it for preview of #html messages and attachments in #aerc mail client. Proof of concept of html pager for aerc is on its way.
-
when using #brow6el #linux #terminal #webbrowser in #kittyterminal (yes we now support kitty image protocol) the YT video is almost like in "normal" browser.
-
#sixels do “compress” image data by its nature design, #libsixel is highly optimized, on the other side #kittyterminal protocol
Direct transmission (t=d):
RGB/RGBA -> base64 … huge data transfer
RGB/RGBA -> PNG -> base64 … better in size, significant overhead
RGB/RGBA -> zlib compression -> base64 … also significant overhead
RGB/RGBA -> PNG -> zlib compression -> base64 .. even bigger overheadSimple file transmission (t=f)
Client needs access to file … Forget about #sshTemporary file transmission (t=t)
Client needs access to /tmp, /dev/shm … forget about sshShared memory object (t=s)
Client needs to have access to POSIX shared memory object/Windows named shared memory object … forget about ssh.So yes, kitty is “superior” protocol with superior performance, except it works as “superior” only on localhost and event that is questionable at least in case of #brow6el (ok I acknowledge thats this is very specific “hack”)
-
Being described as “essentially performed the software equivalent of fitting a Ferrari engine into a horse carriage, and somehow made it work.” made my day. #brow6el #makeuseof
https://www.makeuseof.com/laughed-at-terminal-browser-used-it/
-
Wow, I’ve just tried #brow6el - a #sixel based terminal (!) web browser - on one of classic Polish portals, packed with ads and mashup JS/HTML. And it… works!
Sixel is an old (DEC times) but very clever protocol for displaying 6-bit graphics right in terminal window, Brow6el is a Chromium-engine using Sixel graphics to render the pages. So essentially you’ve got a fully functional graphical (!) web browser in a text terminal. Because it’s still Chromium, this particular website uses ~500 MB of RAM.
Surprisingly, the build process on Ubuntu is also rather trivial and takes ~5 min (thanks to the use of prebuilt Chromium binary I suppose)
-
Wow, I’ve just tried #brow6el - a #sixel based terminal (!) web browser - on one of classic Polish portals, packed with ads and mashup JS/HTML. And it… works!
Sixel is an old (DEC times) but very clever protocol for displaying 6-bit graphics right in terminal window, Brow6el is a Chromium-engine using Sixel graphics to render the pages. So essentially you’ve got a fully functional graphical (!) web browser in a text terminal. Because it’s still Chromium, this particular website uses ~500 MB of RAM.
Surprisingly, the build process on Ubuntu is also rather trivial and takes ~5 min (thanks to the use of prebuilt Chromium binary I suppose)
-
Wow, I’ve just tried #brow6el - a #sixel based terminal (!) web browser - on one of classic Polish portals, packed with ads and mashup JS/HTML. And it… works!
Sixel is an old (DEC times) but very clever protocol for displaying 6-bit graphics right in terminal window, Brow6el is a Chromium-engine using Sixel graphics to render the pages. So essentially you’ve got a fully functional graphical (!) web browser in a text terminal. Because it’s still Chromium, this particular website uses ~500 MB of RAM.
Surprisingly, the build process on Ubuntu is also rather trivial and takes ~5 min (thanks to the use of prebuilt Chromium binary I suppose)
-
Wow, I’ve just tried #brow6el - a #sixel based terminal (!) web browser - on one of classic Polish portals, packed with ads and mashup JS/HTML. And it… works!
Sixel is an old (DEC times) but very clever protocol for displaying 6-bit graphics right in terminal window, Brow6el is a Chromium-engine using Sixel graphics to render the pages. So essentially you’ve got a fully functional graphical (!) web browser in a text terminal. Because it’s still Chromium, this particular website uses ~500 MB of RAM.
Surprisingly, the build process on Ubuntu is also rather trivial and takes ~5 min (thanks to the use of prebuilt Chromium binary I suppose)
-
Wow, I’ve just tried #brow6el - a #sixel based terminal (!) web browser - on one of classic Polish portals, packed with ads and mashup JS/HTML. And it… works!
Sixel is an old (DEC times) but very clever protocol for displaying 6-bit graphics right in terminal window, Brow6el is a Chromium-engine using Sixel graphics to render the pages. So essentially you’ve got a fully functional graphical (!) web browser in a text terminal. Because it’s still Chromium, this particular website uses ~500 MB of RAM.
Surprisingly, the build process on Ubuntu is also rather trivial and takes ~5 min (thanks to the use of prebuilt Chromium binary I suppose)
-
It is time to start migrating my #oss code to #codeberg and why not to start with something funny and new. This is my toy project. Let me introduce #brow6el, very basic Linux terminal #webbrowser based on Chromium CEF with #sixel rendering. Yes you can have fully graphical browser in #Linux terminal if you have sixel support. No binary files are available yet, but build is pretty simple and documented. Be aware it just POC with glitches here and there, so be nice to me. But it has js console ;-) if I will have time, I will add bookmarks. https://codeberg.org/janantos/brow6el
-
It is time to start migrating my #oss code to #codeberg and why not to start with something funny and new. This is my toy project. Let me introduce #brow6el, very basic Linux terminal #webbrowser based on Chromium CEF with #sixel rendering. Yes you can have fully graphical browser in #Linux terminal if you have sixel support. No binary files are available yet, but build is pretty simple and documented. Be aware it just POC with glitches here and there, so be nice to me. But it has js console ;-) if I will have time, I will add bookmarks. https://codeberg.org/janantos/brow6el
-
It is time to start migrating my #oss code to #codeberg and why not to start with something funny and new. This is my toy project. Let me introduce #brow6el, very basic Linux terminal #webbrowser based on Chromium CEF with #sixel rendering. Yes you can have fully graphical browser in #Linux terminal if you have sixel support. No binary files are available yet, but build is pretty simple and documented. Be aware it just POC with glitches here and there, so be nice to me. But it has js console ;-) if I will have time, I will add bookmarks. https://codeberg.org/janantos/brow6el
-
It is time to start migrating my #oss code to #codeberg and why not to start with something funny and new. This is my toy project. Let me introduce #brow6el, very basic Linux terminal #webbrowser based on Chromium CEF with #sixel rendering. Yes you can have fully graphical browser in #Linux terminal if you have sixel support. No binary files are available yet, but build is pretty simple and documented. Be aware it just POC with glitches here and there, so be nice to me. But it has js console ;-) if I will have time, I will add bookmarks. https://codeberg.org/janantos/brow6el
