@evgandr@bsd.cafe @yoasif@mastodon.social @dillo@fosstodon.org

https://old.reddit.com/ is actually somewhat usable with dillo.

I think the best approach to surviving the current webpocalypse is to just forget about having "one browser to rule them all."

Take a multi-vectored approach:

  • Use a terminal browser like w3m, links, lynx, or chawan when doing some quick-and-dirty lookups, or when you don't feel like faffing about with a mouse at all
  • Use #Dillo for blogs, #smolweb sites, and sites that you don't want eating your cpu if you load them in a full browser
  • Optionally use #NetSurf for the few sites you know work better with it
  • Use #Firefox with your own custom settings or a fork like #LibreWolf for things that really require full JS and that kind of thing
  • Use a Blink-based browser like #Falkon or #UnGoogledChromium for the rare cases where a website just doesn't like firefox
I don't have dillo as my default browser on most of my systems now, but on all of my systems, I have one keystroke to open firefox or librewolf, and another to open dillo. A lot of times, I'll grab the url from @tut@fosstodon.org, launch dillo with a keystroke, and paste in the URL. If it doesn't work in dillo for some reason, or the formatting is too far off, it's easy enough just to fire up the old fox and paste in the url there.

Here's a link to a toot where I discovered how to tweak the colors in dillo to be a bit more contrasty:
https://polymaths.social/@rl_dane/statuses/01K3YBWR5XE7N781P9F7432VP7

Here's a link to a toot with my keysrc file for more keyboard-friendly navigation (a little like qutebrowser or luakit, but only a little so far):
https://polymaths.social/@rl_dane/statuses/01K3EQQ78KJG4E07KP74Y6Q0VE

I also have firefox settings to disable AI available upon request. It's a bit of a faff to get it set up the first time, but then you're golden (for now ;)
reddit: the front page of the internet

Reddit gives you the best of the internet in one place. Get a constantly updating feed of breaking news, fun stories, pics, memes, and videos just for you. Passionate about something niche? Reddit has thousands of vibrant communities with people that share your interests. Alternatively, find out what’s trending across all of Reddit on r/popular. Reddit is also anonymous so you can be yourself, with your Reddit profile and persona disconnected from your real-world identity.

Importantes mejoras en el nuevo CaffeineOS 9317

Esta nueva versión del CaffeineOS (9317) se distribuye como imagen completa y requiere obligatoriamente una instalación desde cero grabando la ISO de nuevo, algo poco habitual y aunque pueda resultar una tocada de webs, sobretodo para quienes tienen su sistema muy configurado por propia cuenta, está totalmente justificado por la profundidad de los cambios introducidos y la reestructuración interna del sistema.

Una de las novedades más relevantes es la incorporación de soporte para FrameThrower, configurable directamente desde el archivo cmdline.txt de emu68, lo que abre la puerta a un manejo más fino del renderizado y el rendimiento gráfico. En paralelo, se introducen dos nuevos lanzadores, Start_Caffeine_OS39Edition.exe y Start_CaffeineOS_ButcherEdition.exe, pensados para facilitar la vida a quienes usan CaffeineOS bajo WinUAE. Estas herramientas se encargan de cerrar instancias activas del emulador si el usuario lo desea, lanzar WinUAE con la configuración correcta, gestionar automáticamente los permisos de administrador y garantizar que el arranque del sistema sea coherente y sin fricciones. Todo el funcionamiento queda documentado en un archivo ReadMe específico incluido en el propio sistema.

El apartado gráfico recibe una atención especial en esta versión. Se actualiza el control del kernel de VideoCore con VC4KernelToggle v1.1, basado en el trabajo original de Michal Schulz, permitiendo un escalado pixel-perfect en resoluciones bajas, accesible tanto desde línea de comandos como desde scripts de arranque. A esto se suma VC4KernelCX, una commodity que automatiza el cambio del escalado del kernel de VideoCore en sistemas emu68 y permite activarlo o desactivarlo incluso mediante una simple combinación de teclas, integrándose de forma elegante en el arranque de Workbench.

