#retawq — Public Fediverse posts

#retrocomputing #frogfind #searchengine #unix #retawq

👻 Another Ghost in the Logs: When a UNIX Classic Says Hello

Usually, a morning logfile analysis is just a noisy stream of AI scrapers, script kiddies, and SEO bots. But this week, FrogFind’s logs caught a true retro artifact: retawq/0.2.6c [en] (text). 🎣

Seeing a terminal-based browser from 2004 bravely navigating the web of 2026 demands absolute respect!

🕰️ What exactly is retawq?
When we think of text browsers, we usually think of Lynx or w3m. But retawq is a highly optimized, multi-threaded text-mode browser from the early 2000s (this specific version dropped in 2004). Built in C for POSIX systems, it relies purely on curses/ncurses for terminal output. No JavaScript, no bloated CSS, no trackers—just blazing-fast, pure text. 💻

🐸 The FrogFind Magic
If this classic browser hit a modern website today, it would instantly choke on megabytes of React and Angular scripts. This is where FrogFind steps in as the perfect translator.

FrogFind strips away the modern bloat and serves pure, lightweight HTML. For retawq, this is a feast: it perfectly renders ASCII tables, keeps links keyboard-navigable, and delivers a flawless text flow. ⚡

🎯 Mission Accomplished
Log entries like this are the ultimate proof of why we do this. Somewhere out there, someone is sitting at a classic UNIX box, a vintage Linux setup, or an old SPARC workstation, reading the daily news in a terminal window.

No cookie popups. No flashing ads. Just pure information, exactly how the web was meant to be. This is why we keep the retro web alive! 🚀

#retrocomputing #frogfind #searchengine #unix #retawq

👻 Another Ghost in the Logs: When a UNIX Classic Says Hello

Usually, a morning logfile analysis is just a noisy stream of AI scrapers, script kiddies, and SEO bots. But this week, FrogFind’s logs caught a true retro artifact: retawq/0.2.6c [en] (text). 🎣

Seeing a terminal-based browser from 2004 bravely navigating the web of 2026 demands absolute respect!

🕰️ What exactly is retawq?
When we think of text browsers, we usually think of Lynx or w3m. But retawq is a highly optimized, multi-threaded text-mode browser from the early 2000s (this specific version dropped in 2004). Built in C for POSIX systems, it relies purely on curses/ncurses for terminal output. No JavaScript, no bloated CSS, no trackers—just blazing-fast, pure text. 💻

🐸 The FrogFind Magic
If this classic browser hit a modern website today, it would instantly choke on megabytes of React and Angular scripts. This is where FrogFind steps in as the perfect translator.

FrogFind strips away the modern bloat and serves pure, lightweight HTML. For retawq, this is a feast: it perfectly renders ASCII tables, keeps links keyboard-navigable, and delivers a flawless text flow. ⚡

🎯 Mission Accomplished
Log entries like this are the ultimate proof of why we do this. Somewhere out there, someone is sitting at a classic UNIX box, a vintage Linux setup, or an old SPARC workstation, reading the daily news in a terminal window.

No cookie popups. No flashing ads. Just pure information, exactly how the web was meant to be. This is why we keep the retro web alive! 🚀

#retrocomputing #frogfind #searchengine #unix #retawq

👻 Another Ghost in the Logs: When a UNIX Classic Says Hello

Usually, a morning logfile analysis is just a noisy stream of AI scrapers, script kiddies, and SEO bots. But this week, FrogFind’s logs caught a true retro artifact: retawq/0.2.6c [en] (text). 🎣

Seeing a terminal-based browser from 2004 bravely navigating the web of 2026 demands absolute respect!

🕰️ What exactly is retawq?
When we think of text browsers, we usually think of Lynx or w3m. But retawq is a highly optimized, multi-threaded text-mode browser from the early 2000s (this specific version dropped in 2004). Built in C for POSIX systems, it relies purely on curses/ncurses for terminal output. No JavaScript, no bloated CSS, no trackers—just blazing-fast, pure text. 💻

🐸 The FrogFind Magic
If this classic browser hit a modern website today, it would instantly choke on megabytes of React and Angular scripts. This is where FrogFind steps in as the perfect translator.

FrogFind strips away the modern bloat and serves pure, lightweight HTML. For retawq, this is a feast: it perfectly renders ASCII tables, keeps links keyboard-navigable, and delivers a flawless text flow. ⚡

🎯 Mission Accomplished
Log entries like this are the ultimate proof of why we do this. Somewhere out there, someone is sitting at a classic UNIX box, a vintage Linux setup, or an old SPARC workstation, reading the daily news in a terminal window.

No cookie popups. No flashing ads. Just pure information, exactly how the web was meant to be. This is why we keep the retro web alive! 🚀

#retrocomputing #frogfind #searchengine #unix #retawq

👻 Another Ghost in the Logs: When a UNIX Classic Says Hello

