necromancy / reborn of dillo 3.2.3

[nick65go]

main site: https://dillo-browser.github.io/

Dillo+ (Dillo-Plus) on https://github.com/crossbowerbt/dillo-plus
as multi-protocol browser  (Gopher, Gemini), with Reader mode CSS style & DLS (Dillo Local Script) for Zip, EPub, RSS.
Has quick searching engines, or External media player.

[gadget42]

as far as I can tell after reviewing the currently available material(s) the correct current version of Dillo is 3.0.5

the Dillo-Plus version is currently 3.2.3(as per https://github.com/crossbowerbt/dillo-plus)

here is a link to the latest about.c file:
https://github.com/dillo-browser/dillo/blob/master/src/IO/about.c

also for historical reference:
https://forum.tinycorelinux.net/index.php/topic,25832.msg172775.html#msg172775

[nick65go]

Right, so maybe the admin of the forum could change the title, to be like: "re-born of Dillo 3.0.5 as Dillo-plus 3.2.3"
Like Phoenix bird, but I do not believe in re-incarnation, so there is no re-born, but just born as a new instance. Hm.. semantics .. semantics.
The news is that some old software was "improved" / "modernized" whatever. Anyway is one of the few that still use FLTK. When almost 99% (estimated) of Tinycore is NOT using so much FLTK.

(FLTK is mostly for base apps., the carrot initial attraction, then many GUI are gtk1/2/3, QT etc).

Anyway, news is also that FLTK 1.4 starts to use Wayland server... in the world of UEFI...

[Juanito]

Anyway, news is also that FLTK 1.4 starts to use Wayland server... in the world of UEFI...

I was playing around with an fltk-1.4 wayland only version of tinycore a while ago..

[vinceASPECT]

Hello  forum,

It is good to have  a good efficiency free web browser that serves a purpose of Worldwide web information  & basic  services such  as communication   .......i think. "Links"  graphical web browser" version . Is. Very. Good  for that

......"Twibright".....company

Thanks.

C

[neonix]

Is it possible to modify Dillo that every webpage was opened in new window. Sometimes Dillo crush without a reason, or becouse lack of free RAM. There is also memory leak problem with this browser.

[nick65go]

Maybe you could report a bug to the new developer in charge on git?
The DPI system of protocol/extension is the future for dillo (3.1+). It is a shame the developers do not cooperate between dillo/dillo-plus etc.

EDIT: "lack of free RAM", really? Maybe you did know that extensions DO RUN even if/after dillo is closed (check with top).
The new version 3.1 rc+ seems (git says) solved the problem of random crashes (because some SSL/TLS linked libs, about SNI --whatever this acronym is).

[nick65go]

from https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo*.info
there are 2 versions of dillo, none of them up-to-date in TC15, as recent dillo 3.1+ of April 2024
the patched one (in Tinycore) was dillo 3.0.5, but not dillo 3.1.0-rc1 (https://dillo-browser.github.io/latest.html)

https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo-beta.tcz.info
Title:          dillo-beta.tcz
Description:    Dillo - the fast and light web browser
Version:        3.1 (20181005)
Change-log:     2019/07/20 v3.0.5
Current:   2020/02/10 v3.1 (neonix) TC 10.x
==
https://mirrors.dotsrc.org/tinycorelinux/15.x/x86_64/tcz/dillo.tcz.info
Title:          dillo.tcz
Description:    Dillo web browser
Version:        3.0.5 + patches
      2020/02/20 fixed openssl-1.1.1 dependency (neonix) TC11.x
Current:   2024/04/02 Use OpenSSL 3.2 & patched for SNI support (CNK) TC14.x


FYI: for me it did not crash, in WSL2 (Windows Subsystem for Linux) for Alpine Linux.

[Dies Irae]

Is it possible to modify Dillo that every webpage was opened in new window. Sometimes Dillo crush without a reason, or becouse lack of free RAM. There is also memory leak problem with this browser.

the usual 2 dillo in extensions by design refuse to drop cache. While i'd want this as an option, the argument is that a number of folk don't want it to drop cache when you close a tab, couse then they'd have to redownload some webpage/css file. Combined with the risk for crash, you want to run 2 instances of dillo: one, you kill regularly (if it didn't crash already), to get your ram back. The other you run for pages you actually wanted to keep open (and didn't crash your 'temp' dillo).

[CNK]

I think I noticed some crashes with the dillo-beta.tcz extension on x86, which may have been some of the issues fixed since then in the 'beta' code. I haven't had any crashes with the current or previous dillo.tcz extension for x86_64 for Dillo 3.0.5.

I happened to submit the updated dillo.tcz extension just before the new release candidate for 3.1.0 came out, but before doing a new extension for that it seems sensible to wait until the full 3.1.0 release which the announcement said was expected in a few weeks. I've also reported a few bugs on the Dillo mailing list that might be fixed before then.

Since the dillo-beta.tcz extensions are for the 3.1.0 release which is hopefully happening soon, that will make them redundant so perhaps they should be removed then? I intend to build a dillo.tcz extension for x86 and x86_64 when it's fully released, unless someone else wants to do it (I checked that Neonix didn't want to before I submitted the new dillo.tcz for x86_64).

@nick65go The DPI system is supported in all the Dillo variants and versions, and is how the dillo-gopher.tcz and dillo-gemini.tcz extensions work.

@neonix If you're running out of RAM then Dillo might not be crashing but getting killed by the Linux kernel because it needs free RAM to do something else to keep the system running. I really like the cache because I use mobile broadband for my home internet, but a maximum cache size setting in Dillo would be useful in cases like yours. It's probably a fair bit of work to implement that properly though. Modern webpages that load lots of massive images expecting them to be scaled down with CSS are also a problem if RAM is limited.

[neonix]

Here's few thouths about this browser.

Version 3.0.5 and 3.1 are two different animals (I like armAdillo name more than Dillo) with different issues and bugs.

I find this tip in
https://news.ycombinator.com/item?id=38847613

hange the user agent to this one at ~/.dillo/dillorc:
      http_user_agent="Mozilla/5.0 (PSP (PlayStation Portable); 2.00)"
Then a lot of sites will load a compatible version.

On Wikipedia talk section there's interesting discusion about this browser.
https://en.m.wikipedia.org/wiki/Talk:Dillo

New version of Damn Small Linux use Dillo as main web browser.
https://www.youtube.com/watch?v=lKLeqqqNHYU

Tiny Desktop Linux also has Dillo.
https://www.youtube.com/watch?v=FJ6m0D4h_Fs

Some years ago I use hv3 web browser with polipo proxy that speed up connection.

I also used AnalogX Fastcache when I was WinMe user.

As long as there's an Internet, everyone is going to want to do things faster. Browse the web, ping servers, download files, whatever. Every time you go to a new website, or a website you haven't been to in a day or so, your computer needs to locate the server again using DNS. Each DNS request can take anywhere from 50 milliseconds, to even a second or more, but most are in the 100 to 200 millisecond range. Want to save a couple hundred milliseconds? Probably not, but what about a couple million or more? That's what AnalogX FastCache is all about.
    AnalogX FastCache is a caching DNS server that runs on your local machine and handles any DNS request that your computer makes, from Internet Explorer to your favorite FTP client. Once a query is made, FastCache will override the normal timeout for the item with one that you specify, so instead of saving a query for a couple of seconds, it can save it for a couple of days. Now every time you ask for it again while it's in the cache, it gives it to you instantly.

If Dillo could save rendered webpages as jpg, I would save a lot of RAM and time.

[neonix]

Maybe you could report a bug to the new developer in charge on git?
The DPI system of protocol/extension is the future for dillo (3.1+). It is a shame the developers do not cooperate between dillo/dillo-plus etc.

EDIT: "lack of free RAM", really? Maybe you did know that extensions DO RUN even if/after dillo is closed (check with top).
The new version 3.1 rc+ seems (git says) solved the problem of random crashes (because some SSL/TLS linked libs, about SNI --whatever this acronym is).

It's hard to recreate a bug in web browser that doesn't have history. I know it was developers decision to create private browser without history, but it's standard nowadays. Sometimes I have to use kil -9 to clean all zombie instances.But where are the main developers? There are many forks.