Help. Suis en train de déployer un nouveau design de mon blog ultra minimaliste. Je cherche volontaires pour capturer cette page sur Windows, Linus, Androïd: https://tcrouzet.com/2025/11/10/the-slow-web-is-faster/ (idéal en mode inspection avec affichage mobile sélectionné). Je veux voir comment les polices systèmes rendent hors du monde Apple!!!
alcinnz
boosted
Here is a new proposal on how to include OpenPGP signatures in HTML documents and verify them from the browser itself:
https://dillo-browser.org/rfc/006-signatures-html/
It shouldn't be too hard to implement in #Dillo and offload the verification to an external program like GnuPG.
CC @tomasino
Here is a new proposal on how to include OpenPGP signatures in HTML documents and verify them from the browser itself:
https://dillo-browser.org/rfc/006-signatures-html/
It shouldn't be too hard to implement in #Dillo and offload the verification to an external program like GnuPG.
CC @tomasino
｢ Dillo is a multi-platform graphical web browser, known for its speed and small footprint, that is developed with a focus on personal security and privacy. It is built with the FLTK 1.3 GUI toolkit ｣
Dillo, a multi-platform graphical web browser
https://github.com/dillo-browser/dillo
#HackerNews #Dillo #browser #multi-platform #web #browser #open #source #technology
So... I was fixing some problems with @Mastodon notifications in the bloat client to use it with #Dillo when I accidentally visited the "dismiss notifications" (/notifications/clear) enpoint assuming it would mark them as read, not erase them!?
May be a good idea to change the documentation to "Erase all notifications". In the meanwhile, I would need to repopulate some to continue testing :-)
Michael Dexter
and 1 other
boosted
Rewrote the bug tracker in C
https://git.dillo-browser.org/buggy
Now it is... checks notes... 150 times faster rendering the output. It only takes half a second rendering the 450+ issues or <50ms when updating one issue alone on the Atom N455 CPU.
With the right encantation of entr(1) and kill -USR1 we should get near realtime edit on #Dillo.
Rewrote the bug tracker in C
https://git.dillo-browser.org/buggy
Now it is... checks notes... 150 times faster rendering the output. It only takes half a second rendering the 450+ issues or <50ms when updating one issue alone on the Atom N455 CPU.
With the right encantation of entr(1) and kill -USR1 we should get near realtime edit on #Dillo.
Looking for a lightweight CLI fedi/mastodon client while I fix brutaldon OAuth on #Dillo.
Preferably with _very low_ RAM usage.
For reference, toot(1) (written in Python) uses more than three times as much memory as Dillo.
d1
and 4 others
boosted
Good news, we have a new website on EU soil 🎉
And a Git web frontend (cgit) that works well with #Dillo:
https://git.dillo-browser.org/
If all goes well, we will be moving the rest of the components away from GitHub.
Many thanks to all the donors that have made this posible, hopefully we can keep the lights on for some more years:
alcinnz
boosted
All bug trackers seem to be too complicated, so I made one myself in less than 300 lines. I imported the issues from GitHub and it seems to work well in #Dillo and #links2.
https://bug.dillo-browser.org/
Issues are stored in plain Markdown files with some special headers in a git repository. They get rendered to HTML when pushing a new commit to the bugtracker repo.
The whole thing is less than 300 lines of shell script and awk. It uses no javascript or databases.
The source code of the previous issue, showing simple headers and markdown syntax.
A issue rendered in Dillo with the headers and code fences for snippets.
The same index page rendered in links2
Main bug tracker index page rendered in Dillo
All bug trackers seem to be too complicated, so I made one myself in less than 300 lines. I imported the issues from GitHub and it seems to work well in #Dillo and #links2.
https://bug.dillo-browser.org/
Issues are stored in plain Markdown files with some special headers in a git repository. They get rendered to HTML when pushing a new commit to the bugtracker repo.
The whole thing is less than 300 lines of shell script and awk. It uses no javascript or databases.
The source code of the previous issue, showing simple headers and markdown syntax.
A issue rendered in Dillo with the headers and code fences for snippets.
The same index page rendered in links2
Main bug tracker index page rendered in Dillo
alcinnz
boosted
Just patched WRP to output the resulting HTML after JS is processed in a remote machine running headless Chromium as renderer. I then added a #Dillo plugin to make it easier to use.
The result is that many websites behind a JS wall now become readable in this old notebook.
Another example showing fosstodon Dillo profile being loaded via WRP
Another segment of the page under the WRP plugin, now displaying a list with links and tables.
Same page loaded using the WRP proxy now is displayed, showing a schematic.
Broken page with "You need to enable Javascript to view this site"
Good news, we have a new website on EU soil 🎉
And a Git web frontend (cgit) that works well with #Dillo:
https://git.dillo-browser.org/
If all goes well, we will be moving the rest of the components away from GitHub.
Many thanks to all the donors that have made this posible, hopefully we can keep the lights on for some more years:
Just patched WRP to output the resulting HTML after JS is processed in a remote machine running headless Chromium as renderer. I then added a #Dillo plugin to make it easier to use.
The result is that many websites behind a JS wall now become readable in this old notebook.
Another example showing fosstodon Dillo profile being loaded via WRP
Another segment of the page under the WRP plugin, now displaying a list with links and tables.
Same page loaded using the WRP proxy now is displayed, showing a schematic.
Broken page with "You need to enable Javascript to view this site"