Back to News
Advertisement
Advertisement

⚡ Community Insights

Discussion Sentiment

80% Positive

Analyzed from 417 words in the discussion.

Trending Topics

#dillo#https#google#browsers#search#engines#com#browser#www#age

Discussion (18 Comments)Read Original on HackerNews

userbinatorabout 2 hours ago
Unfortunately even Google started requiring JS, which was a huge attack against small browsers and the open web.
rodarimaabout 1 hour 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/posts/2021/03/10/search-engines-with-own-...

nicoburnsabout 2 hours ago
Yep, https://html.duckduckgo.com works well in such browser though :)
childintime44 minutes ago
But does it require ES6? Javascript was quite minimal in the early days. It doesn't need a JIT, in fact I'd prefer it not to be.
shevy-javaabout 2 hours ago
Google at this point kind of controls the www. Now, strictly speaking that statement is not true, but it now feels as if Google sits in so many areas that are important for the www; chrome is just the most obvious one.
jmclnxabout 2 hours ago
I use dillo a lot, congratulations!

With these age verification laws and depending upon what Firefox does, dillo could very well be the go-to browser on Linux and BSD. If these laws hit us and Firefox adds logic to verify one's age, I will be 100% dillo.

shevy-javaabout 2 hours ago
Understandable but I think the age sniffing laws are much more profound. It's fascinating to see how quickly all countries succumb to them right now.

People may not believe it right now, but I think anonymously browsing the www will be a thing of the past in some years. People should see the concomitant attacks on VPNs - this is all concerted, not "isolated accidents". We need to make the flow of money obvious - I am fed up of being controlled by lobbyists.

pureagave28 minutes ago
i totally misread the title of this post. What is wrong with me?
elchabout 2 hours ago
It’s a shame that in my case trying to use Dillo here (HN) keeps returning 429, something that doesn’t happen with "full‑size" browsers (JS?).
rodarimaabout 2 hours 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://git.dillo-browser.org/dillo/

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

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

elchabout 2 hours ago
I meant browsing HN with Dillo. And it is not Dillo's fault. Other not "mainstream" browsers have the same problem.
nicoburnsabout 1 hour ago
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/

rodarimaabout 2 hours 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.

leoalejobabout 1 hour ago
that's cool!
shevy-javaabout 2 hours ago
Am I the only one who has to giggle when reading that name?

I know people have somewhat related thoughts about the image editor called GIMP.

userbinator29 minutes ago
They missed a great opportunity to name the "Control via UNIX socket" section "Teledillonics".
johnwheelerabout 1 hour ago
Yeah, I was going to say the same thing, kind of an unfortunate name. Why? It makes you think of a DILD*. Then you have to remind yourself, they probably mean armadillo.