Usually, a morning logfile analysis is just a noisy stream of AI scrapers, script kiddies, and SEO bots. But this week, FrogFind’s logs caught a true retro artifact: retawq/0.2.6c [en] (text). 🎣

Seeing a terminal-based browser from 2004 bravely navigating the web of 2026 demands absolute respect!

🕰️ What exactly is retawq?
When we think of text browsers, we usually think of Lynx or w3m. But retawq is a highly optimized, multi-threaded text-mode browser from the early 2000s (this specific version dropped in 2004). Built in C for POSIX systems, it relies purely on curses/ncurses for terminal output. No JavaScript, no bloated CSS, no trackers—just blazing-fast, pure text. 💻

🐸 The FrogFind Magic
If this classic browser hit a modern website today, it would instantly choke on megabytes of React and Angular scripts. This is where FrogFind steps in as the perfect translator.

FrogFind strips away the modern bloat and serves pure, lightweight HTML. For retawq, this is a feast: it perfectly renders ASCII tables, keeps links keyboard-navigable, and delivers a flawless text flow. ⚡

🎯 Mission Accomplished
Log entries like this are the ultimate proof of why we do this. Somewhere out there, someone is sitting at a classic UNIX box, a vintage Linux setup, or an old SPARC workstation, reading the daily news in a terminal window.

No cookie popups. No flashing ads. Just pure information, exactly how the web was meant to be. This is why we keep the retro web alive! 🚀

#retrocomputing #frogfind #searchengine #unix #retawq

👻 Another Ghost in the Logs: When a UNIX Classic Says Hello

Usually, a morning logfile analysis is just a noisy stream of AI scrapers, script kiddies, and SEO bots. But this week, FrogFind’s logs caught a true retro artifact: retawq/0.2.6c [en] (text). 🎣

Seeing a terminal-based browser from 2004 bravely navigating the web of 2026 demands absolute respect!

🕰️ What exactly is retawq?
When we think of text browsers, we usually think of Lynx or w3m. But retawq is a highly optimized, multi-threaded text-mode browser from the early 2000s (this specific version dropped in 2004). Built in C for POSIX systems, it relies purely on curses/ncurses for terminal output. No JavaScript, no bloated CSS, no trackers—just blazing-fast, pure text. 💻

🐸 The FrogFind Magic
If this classic browser hit a modern website today, it would instantly choke on megabytes of React and Angular scripts. This is where FrogFind steps in as the perfect translator.

FrogFind strips away the modern bloat and serves pure, lightweight HTML. For retawq, this is a feast: it perfectly renders ASCII tables, keeps links keyboard-navigable, and delivers a flawless text flow. ⚡

🎯 Mission Accomplished
Log entries like this are the ultimate proof of why we do this. Somewhere out there, someone is sitting at a classic UNIX box, a vintage Linux setup, or an old SPARC workstation, reading the daily news in a terminal window.

No cookie popups. No flashing ads. Just pure information, exactly how the web was meant to be. This is why we keep the retro web alive! 🚀

I tried to simulate a #56k connection under Linux with wondershaper: git://github.com/magnific0/wondershaper I ran it with “./sudo wondershaper -a $IFACE -d 56 -u 32”. #Gopher and #IRC worked fast enough, telnet with near no lag, and #MUDs better than telnet with tt++. HTTPS over #lynx ran so-so, #Retawq a little better. SSH was a latency monster, mosh made input bearable but switching between tmux panes had half-sec lag. #Gemini was unusabily slow over telnet at SDF, (maybe it sends too much redraws?), while locally wasn’t better and I’ve got several connection errors in order to get a page.

I think #Gemini and #HTTPS pages need at least an ISDN or low end DSL connection to get usable enough.

#EDIT 56k modems were not that asymetrical, with further test #gemini works ok, better than #HTTPS at least. Still, upon opening two IRC clients the lag get as it shows under mosh, SSH it’s just unusable. Also, the documentation is wrong and I may have to divide the units by 8, so I may be right from the first statement.

I tried to simulate a #56k connection under Linux with wondershaper: git://github.com/magnific0/wondershaper I ran it with “./sudo wondershaper -a $IFACE -d 56 -u 32”. #Gopher and #IRC worked fast enough, telnet with near no lag, and #MUDs better than telnet with tt++. HTTPS over #lynx ran so-so, #Retawq a little better. SSH was a latency monster, mosh made input bearable but switching between tmux panes had half-sec lag. #Gemini was unusabily slow over telnet at SDF, (maybe it sends too much redraws?), while locally wasn’t better and I’ve got several connection errors in order to get a page.

I think #Gemini and #HTTPS pages need at least an ISDN or low end DSL connection to get usable enough.

#EDIT 56k modems were not that asymetrical, with further test #gemini works ok, better than #HTTPS at least. Still, upon opening two IRC clients the lag get as it shows under mosh, SSH it’s just unusable. Also, the documentation is wrong and I may have to divide the units by 8, so I may be right from the first statement.