HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
crossbowerbt
dillo-plus
C++2023–2026
crossbowerbt / dillo-plus

dillo-plus

A lightweight web browser based on Dillo but with many improvements, such as: support for http, https, gemini, gopher, epub, reader mode and more...

7Distinct people
7Mentions
1Explicit recommenders
186GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A lightweight web browser based on Dillo but with many improvements, such as: support for http, https, gemini, gopher, epub, reader mode and more...

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

I love Dillo. But I have lately been trying Dillo+ which adds some quality of life features. Have these features been incorporated into the existing Dillo?…

system7rocks used a recommendation phrase. One indexed comment matches. This is a phrase match, not a verdict.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:56:33 AM 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 month7 dated mentions

Observed mentions: 2023-07-28 21:36:36 UTC to 2026-02-27 13:10:37 UTC.

0122023-07-01 00:00:00 UTC to 2023-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 20232023-08-01 00:00:00 UTC to 2023-09-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-09-01 00:00:00 UTC to 2023-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-10-01 00:00:00 UTC to 2023-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-11-01 00:00:00 UTC to 2023-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2023-12-01 00:00:00 UTC to 2024-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-01-01 00:00:00 UTC to 2024-02-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2024-02-01 00:00:00 UTC to 2024-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 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): 2 mentions; 0 submissions, 2 comments2024-06-01 00:00:00 UTC to 2024-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 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 commentsOct 20242024-11-01 00:00:00 UTC to 2024-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2024-12-01 00:00:00 UTC to 2025-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2025-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): 1 mentions; 0 submissions, 1 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 2026

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
Jul 20232023-07-01 00:00:00 UTC2023-08-01 00:00:00 UTC101
Aug 20232023-08-01 00:00:00 UTC2023-09-01 00:00:00 UTC000
Sep 20232023-09-01 00:00:00 UTC2023-10-01 00:00:00 UTC000
Oct 20232023-10-01 00:00:00 UTC2023-11-01 00:00:00 UTC000
Nov 20232023-11-01 00:00:00 UTC2023-12-01 00:00:00 UTC000
Dec 20232023-12-01 00:00:00 UTC2024-01-01 00:00:00 UTC000
Jan 20242024-01-01 00:00:00 UTC2024-02-01 00:00:00 UTC101
Feb 20242024-02-01 00:00:00 UTC2024-03-01 00:00:00 UTC000
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 UTC202
Jun 20242024-06-01 00:00:00 UTC2024-07-01 00:00:00 UTC000
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 UTC000
Dec 20242024-12-01 00:00:00 UTC2025-01-01 00:00:00 UTC101
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 UTC101
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC101

What Hacker News says

1 sources
I'd be ok with it if it's possible to use all the insights and software from after that, we'd just be constrained by the hardware - the Amiga 4000, Apple Mac Quadra 840av 128 MB or a Pentium 66 MHz or the 486 DX2-66 with 64 MB ram. On the Amiga4000 and Apple you could run their 'native' OS, or you could run a modern day NetBSD or a BeOS version (HaikuOS wouldn't run). On the Pentium-66, modern Freedos would run, Windows 3.11+win32s+calmira, Windows98SE, Windows2000sp5, XPlite, NetBSD and perhaps even an absolutely stripped down Linux 6 kernel with all the features that would be handy. You could program in a modern i586 build FreePascal, Zig, Lua, juniper, micropython/shedskin, mruby/natalie, picoruby, juniper - perhaps a low memory JVM could run (OpenJDK 8 or JamVM). It'd be possible to use sqlite, raylib and r3d-freepascal for efficient
Read the rest
3D games/apps next to Quake/Darkplaces, Doom2/GZDoom, Duke3D, Counterstrike 1.5, Halflife, perhaps Unreal1, Irrlicht and FTEQW. Modern LambdaMOO's Toastunt/Moor could be made to run and inform6 and tads3 interactive fiction compilers. Fairy-Stockfish could be compiled - so enough creativity for gaming. I am just worried about getting Vassal, the java boardgame game engine to run comfortably... but the resolution would be pretty low to play many boardgames comfortably: the highest ATI card could drive 1280x1024. I would really like to use it so I don't have the real world board game setup time. Keldons Race for the Galaxy would compile and run though. For internet, Dillo+ supports https, gemini and gopher. https://github.com/crossbowerbt/dillo-plus This can also be used to browse zim offline wikipedia files with kiwix-serve. Now my only real problem is that we wouldn't have GenAI - probably EVER - would that be a blessing or a curse? --- Handy Linux kernel 6 tweaks for low memory situations if you don't want to run NetBSD (which perhaps would be the best choice): * zram + zstd zram creates a compressed block device in your RAM. To the OS, it looks like a regular swap partition, but it lives entirely in memory. When your 64MB fills up, the kernel sends data to /dev/zram0. The data is compressed (usually 3:1 ratio) and stored back in a small slice of your RAM. Version 6.19 includes better compression ratios and rebalancing. It prevents the CPU from over-working itself on decompression. * zswap + zstd zswap is a front-end for a physical swap file on your hard drive. It intercepts pages headed for the hard drive, compresses them, and keeps them in a RAM pool. If that pool gets too full, it evicts the oldest compressed data to the actual disk. Starting in 6.18, zswap transitioned to using the zsmalloc allocator by default. This reduces "internal fragmentation," meaning it packs those compressed bytes tighter. * frontswap API that allows the kernel to intercept swap-outs and store them in a transient memory pool; it works with Zswap to keep the system responsive during high load. * Maple tree Replaces old "Red-Black trees" for memory management; it reduces the CPU cycles needed to find data in RAM. * SLUB sheaves A modern memory allocator optimization that packs small objects into "sheaves" to reduce fragmentation. * CONFIG_SLOB_BERBER A specialized 2025 backport of the old "SLOB" allocator; a memory-efficient way to handle kernel objects, saving roughly 1-2MB of overhead compared to the standard SLUB used in modern PCs. * Ext4 without journaling Disable the "Journal" to save RAM and disk writes; it provides the best file-allocation speed without the memory overhead of Btrfs. * Reiser4 patch An efficient file system for small files; it packs them directly into the tree nodes, which saves disk space and reduces I/O. * KSM (Kernel Shared Memory) Scans RAM for identical pages (like duplicate library code) and merges them into one; it’s a "free" RAM upgrade if you run multiple instances of the same program. * Very High Frequency (VHF) HZ Tuning Manually setting CONFIG_HZ to 100 (instead of the modern 1000); this reduces the number of times the CPU "wakes up" per second, saving precious cycles for actual work. * DevTmpfs Automates device node creation entirely within the kernel; it saves you from running a heavy udev or mdev daemon in userland, freeing up roughly 2–5MB of RAM. * LZ4 Compression for Kernel/Initramfs Using LZ4 instead of xz, gzip or zstd for the kernel image.
In Dear Time Lords: Freeze Computers in 1993

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.