#Tag
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 :-)
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.
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:
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.
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.
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.
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.
@rl_dane I'm still waiting for the motivation to learn Ruby ^^' https://github.com/mastodon/mastodon/issues/34241
I'm surprised that GoToSocial seems to be working well. I might submit a patch to fix the layout is not all over the place in #Dillo.
@rl_dane I'm still waiting for the motivation to learn Ruby ^^' https://github.com/mastodon/mastodon/issues/34241
I'm surprised that GoToSocial seems to be working well. I might submit a patch to fix the layout is not all over the place in #Dillo.
Me in 2002: Dillo looks nice, and is way faster than Mozilla, but I don't think I can ever use it as my main browser.
Me in 2025: Dillo go brrrrr! XD
Me in 2002: Dillo looks nice, and is way faster than Mozilla, but I don't think I can ever use it as my main browser.
Me in 2025: Dillo go brrrrr! XD
A space for Bonfire maintainers and contributors to communicate