Otra incorporación importante es la nueva herramienta de descarga de CaffeineOS, diseñada para gestionar actualizaciones y archivos históricos del sistema. Es especialmente relevante porque la edición TheButcher pasará a distribuirse exclusivamente a través de esta herramienta, que se integra tanto en el sistema como en la barra superior. En la misma línea de facilitar la configuración, se añade un editor gráfico del archivo cmdline.txt de emu68, pensado específicamente para sistemas PiStorm, evitando errores manuales y simplificando ajustes avanzados.

A nivel de configuración interna, se introduce el parámetro avoid_warnings=2, que no solo elimina las superposiciones de advertencia, sino que además permite el uso del modo turbo incluso en situaciones de bajo voltaje, una mejora práctica para determinados montajes. También se han refactorizado numerosas utilidades del sistema: AskReboot se actualiza y añade localización polaca, About pasa a mostrar correctamente la versión de WinUAE y el icono del modelo de Amiga también en sistemas 3.x, Karma, ChangeWPA y SetDayLight reciben revisiones profundas en sus versiones MUI, y este último actualiza la base de datos mundial de zonas horarias y reglas de horario de verano.

El sistema viene además acompañado de nuevo contenido preinstalado que refuerza su carácter “listo para usar”. Se incluyen el mod TERRA de Quake, OutRun Amiga Edition AGA, el paquete AmigaE de Ferry, juegos como CAOS_Pong y CAOS_Breakout, así como nuevas librerías y utilidades como gic400.library y Emu68EDID. Todo ello convive con una larga lista de componentes actualizados: emu68 y emu68_32Lite, OpenURL, NetSurf, AmiSSL, MAME MiniMix, WHDLoad, Curl, HippoPlayer, TuneFinder_MUI y múltiples librerías y dispositivos clave del sistema.

Especial atención merece el trabajo realizado en la pila gráfica y de red. Se actualiza el driver videocore.card para Picasso96, se revisa LoadDB para evitar conflictos con comprobaciones de teclas durante el arranque, y CheckSystem ahora detecta automáticamente la versión de emulation.library para ajustar la configuración adecuada de Picasso96. TCPStackSelector amplía compatibilidad con MiamiDX y genet, reforzando la conectividad.

Por último, en los sistemas Butchered se revisa MCP, que deja de ejecutarse en entornos 3.2.x, y se aplica un parche específico a dopus5.library que modifica múltiples asignaciones de memoria de CHIP a ANY, permitiendo un uso mucho más eficiente de la FAST RAM en tareas como renderizado de iconos, manejo de sprites, buffers de imagen y fondos de escritorio.

Recuerda que para usar CaffeineOS, necesitas tus ROMs originales.

Puedes descargarlo y si quieres, donar una pequeña ayuda para que el gran Pedro Cotter pueda seguir con el proyecto adelante, en la web oficial.

#actualizaciónMayor #amiga #AmigaDevelopment #AmigaGames #amigaos #amissl #CaffeineOS9317 #caffeineos #cleanInstallation #CommodoreAmiga #demoscene #desarrolloAmiga #emu68 #escaladoPixelPerfect #Framethrower #gráficosRTG #herramientasDeLanzamiento #herramientasDelSistema #hippoplayer #imagenISO #instalaciónLimpia #ISOImage #juegosAmiga #launcher #MAMEAmiga #netsurf #networkStack #OutRunAmigaEdition #picasso96 #pilaDeRed #pistorm #pixelPerfectScaling #QuakeAmiga #retroComputing #retroinformática #RTGGraphics #sistemaOperativoAmiga #systemUtilities #VC4Kernel #VideoCore #whdload #winuae

Web browser: MUI version of NetSurf 3.11
Version 3.11 of the NetSurf web browser is available for AmigaOS 3.x in a ReAction variant by Chris Young and in an SDL-based variant by Artur Jarosik. The latter has now also started work on a MUI version, the first releases of which have already been made available in their current state of development.

