<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>minitech</author><text>&amp;gt; Also, the lack of a Javascript engine makes it a very secure browser. Whenever I try to open a link that I am suspicious of, I do so in dillo.&lt;p&gt;I would suggest using a Chromium or Firefox profile with JavaScript and webfonts disabled for this instead of questionably maintained C software that doesn’t have a sandbox for any of the complex and commonly exploited things it does (image decoding, HTML&amp;#x2F;CSS parsing, network protocols, local file access).</text><parent_chain><item><author>krylon</author><text>Given the circumstances, I am happy to read this. I own two ~2009 netbooks with Intel Atom N270 CPUs and 1GB of RAM each - running Firefox on those is ridiculous, whereas dillo will run very well on these.&lt;p&gt;I used to use dillo on my main desktop too, for browsing documentation that wasn&amp;#x27;t too heavy on CSS - having 20 to 40 tabs open would gobble up a lot of RAM in Firefox, whereas dillo happily stayed around 100MB no matter what I threw at it. My current desktop has enough RAM this not a concern any more, but I have fond memories of using dillo on memory-deficient machines and am a current user still.&lt;p&gt;Also, the lack of a Javascript engine makes it a very secure browser. Whenever I try to open a link that I am suspicious of, I do so in dillo.&lt;p&gt;So thanks to everyone who continues to work on this, I really appreciate the work you do! Dillo is a fine piece of software that I have enjoyed using for at least 15 years now, and I hope it will be around for many years to come! &amp;lt;3</text></item></parent_chain></comment><story><title>Show HN: Resurrecting the Dillo browser</title><url>https://dillo-browser.github.io/</url><text>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.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=32448104&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=32448104&lt;/a&gt;&lt;p&gt;I felt sad as I didn&amp;#x27;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].&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo&amp;#x2F;issues&amp;#x2F;34&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo&amp;#x2F;issues&amp;#x2F;34&lt;/a&gt;&lt;p&gt;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 &amp;quot;dillo-browser&amp;quot; and made a new webpage [2] with a backup of the old one.&lt;p&gt;[2]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;dillo-browser.github.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;dillo-browser.github.io&amp;#x2F;&lt;/a&gt;&lt;p&gt;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.&lt;p&gt;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!&lt;p&gt;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:&amp;#x2F;&amp;#x2F;...). 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].&lt;p&gt;[3]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo-plugin-man&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo-plugin-man&lt;/a&gt;
[4]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;groups.google.com&amp;#x2F;g&amp;#x2F;dillo&amp;#x2F;c&amp;#x2F;WGEMg7AXN4o&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;groups.google.com&amp;#x2F;g&amp;#x2F;dillo&amp;#x2F;c&amp;#x2F;WGEMg7AXN4o&amp;#x2F;&lt;/a&gt;&lt;p&gt;As of today, I&amp;#x27;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).&lt;p&gt;Regarding the future of Dillo, I&amp;#x27;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 ;-)&lt;p&gt;If you want to contribute, feel free to open a PR or send a patch (via GitHub or by email, I don&amp;#x27;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.&lt;p&gt;Thanks!
Rodrigo.</text></story>
<instructions>Your goal is to analyze the following comment and estimate how highly it will be upvoted by the Hacker News community.</instructions><comment><author>yjftsjthsd-h</author><text>I also like dillo, but just as an option - have you tried netsurf as well? Likewise very lightweight.</text><parent_chain><item><author>krylon</author><text>Given the circumstances, I am happy to read this. I own two ~2009 netbooks with Intel Atom N270 CPUs and 1GB of RAM each - running Firefox on those is ridiculous, whereas dillo will run very well on these.&lt;p&gt;I used to use dillo on my main desktop too, for browsing documentation that wasn&amp;#x27;t too heavy on CSS - having 20 to 40 tabs open would gobble up a lot of RAM in Firefox, whereas dillo happily stayed around 100MB no matter what I threw at it. My current desktop has enough RAM this not a concern any more, but I have fond memories of using dillo on memory-deficient machines and am a current user still.&lt;p&gt;Also, the lack of a Javascript engine makes it a very secure browser. Whenever I try to open a link that I am suspicious of, I do so in dillo.&lt;p&gt;So thanks to everyone who continues to work on this, I really appreciate the work you do! Dillo is a fine piece of software that I have enjoyed using for at least 15 years now, and I hope it will be around for many years to come! &amp;lt;3</text></item></parent_chain></comment><story><title>Show HN: Resurrecting the Dillo browser</title><url>https://dillo-browser.github.io/</url><text>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.&lt;p&gt;[0]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=32448104&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=32448104&lt;/a&gt;&lt;p&gt;I felt sad as I didn&amp;#x27;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].&lt;p&gt;[1]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo&amp;#x2F;issues&amp;#x2F;34&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo&amp;#x2F;issues&amp;#x2F;34&lt;/a&gt;&lt;p&gt;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 &amp;quot;dillo-browser&amp;quot; and made a new webpage [2] with a backup of the old one.&lt;p&gt;[2]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;dillo-browser.github.io&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;dillo-browser.github.io&amp;#x2F;&lt;/a&gt;&lt;p&gt;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.&lt;p&gt;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!&lt;p&gt;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:&amp;#x2F;&amp;#x2F;...). 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].&lt;p&gt;[3]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo-plugin-man&quot;&gt;https:&amp;#x2F;&amp;#x2F;github.com&amp;#x2F;dillo-browser&amp;#x2F;dillo-plugin-man&lt;/a&gt;
[4]: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;groups.google.com&amp;#x2F;g&amp;#x2F;dillo&amp;#x2F;c&amp;#x2F;WGEMg7AXN4o&amp;#x2F;&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;groups.google.com&amp;#x2F;g&amp;#x2F;dillo&amp;#x2F;c&amp;#x2F;WGEMg7AXN4o&amp;#x2F;&lt;/a&gt;&lt;p&gt;As of today, I&amp;#x27;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).&lt;p&gt;Regarding the future of Dillo, I&amp;#x27;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 ;-)&lt;p&gt;If you want to contribute, feel free to open a PR or send a patch (via GitHub or by email, I don&amp;#x27;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.&lt;p&gt;Thanks!
Rodrigo.</text></story>