HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
dillo-browser
dillo
C++2024–2025
dillo-browser / dillo

dillo

NO LONGER UPDATED!, see https://dillo-browser.org/news/migration-from-github/. New repo at https://git.dillo-browser.org/dillo/

Web Development
Explore on GitHubRead Hacker News discussions
8Distinct people
15Mentions
0Explicit recommenders
1.2KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

NO LONGER UPDATED!, see https://dillo-browser.org/news/migration-from-github/. New repo at https://git.dillo-browser.org/dillo/

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 12:54:37 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month15 dated mentions

Observed mentions: 2024-01-02 21:55:08 UTC to 2025-11-05 21:45:25 UTC.

024682024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 8 mentions; 1 submissions, 7 commentsJan 20242024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-03-01 00:00:00 UTC to 2024-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-04-01 00:00:00 UTC to 2024-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-05-01 00:00:00 UTC to 2024-06-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-07-01 00:00:00 UTC to 2024-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-08-01 00:00:00 UTC to 2024-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-09-01 00:00:00 UTC to 2024-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-10-01 00:00:00 UTC to 2024-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsDec 20242025-01-01 00:00:00 UTC to 2025-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-02-01 00:00:00 UTC to 2025-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-03-01 00:00:00 UTC to 2025-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-04-01 00:00:00 UTC to 2025-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-05-01 00:00:00 UTC to 2025-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-06-01 00:00:00 UTC to 2025-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-07-01 00:00:00 UTC to 2025-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-08-01 00:00:00 UTC to 2025-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsNov 2025

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC817
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC101
Mar 20242024-03-01 00:00:00 UTC2024-04-01 00:00:00 UTC000
Apr 20242024-04-01 00:00:00 UTC2024-05-01 00:00:00 UTC000
May 20242024-05-01 00:00:00 UTC2024-06-01 00:00:00 UTC101
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC101
Jul 20242024-07-01 00:00:00 UTC2024-08-01 00:00:00 UTC000
Aug 20242024-08-01 00:00:00 UTC2024-09-01 00:00:00 UTC000
Sep 20242024-09-01 00:00:00 UTC2024-10-01 00:00:00 UTC000
Oct 20242024-10-01 00:00:00 UTC2024-11-01 00:00:00 UTC000
Nov 20242024-11-01 00:00:00 UTC2024-12-01 00:00:00 UTC101
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC000
Jan 20252025-01-01 00:00:00 UTC2025-02-01 00:00:00 UTC000
Feb 20252025-02-01 00:00:00 UTC2025-03-01 00:00:00 UTC000
Mar 20252025-03-01 00:00:00 UTC2025-04-01 00:00:00 UTC000
Apr 20252025-04-01 00:00:00 UTC2025-05-01 00:00:00 UTC000
May 20252025-05-01 00:00:00 UTC2025-06-01 00:00:00 UTC000
Jun 20252025-06-01 00:00:00 UTC2025-07-01 00:00:00 UTC000
Jul 20252025-07-01 00:00:00 UTC2025-08-01 00:00:00 UTC000
Aug 20252025-08-01 00:00:00 UTC2025-09-01 00:00:00 UTC000
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC000
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC312

What Hacker News says

