The Google index is still accessible from many other "proxy search engines" that still work without JS, one example is Startpage.

See the nice list from Seirdy for more details on search engines: https://seirdy.one/posts/2021/03/10/search-engines-with-own-...

First thing I see when I try to visit Startpage, for probably the first time ever, is "Our system has detected the type of high-volume traffic coming from your internet connection that is normally associated with bots and scrapers." WTF. Total BULLSHIT. I have accessed that site precisely ZERO times from this IP. Now it will be one, and the last time I ever try.

There are no special rules against modern browsers. Can you reproduce it systematically?, if so, any chances you can paste the HTTP headers?

In any case, apart from our cgit instance we have mirrors in Codeberg and SourceHut:

- https://git.dillo-browser.org/dillo/

- https://codeberg.org/dillo/dillo

- https://git.sr.ht/~dillo/dillo

I meant browsing HN with Dillo. And it is not Dillo's fault. Other not "mainstream" browsers have the same problem.

Ahh, I see. Yes, I also see it sometimes, for those cases the "Mimic Chrome" workaround usually fixes it.

I assume is a side effect of abusive crawlers compounded with Dillo headers not being very common.

Very possible. I was too lazy to investigate.

BTW Thanks for all fixes, especially this one https://bug.dillo-browser.org/511/. Dillo (3.2.0) crashed quite often on my system because of this bug. I hope I will compile and test the new release soon.

I can browse HN fine with both Servo [0] and Blitz [1] (the latter of which is no-JS like Dillo). So I think there might be something Dillo-specific going on here.

[0]: https://github.com/servo/servo/

[1]: https://github.com/DioxusLabs/blitz/

Amazing that the minimal version works in Dillo, except for the categories menu which uses JS (using a form and submit button inside a noscript tag would work as a fallback).

Thanks a lot for considering no-JS browser like Dillo, in the current web hellscape is certainly a difficult task. I checked and it works well in Dillo on my end.

> The post does not mention CI anywhere else, are they doing anything with it, keeping it on GitHub, or getting rid of it?

Yes, we have our own CI service. It is not public for now.

Yep, thats what I meant :)

Yes, we did some experiments with pledge and landlock, but we need to redesign some parts to be able to properly isolate them into separate processes first.

In the short term you can disable CSS or images from the menu. You can also disable specific image decoders from the configuration with the "ignore_image_formats" option.

In 2007 it was moved to Mercurial which I then exported to git when the hg server went down. The history from 2002-2007 was lost (I believe SVN), if someone still has a copy please send it to us. See the missing section:

https://dillo-browser.org/release/3.1.0/commits-author.png

The initial release was around the 15th of December, 1999. It's going to be 26 years ago: https://dillo-browser.org/25-years/index.html

I used Dillo in 2001-2002 with the PlayStation 2 Linux kit. With 32MB of RAM for Linux, and 4MB for the graphics. It worked really well despite the CPU was 294MHz (MIPS R-5900, two-way in-order CPU, with SIMD unit, and only one hardware thread, having two auxiliary vector units as companions).

Huh, somehow I had the idea that Raph Levien wrote it. The PNG here says corvid, Jeremy Henty, Johannes Hofmann, Jorge Arellano Cid, Rodrigo Arias Mallo (which is presumably you), Sebastian Geerken, and "other".

It's good to see that it's active again!

Raph Levien wrote the original Gzilla browser of which Dillo was forked in late 1999: http://www.levien.com/gzilla/

Oh, that's probably what I was thinking of. Thanks!

Jorge originally said "Dill-O" in a video, but I almost always say "Diyo" because I'm Spanish and the word comes from the Spanish word "armadillo": https://en.wikipedia.org/wiki/Armadillo

Oldest I could find was an Ipaq 3700: https://dillo-browser.github.io/gallery/