https://www.amiga-news.de/en/news/AN-2025-11-00113-EN.html

#Amiga #AmigaOS3 #MUI #browser #NetSurf

amiga-news.de - Web browser: MUI version of NetSurf 3.11

Sorry for the delay, just seen your reply.

Sure, one might argue that the problem lay on browsers that do not implement the full set of Web standards.
But since more then 20 years such standards are designed by #Google (and geek-friendly #PR dept known as #Mozilla) to reinforce its own hegemony. This means that no real independent group can reasonably hope to build a "standard compliant" browser from scratch.

Now, obviously I gave a deep look to the code of #Netsurf before asking @grunfink@comam.es to modify Snac2.
And unfortunately, the problem is not much handling the details/summary tags (despite them being more complex then one might think at first, because of the name attribute management), but the whole rendering that should be refactored.
The #NetSurf team told me they are analyzing the issue of dynamic rendering, but a solution seem still far to be implemented.
Till then, there is no point into customizing the tags in libdom and enabling a custom rendering in netsurf's layout engine.

Yet you are right that I didn't look specifically into the snac's page rendering code.

And I'm obviously fine to leave it as it is as long as I can't hack on it myself.

But anyway, I supposed that @grunfink@comam.es might be interested in the idea and were curious to discuss it with you.

CC: @dillo@fosstodon.org
WHATWG - Wikipedia

snac is essentially a single-page application
Not much sure I agree.

After all I see a few different URI handled by my snac instance:
I can even focus on a single post through search (as I'm doing right now) and interact with it.

So in abstract I don't think it's something that would degenerate snac's nature: it might serve a few more single task views/page/uri, such as
And the Reply button might be turned to a link to search of the post one wanted to reply to.

With such a setup, I guess both #NetSurf, #Dillo and even #Links and #Lynx would be able to interact with a snac server.

Would I make it the default? well, who knows? in an ideal world, since the change would impact the authenticated user that infact also choose the browser to use, I'd make it something people could configure in a user setting.

But I know I'm asking for work I have no time to do myself these days... for something that few people would appreciate. But I guess those few people would appreciate it a lot! 😀

CC: @dillo@fosstodon.org @grunfink@comam.es
Yeah #NetSurf layout rendering is static: once rendered it can't change much.
I talked a bit with developers and they were considering a refactoring to make it more dynamic, but they're still at design stage.

Yet I see a more simple solution, since in fact details/summary are simply rendered as divs: just leave the thread structure as is, all visible, but add a "Reply" button before "Like" or after "Hide" that link to a new page. In such page you just see the post you are replying to and the reply form. That should make the thread page usable on both NetSurf and @dillo@fosstodon.org

Similar arrangement would be required for the initial forms, "New Post...", "Operations...", "User Settings..." and so on should all become links to different dedicated pages.

Obviously this mode of operation should be controlled by an optional server.json's config.
Or maybe a User Setting, but I'd go for a server.json config for simplicity.

CC: @grunfink@comam.es
How cool is @grunfink@comam.es's Snac2 over NetSurf?

The CSS has been created by @anzu@items.minimals.org (inspired by paper-dark and somewhat hacked by me). The only issue were CSS variables that libcss does not support (yet).

Unfortunately Snac relies on detail/summary HTML tag that is not yet properly handled by NetSurf. It would be nice to have a server.json option to open all forms in dedicated pages, so that a social network programmed in C in could be easily used through a browser programmed in C too!

#Snac2 #NetSurf #FreeSoftware #PermaComputing #KISS
Dillo Website

Exploit demo for CVE-2024-51317, a use-after-free in the #NetSurf web browser enabling arbitrary code execution when JavaScript is enabled. Target is NetSurf 3.11 on Ubuntu 22.04.

Patched in upstream source code, still making its way to distro packages. To mitigate, disable JS (off by default).

Whats going on with #Netsurf? Web and git servers are not reachable