Notices by Dillo browser (dillo@fosstodon.org)

@mms there is one Dillo release per floppy. The idea is to restrict ourselves to keep the codebase fit in 1.44 MB.

See you at #FOSDEM this Sunday at 16:10. I'll carry some floppy disks with the latest #Dillo 3.2.0 release.

https://fosdem.org/2025/schedule/event/fosdem-2025-4100-resurrecting-the-minimalistic-dillo-web-browser/

@nichlas I know these two:

https://mataroa.blog/
https://bearblog.dev/

But I often use just an editor and write HTML directly. It helps keeping it simple.

"The median page weight for a desktop page, as measured in October 2024 is 2,652 KB", we could fit two #Dillo releases there!

https://almanac.httparchive.org/en/2024/page-weight#fig-15

Amazing yearly report on the state of the #Web by the HTTP Archive, check it out:

https://almanac.httparchive.org/en/2024/table-of-contents

#Dillo version 3.2.0 released! 🎉

https://dillo-browser.github.io/release/3.2.0

#Google is now banning #Dillo user agent via a JS wall. Other user agents still work for now (http_user_agent option in dillorc).

See: https://news.ycombinator.com/item?id=42719865

#Dillo 3.2.0-rc1 released.

If no more problems appear, the stable release will follow soon.

https://github.com/dillo-browser/dillo/releases/tag/v3.2.0-rc1

Not all heroes wear capes.

https://forums.raspberrypi.com/viewtopic.php?t=291177

Tell me again why I cannot edit a page from the browser itself using HTTP PUT (like a wiki).

https://techno-barje.fr/post/2023/10/20/history-of-edition-and-publishing-in-web-browsers/

New #Dillo plugin to add reader mode support with rdrview.

https://github.com/dillo-browser/dillo-plugin-rdrview

@jn that would be very nice! I'll appreciate if you send some picture for the gallery: https://dillo-browser.github.io/gallery/index.html

Just read this post: "building dillo only takes ~20min" on a IBM ThinkPad 380Z from 1998, with a "powerful 233MHz Pentium II, and whopping 160 megs of RAM". Truly amazing! :D

https://luke8086.dev/netbsd-on-thinkpad-380z.html

@kev could you configure your nginx server to send content-type: image/webp for .webp images in your blog?, it is currently sending text/plain and failing to render in Dillo. Example: https://kevquirk.com/media/pages/blog/year-2-at-the-smallholding/05614e701c-1730903864/garage-then.webp

@gumnos yes, it would require the IANA to reserve .unix for UNIX sockets to avoid collisions.

The RFC specifies how a user can override a system-wide UNIX host by setting it in their own unix.hosts file (maybe at ~/.config/unix.hosts), which takes priority over /etc/unix.hosts.

Using "socket:" doesn't specify the protocol to use *inside* the socket. A single unix socket could serve multiple "hosts" via HTTP by using the Host: header. What problem does using the full path solve?

Here is a new #Dillo #RFC to support UNIX sockets in URLs. Comments?

https://dillo-browser.github.io/rfc/003-unix-sockets/

Now you can link to an specific line in a plain text file adding a line fragment like #L123. Not sure why this is not more common.

Friendly reminder that we are at #dillo channel in Libera.chat via IRC.

Support to open URLs using external tools just got merged. Now you can open a YouTube video directly from #Dillo.

You can add as many menu entries as you need and specify how the URL is passed to the external program in the configuration file.

See: https://github.com/dillo-browser/dillo/pull/326

#Dillo is now 25 years old!

Check out the special page for the anniversary: https://dillo-browser.github.io/25-years/

TIL that there is a MS-DOS fork of #Dillo that can run on a modern browser:

https://archive.org/details/msdos_dillodos