15 sources
gregsadetsky·Nov 5, 2025
`brew install dillo` on Macs (and see [0] for other platforms) and then `dillo` starts up a 1.1Mb executable that is so freaking, shockingly fast. TIL I also learned that although the Google homepage renders beautifully, I need to "Turn on JavaScript to keep searching" [1] Wow, Google Maps is even snarky-ish about it: "When you have eliminated the JavaScript, whatever remains must be an empty page." (that's what appears! for real) I mean, what was I expecting. U+1F643. [0] https://github.com/dillo-browser/dillo/blob/master/doc/insta... [1] https://www.reddit.com/r/google/comments/1i3njv0/google_begi...
In Dillo, a multi-platform graphical web browser
anthk·Jun 5, 2024
As an ATOM N270 user: - Luakit it's faster Here's a guide in Spanish, but the content it's clear to guess. "pkg_add" it's for OpenBSD, but OFC you know how to get it under AntiX. https://gopher.floodgap.com/gopher/gw?=texto-plano.xyz+70+30... - Use this $HOME/.drirc: <driconf> <device driver="i915"> <application name="Default"> <option name="stub_occlusion_query" value="true" /> <option name="fragment_shader" value="true" /> </application> </device> </driconf> Use zram. I'd suggest using 1/3 of RAM as a compressed one: https://wiki.debian.org/ZRam Dillo fork: https://github.com/dillo-browser/dillo Use mpv+yt-dlp for media sites. $HOME/yt-dlp.conf: #start --format "best[height=480]" #end $HOME/.config/mpv/config #start ytdl-format=bestvideo[height<=?480][fps<=?3
Read the rest
0]+bestaudio/best vo=xv audio-pitch-correction=no quiet=yes pause=no vd-lavc-skiploopfilter=all #end Recommended: - mupdf - mocp for music - mosh - profanity for Jabber - sfeed+lynx for RSS - Mutt/Sylpheed for email - Catgirl for IRC - sxiv as the image viewer
In Running Linux on an Ancient Netbook
anthk·Feb 1, 2024
I'd put this dillo fork: https://github.com/dillo-browser/dillo On games, sgt-puzzles and bsdgames fit well, among nethack/slashem, DCSS and OFC Frotz too plus a few libre games (Spiritwrak and such). Slashem+BSDGames+3 adventures for Frotz would weight less than 20MB I think. Compressed, about 7. BTW, I'd ditch XMMS for Audacious; a Pentium 3/4 today would be more than enough to run it. BTW Visidata it's huge, use sc-im+Gnuplot. On browsers, felinks supports Gopher and Gemini too. Gopher has nice stuff as gopher://magical.fish, Gemini has similar places too.
In Damn Small Linux 2024
rodarima·Jan 15, 2024
The problem is fixed now in master. It was caused by an attempt to shutdown the SSL session (which requires sending data) in a closed file descriptor, which is handled different between OpenSSL (no thread error queued) and LibreSSL (badsectoracula was using LibreSSL, which queues a thread error), and later causes an assert to trigger as it was not expecting any error in the queue. See[1] for more details. [1]: https://github.com/dillo-browser/dillo/pull/59 Thanks again for the report, these type of issues are hard to reproduce without using different environments.
In Show HN: Resurrecting the Dillo browser
rodarima·Jan 9, 2024
Thanks for your DPI work. I tested the gemini plugin and works very well. My only complain is that it keeps asking to confirm new keys every time a new server is visited which causes a lot of friction to explore several gemini servers. I understand that is a tradeoff between usability and security, but I wish there was a better solution than that. For now I uploaded Charles plugin written in shell script[1], which always trusts the certificate. [1]: https://github.com/dillo-browser/dillo-plugin-gemini/ But I'm considering switching to the Go version if I can find a way to improve the UX. Also, I kindly ask you to add the tag "dillo-plugin" so you can make Dillo plugins easily discoverable by searching for the tag in GitHub[2]. [2]: https://github.com/topics/dillo-plugin > I believe that in recent versions of Dillo, even https is implement
Read the rest
ed as a DPI plugin. This was done initially[3] (before 2007) but it was moved to the browser itself[4] in 2016. [3]: https://github.com/dillo-browser/dillo/commits/afd2763caa56d... [4]: https://github.com/dillo-browser/dillo/commit/bf5a7783f4a192...
In Show HN: Resurrecting the Dillo browser
rodarima·Jan 3, 2024
> I used to test out sites on Dillo a lot to see if the experience was absolutely broken Thanks! That should be done more often :-) > Shame to see a project moving from a self-hosted Mercurial repository to a US-megacorparate-owned Git repository in Microsoft GitHub Agreed. I decided that it was a good starting point moving to GitHub as a first start, to increase the chances the project gets more visibility and hopefully attract more contributions. I also trust GitHub to be alive for at least 5 to 10 more years, so I can put a redirect notice on the main webpage. But yeah, I agree it would be better to self host or move to a federated forge. There is an issue to cover other options[1], but our current problem is that other forges like Codeberg don't have a way (as a free account) to run the CI pipelines in other platforms like MacOS. My i
Read the rest
dea was to eventually get hold on some real hardware so we can setup our own runners and also test in different architectures. Feel free to add other alternatives and I will take a look. [1]: https://github.com/dillo-browser/dillo/issues/39 Keep in mind also, that because the project was previously self-hosted (including the mail server) that created a gigantic single point of failure (which failed very badly) that I'm trying to avoid. > But at least the maintainer is committed to accepting email patches so folks aren’t required to create accounts / accept ToS with them. Yeah, I'm thinking in creating a mailing list for that purpose, but apart from sourcehut (at least on alpha) and googlegroups, I don't know that many places that offer one free of charge.
In Show HN: Resurrecting the Dillo browser
unwind·Jan 3, 2024
Cool, I remember the name Dillo from ... way back when, I guess. Interesting to see a mix of C and C++ in the same codebase, that always makes me curious if there is some internal/mental "pressure" to convert the C code to C++ since that does seem simpler in many ways if you're already using C++. Also, does anyone know why the functions have a (to me, incredibly random) "a_" prefix? Like this, from "dicache.h" [1]: void a_Dicache_init (void); DICacheEntry *a_Dicache_get_entry(const DilloUrl *Url, int version); void *a_Dicache_png_image(const char *Type, void *Ptr, CA_Callback_t *Call, void **Data); void *a_Dicache_gif_image(const char *Type, void *Ptr, CA_Callback_t *Call, void **Data); It's like a set of perfectly module-prefixed names, but then an additional prefix of "a_" has been added? Edit: moved a comma. [1]: https
Read the rest
://github.com/dillo-browser/dillo/blob/master/src/dicac...
In Show HN: Resurrecting the Dillo browser
gregsadetsky·Jan 3, 2024
Wow, this is so stunning. Thanks a lot Rodrigo, and obviously to the dillo team, Jorge Arellano Cid, etc.!! For others on Macs (I'm on an M1 under macOS 12.7), here's what worked for me: - start by following the mac installation instructions here [0], specifically `brew install` the suggested packages + openssl (I used version 3) - follow the "from git" installation instructions here [1] BUT, before running `./configure`, run these export commands [2] to make sure that the openssl files are found - `make`, then `sudo make install` (like in the good old days). then run `dillo`. - it just... works. and it's blazing fast. it's a 1.6mb binary, it supports ssl... it's brilliant. google search sorta works (with broken css). signing in to google is impossible without javascript..? yeah wow. a whole world to explore. THANKS! [0] https://github.co
Read the rest
m/dillo-browser/dillo/blob/master/doc/insta... [1] https://github.com/dillo-browser/dillo/blob/master/doc/insta... [2] https://stackoverflow.com/a/77749836
In Show HN: Resurrecting the Dillo browser
badsectoracula·Jan 3, 2024
Here[0], i submitted a bug report. The issue seems to be that some OpenSSL error isn't handled elsewhere, isn't removed from the error queue and the function with the assertion assumes the queue is empty. I put a breakpoint in ERR_put_error in the version that comes with openSUSE though there isn't much debug info there to be had so i don't know what the error is (perhaps building OpenSSL from source code with debug info and having Dillo link against it would help). I found where the error comes in Dillo's side (check the comment i made in the bug report) but i'm not sure how that'd be fixed (aside from draining the error queue :-P) as i don't know why these calls are made in the first place. [0] https://github.com/dillo-browser/dillo/issues/51
In Show HN: Resurrecting the Dillo browser
rodarima·Jan 2, 2024
> * w3m's bookmark system is implemented using local CGI; it seems Dillo's bookmarks are implemented as a dpi plugin too. Yeah, a lot of things [1] are implemented as DPI in Dillo. Some of the plugins implement "websites" like file:, vsource: and ftp: but others implement other features like the handling of cookies, downloads or bookmarks. As they are a different process, if you close the browser, the downloads continue. [1]: https://github.com/dillo-browser/dillo/tree/master/dpi > * w3m can use urimethodmap + local CGI to implement additional protocols. I guess DPI can do that too? (At least the custom man: scheme in dillo-plugin-man seems to indicate it can.) Yes, there is a file (~/.dillo/dpidrc) that associates the protocol to the plugin binary (like this "proto.man=man/man.filter.dpi"). There is also gemini: gopher: and even git: ava
Read the rest
ilable as external plugins. > I had no idea any browser supported this besides w3m. I mostly imitated w3m's design in my own project (which includes the twist that support for every protocol, including HTTP, is implemented on top of a similar plugin system); I guess I have a second reference point now :) In fact, not so long ago, the HTTPS protocol was implemented as a DPI plugin, but it was changed to be part of the browser.
In Show HN: Resurrecting the Dillo browser
rodarima·Jan 2, 2024Submission

Show HN: Resurrecting the Dillo browser

Hi, in mid 2022 the host dillo.org expired [0], taking down the website, mercurial repo, the mailing list and the email server used to reach the core developers of Dillo. Someone bought it and now serves a weird clone of the original page with missing content. [0]: https://news.ycombinator.com/item?id=32448104 I felt sad as I didn't want it to die, so I got a copy of the repo from my hard disk, uploaded it to GitHub and decided to do some maintenance on the code to at least keep the build working. After some time, the folks at Atari Forum decided to use my repo to port it to the Atari platform and they managed to do it [1]. [1]: https://github.com/dillo-browser/dillo/issues/34 That gave me some motivation to work a bit more on the project to prevent it from dying. So I created an organization under the name of "dillo-browser" and made a n
Read the rest
ew webpage [2] with a backup of the old one. [2]: https://dillo-browser.github.io/ With the help of Andreas Kemnade which had access to the original server, we managed to backup most of the stuff from the original website (including non-reachable pages) which I uploaded to the Archive. In the meanwhile, I combined the support for both OpenSSL (1.1 and 3) and mbedTLS (2 and 3) as well as proper CI with rendering tests. We now build Dillo for Ubuntu, FreeBSD and macOS! I also became familiar with the plugin mechanism in Dillo, which allows any program that uses the standard input and output to become a plugin registered to a given protocol (like file://...). I did a simple one (which is just a bash script) to read local manual pages which is handy to follow links to other pages [3], but check also the ones Charles E. Lehner did which are more advanced [4]. [3]: https://github.com/dillo-browser/dillo-plugin-man [4]: https://groups.google.com/g/dillo/c/WGEMg7AXN4o/ As of today, I'm unable to contact the main developer, Jorge Arellano Cid, which has not interacted with the mailing list for some years now. Jorge, if you read this, please contact with me (you can find my email in the git commits). Regarding the future of Dillo, I'm planning to (finally) do the 3.1 release after some testing, and for that it would be convenient to have the help of some users to get some feedback ;-) If you want to contribute, feel free to open a PR or send a patch (via GitHub or by email, I don't care). Check also the current issues and pull requests to see what is pending or already being working on. I will probably setup a mailing list at some point too. Thanks! Rodrigo.
599 points · Open discussion

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.