rodarima

7 ms·

1.
by rodarima 3mo ago
It can be browsed but to contact the seller you seem to need JS.
2.
by rodarima 4mo ago
> As the author of asciinema I'm flattered that Rodrigo considers asciinema as a potentially useful tool for this problem. Is nice :) > unless most Dillo hackers are terminal editor users My guess is that it is mostly the case, b
3.
by rodarima 4mo ago
> For BMPs, for example, determining whether the author intended 24-bit RGB or 32-bit RGBA sometimes requires decoding the full image and scanning to see whether any pixels' alpha bytes differ from the others, since "all 00&quo
4.
by rodarima 4mo ago
> I think what the author wants is something like Gemini instead of HTML, but that has its own set of problems. Yes and no. I want it to be simpler than HTML (which implies less features) but easy to parse. The problem with Markdown and
5.
by rodarima 4mo ago
> Pages that don't conform with the specification won't be rendered. I agree on what I wrote here. They will fail with an error indicating where the mistake is so you can correct it (more likely the tool that produced it). >
6.
by rodarima 4mo ago
Yeah, I avoided sharing it here because I could see that it would immediately backlash. I also didn't even consider adding a more elaborate "introduction" section because these are my quick notes on what it had in mind at tha
7.
by rodarima 4mo ago
> Browsers absolutely decode as much as they can, and if the file is corrupted halfway through you generally get garbling, not the entire image being replaced by "fuck off". The only case where that is so is if the browser can&
8.
by rodarima 4mo ago
Google drop the mask
9.
by rodarima 4mo ago
Author here. I agree that you cannot go from HTML to XHTML because users and UA devs will always go towards "it mostly works". However, I don't see it that clearly that this cannot be done since the start so that the expectat
10.
by rodarima 5mo ago
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&#x2F
11.
by rodarima 5mo ago
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.
12.
by rodarima 5mo ago
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:&#x2F
13.
Dillo Browser Release 3.3.0(dillo-browser.org)
196 points by rodarima 5mo ago|34 comments
14.
by rodarima 6mo ago
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).
15.
by rodarima 6mo ago
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.
16.
by rodarima 10mo ago
> 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.
17.
by rodarima 10mo ago
Yep, thats what I meant :)
18.
by rodarima 11mo ago
> I wrote about 3.1, 18 months ago Thanks for the article and for including all the references. We now adhere to https://semver.org/ as much as we can, where each of the three version numbers has a meaning, so it would b
19.
by rodarima 11mo ago
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
20.
by rodarima 11mo ago
Raph Levien wrote the original Gzilla browser of which Dillo was forked in late 1999: http://www.levien.com/gzilla/
21.
by rodarima 11mo ago
Many reasons, in no particular order: - It is extremely slow and resource intensive. Opening any link/page takes at least 3 seconds on my fastest computer, but the content is mostly text with images. - It cannot be used without JS (it
22.
by rodarima 11mo ago
Yes, but all those services have the same main problem: a single point of failure. They also don't work offline. I believe that storing the issues in plain text in git repositories synced across several git servers is more robust and f
23.
by rodarima 11mo ago
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://
24.
by rodarima 11mo ago
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/Armadi
25.
by rodarima 11mo ago
Oldest I could find was an Ipaq 3700: https://dillo-browser.github.io/gallery/
26.
by rodarima 11mo ago
AFAIK Georg Potthast wrote a port that worked in DOS based on the work that Benjamin Johnson for Windows. I believe it was based on 3.0p4: https://www.bttr-software.de/forum/board_entry.php?id=10797 Unfortunately, none
27.
by rodarima 11mo ago
Yes, thanks for the reminder. This is what they write about: https://dillo.org/post-sitemap.xml At some point I should investigate if we can fill a complaint to get it taken down at least. Here is more info: https:/&#
28.
by rodarima 11mo ago
I wrote my own: https://git.dillo-browser.org/buggy/ It fetches the issues from GitHub and stores them in <number>/index.md in Markdown format, with some special headers. I then keep the issues in a git repo
29.
by rodarima 11mo ago
Not really. There was this list but it is outdated: https://dillo-browser.org/old/css_compat/index.html Probably the best indicator of which features are supported is to pass as many tests as possible from WPT tha
30.
by rodarima 11mo ago
Yeah, I tried to reach out to Google back when they introduced the JS-wall, but they seem to have an AI chatbot acting as a filter, so I didn't spent much energy. Later they also blocked other non-JS browsers like links or w3m, so I as

More ›