← Feed

Posts

• Post #4120523

  Sadly, the SVG library Nanosvg is now slop. We embed a sane version in #Dillo to read Wikipedia math which will be kept LLM-free. Human-made changes will continue to be cherry-picked from upstream.

• Post #3907322

  Added experimental support to solve go-away and Anubis challenges to the "Fix page" script with a small C helper program to compute the proof-of-work. You will need to enable session cookies in ~/.dillo/cookiesrc (DEFAULT ACCEPT_SESSION) so that the challenge cookie is saved. https://git.dillo-browser.org/plugins/actions/about/

• Post #3584060

  New link navigation mode using the keyboard (coming soon). Use n and N to select a link from the viewport and press Enter to open it. The hjkl keys are also remapped to navigate around, similar to vim.

• Post #3317854

  I have prepared a directory of sites that work well with #Dillo with a focus on human crafted sites to help new users find useful content: https://dir.dillo-browser.org/ There is A LOT of content to explore, so be mindful of the time when entering the rabbit hole. You can also suggest new sites to be added at the end of the page.

• Post #2173500

  After taking a quick look at the "Prompt API" document, I decided to write some design notes towards a fork of the #Web. On forking the Web https://dillo-browser.org/lab/web-fork/

• Post #1963513

  Added support in the "Fix page" script for GitHub issues to read the comments directly from Dillo. They are buried in the HTML itself as JSON. Please migrate away from GitHub if you can, this is awful. One option is Codeberg, which renders the issue pages in plain HTML. https://git.dillo-browser.org/plugins/actions/about/

• Post #1963512

  #Dillo is also mirrored by the Software Heritage non-profit (@swheritage). Here is the source code: https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://git.dillo-browser.org/dillo And our issue tracker (perks of plain text): https://archive.softwareheritage.org/browse/origin/directory/?origin_url=https://git.dillo-browser.org/bugtracker Along with our PGP signed commits, it should have the same level of trust as our own git server.

• Post #1703237

  #Dillo 3.3.0 finally released! 🥳 😎 https://dillo-browser.org/release/3.3.0/

• Post #1626565

  #Dillo on the Luckfox Pico Mini board (ARMv7/RISC-V CPU with 64 MiB of RAM), found on YouTube: https://www.youtube.com/watch?v=FQoGpyFMgKQ

• Post #1550717

  Introducing the Dillo Lab, a new section in our website for experimental ideas and features. https://dillo-browser.org/lab/

• Post #1233093

  Dillo 3.3.0-rc1 released 🥳 Let us know if you encounter any issues to fix them before the 3.3.0 release! https://dillo-browser.org/release/3.3.0-rc1/

• Post #1073797

  The nice 0x0.st paste service has disabled new uploads: % curl -F 'file=@/dev/null' https://0x0.st uploads disabled because it’s been almost nothing but AI botnet spam for the past few months. will be back with a few changes at some point. no ETA. Do you know any other paste service that works without JS (i.e. using curl) in the meanwhile?

• Post #1010026

  Kind reminder that our #Dillo git repository is distributed among three different sites, all in sync: - https://git.dillo-browser.org/dillo - https://codeberg.org/dillo/dillo - https://git.sr.ht/~dillo/dillo Currently #Sourcehut is fighting a DDoS and the service is spotty: https://status.sr.ht/issues/2026-04-06-ddos-attack/ This is precisely why we have chosen a replicated set of git servers.

• Post #855733

  @c64whiz @rl_dane I reported it back to Edegesuite (Akamai) last year (AKAM-CASE #F-CS-9320406), but they have not replied since then. Last time it was caused by the User-Agent header (http_user_agent) and changing it worked, but I haven't changed it now (Dillo/3.2.0) and it still works for me. See: https://bug.dillo-browser.org/327/

• Post #855732

  "If you are a normal visitor and you expected actual content instead of this page, then use a normal, up-to-date browser. It's that simple. [...] You'll have to use another, normal browser. I'm sorry for the inconvenience." Is 2026 the year of accurate bot protection?

• Post #855731

  Hi @brewsterkahle, Is there a reason why the Archive.org (also searching the Wayback Machine) cannot be used without JS? It excludes people with older computers from using the site as modern web browsers require a lot of resources. It used to work in the past, but now it doesn't anymore. Could you consider keeping at least the search and download functionality without requiring JS? Thanks!

• Post #855730

  Every. Damm. Time. #NoJS

• Post #855728

  On forking the #Web: - How do we make sure it doesn't end up like this one? - Are you willing to pay directly or you prefer to continue paying indirectly via surveillance? - Why leaving older machines out wouldn't be considered discrimination? - What are your accessibility favourite DOIs? Treat for thought: https://sessa.bandcamp.com/album/pequena-vertigem-de-amor

• Post #855726

  Just fixed a big blocker for FLTK >= 1.4. Blurry fonts were caused by a half pixel misalignment bug in FLTK which broke the font hinting leading to poor readability. Should be fixed in next FLTK 1.4.5 release. I was not expecting to having to follow this whole font rendering pipeline rabbit hole. I'm surprised how little information there is on the Web about this topic, maybe I write more details later.

• Post #855725

  New commits are now signed with my OpenPGP key so they can also be trusted when cloned from other git mirrors. https://keys.openpgp.org/search?q=32E65EC501A1B6FDF8190D293EE6BA977EB2A253