Reminds me of browsh[1]. Interesting projects.
Forking Chrome to render in a terminal (2023)
11–20 of 20 posts
Re: Forking Chrome to render in a terminal (2023)
#12This needs an option to use the Kitty Graphics Protocol: https://sw.kovidgoyal.net/kitty/graphics-protocol/ No need to render to ASCII/Unicode anymore!
Yes I agree, there is also sixel format but I think that sixel is generally used for pngs etc. but both are really cool imo.
Re: Forking Chrome to render in a terminal (2023)
#13Fun fact, this project helped the author get a job: https://github.com/fathyb/carbonyl/issues/162#issuecomment-1... Carbonyl is surprisingly performant and usable, especially with --zoom=300 --bitmap At lower resolutions, it would be nice to render images using a "subpixel" terminal rendering library like chafa ( https://hpjansson.org/chafa/ ), or maybe sixels/kitty image protocol.
I remember wanting to use carbonyl on some server so that I don't need to actually create a tunnel b/w 2 servers, start puppeeter in debug instance and open up a website and then hook it up using remote debugging in my ungoogled chromium.
I really wanted something that could just work...
Now that being said, the project was really cool.
So it might come slightly off topic but when I had last viewed the project, there were a lot of people asking if the project is dead or more importantly, what has happened to author and there were comments like this after the job part and even hackernews showed concern of the dev's life https://github.com/fathyb/carbonyl/issues/201 [is the dev killed by IDF in Gaza #201]
Re: Forking Chrome to render in a terminal (2023)
#14This needs an option to use the Kitty Graphics Protocol: https://sw.kovidgoyal.net/kitty/graphics-protocol/ No need to render to ASCII/Unicode anymore!
maybe kitty should just implement an X11 server or wayland and support all gui programs
Re: Forking Chrome to render in a terminal (2023)
#15It's surprisingly capable. One tricky problem is trying to solve Captchas with it.
Multimodal LLMs can solve captchas easily if they're allowed to.
Re: Forking Chrome to render in a terminal (2023)
#16This project delivers. Ran on gnome-terminal using podman and I was there watching youtube videos in blocky images. I must try on my rasperry pi.
Re: Forking Chrome to render in a terminal (2023)
#17Re: Forking Chrome to render in a terminal (2023)
#18This needs an option to use the Kitty Graphics Protocol: https://sw.kovidgoyal.net/kitty/graphics-protocol/ No need to render to ASCII/Unicode anymore!
maybe kitty should just implement an X11 server or wayland and support all gui programs
It already exists for Sixel: https://github.com/saitoha/xserver-sixel
...but at that point X forwarding or VNC seems more useful.
Re: Forking Chrome to render in a terminal (2023)
#19It looks like the project is abandoned/no longer maintained.
brow.sh (firefox in the terminal) is still being updated though.
Re: Forking Chrome to render in a terminal (2023)
#20[flagged]