- Dillo-dev - lists.mailman3.com

Error when opening local html file

by Nikolas Nyby

Hello, I couldn't find a bug log for this already, or maybe I am doing something wrong. On current git master, I add this to the address bar: file:///home/nik/Documents/margin-test.html The file fails to load. Also, when using the menu: File -> Open File... dialog, which inserts this into the address bar: file:/home/nik/Documents/margin-test.html and displays the error: ERROR: can't start dpid daemon (URL scheme = 'file')!

July 13, 2026

Re: Save link as... silent failure on gopher protocol

by Diego

Very thanks. I await. Chers Diego. El dom, 12 jul 2026 a las 21:46, Rodrigo Arias (<rodarima(a)gmail.com>) escribió: > Hi, > > On Thu, Jul 09, 2026 at 01:37:14AM +0200, Diego wrote: > >¿Can i have some feedback? ¿Do the patchs work for you? ¿do it seem a > >practical idea? ¿etc? > > Thanks, I received the patches but I haven't had time to look at this > yet, I have have it in my queue. > > Best, > Rodrigo. > > > > >cheers! > >Diego. > > > > > >El vie, 3 jul 2026 a las 14:17, Diego (<darkspirit5000(a)gmail.com>) > escribió: > > > >> Hello, I'm sending two patches with an idea to solve this problem. > >> It's a proof of concept that I'm offering to develop and complete, > >> although I have very little free time. > >> > >> The first patch works with the latest dillo release (3.3.0) but also > works > >> with the current repository. > >> It implements changes in dillo, download.dpi, and the file and data DPIs > >> as examples. > >> The second patch works with the latest gopher.dpi repository. > >> > >> The main idea is that the DPIs that handle protocols save the URL and > >> write the file themselves, coordinating with download.dpi and dillo. > >> > >> To do this, they implement a new DPI command: `save_url` > >> d_cmd = a_Dpip_build_cmd("cmd=%s url=%s destination=%s", "save_url", > url, > >> dl_dest); > >> > >> Dillo initiates a download, sending it to download.dpi as before. If > it's > >> HTTP* or FTP*, it downloads directly as it does now. Otherwise, it will > >> send a `save_url` command to Dillo to coordinate. This allows Dillo to > >> notify the user, verify the security of the change, etc.Currently, Dillo > >> only checks if there's a DPI that handles the requested protocol. > >> > >> (A new function (`a_Dpiapi_is_service_handled(server_str)`) queries > `dpid` > >> without executing the DPI. No code is modified in `dpid`. Modifying > `dpid` > >> or executing the DPI would allow querying the capabilities of the DPIs, > but > >> it doesn't seem necessary.) > >> > >> - If a DPI is present, it sends the `save_url` command to the DPI that > >> coordinates with `download.dpi` via a secondary channel so that > downloads > >> can continue even if all Dillo windows are closed. > >> > >> - If the protocol isn't handled, it notifies download.dpi through the > >> secondary channel (this reduces the amount of code). > >> > >> The next step would be to implement `save_url` in other protocol DPIs. > >> > >> A possible change to download.dpi once all is done is to leave > >> download.dpi it as just a GUI for DPIs and extract the code to download > >> HTTP to a DPI. (There's already ftp.dpi) > >> > >> One last thing: can you recommend a simple Git manual? > >> > >> > >> Saludos > >> Diego. > >> > >> El lun, 25 may 2026 a las 21:23, Rodrigo Arias (<rodarima(a)gmail.com>) > >> escribió: > >> > >>> Hi, > >>> > >>> On Mon, May 25, 2026 at 09:25:58AM -0700, Ben Collver wrote: > >>> >Good day, > >>> > > >>> >I am using dillo 3.3.0 on Slackware64 15.0. > >>> > > >>> >If I open a gopher directory, right-click on an item, and click > >>> >Save link as..., this opens a file save dialog. If i click OK, it > >>> >dismisses the dialog. I expected it to save something, but it > >>> >creates no new files. > >>> > > >>> >Gopher URI: gopher://gopher.pglaf.org/1/4/0/2/8/40282/ > >>> >Top item: 40282-0 > >>> > > >>> >I found the following workaround: > >>> > > >>> >* Left click 40282-0 > >>> >* Click Save button in browser toolbar > >>> > > >>> >This creates a new file as expected. > >>> > >>> Yes, this is a known limitation of the downloads in Dillo. Using the > >>> "Save link as" to fetch a new resource will use wget under the hood, > >>> which only allows http(s). You can see the message in the console: > >>> > >>> > UIcmd_save: /tmp/40282-0.txt > >>> > ** WARNING **: Ignoring download request for > >>> > 'gopher://gopher.pglaf.org/0/4/0/2/8/40282/40282-0.txt': not in > cache > >>> > and not downloadable. > >>> > >>> Browsing to the target file makes the gopher plugin fetch the file and > >>> place it in the Dillo cache (you can see it in about:cache). Then > saving > >>> the current page (or going back and clicking the "Save link as" entry) > >>> works because it fetches it from the cache. > >>> > >>> It is planned to solve this some time in the future, but involves > >>> complex changes. In the meanwhile, you can use this workaround. > >>> > >>> Best, > >>> Rodrigo. > >>> _______________________________________________ > >>> Dillo-dev mailing list -- dillo-dev(a)mailman3.com > >>> To unsubscribe send an email to dillo-dev-leave(a)mailman3.com > >>> > >> > > >_______________________________________________ > >Dillo-dev mailing list -- dillo-dev(a)mailman3.com > >To unsubscribe send an email to dillo-dev-leave(a)mailman3.com > > _______________________________________________ > Dillo-dev mailing list -- dillo-dev(a)mailman3.com > To unsubscribe send an email to dillo-dev-leave(a)mailman3.com >

July 12, 2026

Re: Save link as... silent failure on gopher protocol

by Rodrigo Arias

Hi, On Thu, Jul 09, 2026 at 01:37:14AM +0200, Diego wrote: >¿Can i have some feedback? ¿Do the patchs work for you? ¿do it seem a >practical idea? ¿etc? Thanks, I received the patches but I haven't had time to look at this yet, I have have it in my queue. Best, Rodrigo. > >cheers! >Diego. > > >El vie, 3 jul 2026 a las 14:17, Diego (<darkspirit5000(a)gmail.com>) escribió: > >> Hello, I'm sending two patches with an idea to solve this problem. >> It's a proof of concept that I'm offering to develop and complete, >> although I have very little free time. >> >> The first patch works with the latest dillo release (3.3.0) but also works >> with the current repository. >> It implements changes in dillo, download.dpi, and the file and data DPIs >> as examples. >> The second patch works with the latest gopher.dpi repository. >> >> The main idea is that the DPIs that handle protocols save the URL and >> write the file themselves, coordinating with download.dpi and dillo. >> >> To do this, they implement a new DPI command: `save_url` >> d_cmd = a_Dpip_build_cmd("cmd=%s url=%s destination=%s", "save_url", url, >> dl_dest); >> >> Dillo initiates a download, sending it to download.dpi as before. If it's >> HTTP* or FTP*, it downloads directly as it does now. Otherwise, it will >> send a `save_url` command to Dillo to coordinate. This allows Dillo to >> notify the user, verify the security of the change, etc.Currently, Dillo >> only checks if there's a DPI that handles the requested protocol. >> >> (A new function (`a_Dpiapi_is_service_handled(server_str)`) queries `dpid` >> without executing the DPI. No code is modified in `dpid`. Modifying `dpid` >> or executing the DPI would allow querying the capabilities of the DPIs, but >> it doesn't seem necessary.) >> >> - If a DPI is present, it sends the `save_url` command to the DPI that >> coordinates with `download.dpi` via a secondary channel so that downloads >> can continue even if all Dillo windows are closed. >> >> - If the protocol isn't handled, it notifies download.dpi through the >> secondary channel (this reduces the amount of code). >> >> The next step would be to implement `save_url` in other protocol DPIs. >> >> A possible change to download.dpi once all is done is to leave >> download.dpi it as just a GUI for DPIs and extract the code to download >> HTTP to a DPI. (There's already ftp.dpi) >> >> One last thing: can you recommend a simple Git manual? >> >> >> Saludos >> Diego. >> >> El lun, 25 may 2026 a las 21:23, Rodrigo Arias (<rodarima(a)gmail.com>) >> escribió: >> >>> Hi, >>> >>> On Mon, May 25, 2026 at 09:25:58AM -0700, Ben Collver wrote: >>> >Good day, >>> > >>> >I am using dillo 3.3.0 on Slackware64 15.0. >>> > >>> >If I open a gopher directory, right-click on an item, and click >>> >Save link as..., this opens a file save dialog. If i click OK, it >>> >dismisses the dialog. I expected it to save something, but it >>> >creates no new files. >>> > >>> >Gopher URI: gopher://gopher.pglaf.org/1/4/0/2/8/40282/ >>> >Top item: 40282-0 >>> > >>> >I found the following workaround: >>> > >>> >* Left click 40282-0 >>> >* Click Save button in browser toolbar >>> > >>> >This creates a new file as expected. >>> >>> Yes, this is a known limitation of the downloads in Dillo. Using the >>> "Save link as" to fetch a new resource will use wget under the hood, >>> which only allows http(s). You can see the message in the console: >>> >>> > UIcmd_save: /tmp/40282-0.txt >>> > ** WARNING **: Ignoring download request for >>> > 'gopher://gopher.pglaf.org/0/4/0/2/8/40282/40282-0.txt': not in cache >>> > and not downloadable. >>> >>> Browsing to the target file makes the gopher plugin fetch the file and >>> place it in the Dillo cache (you can see it in about:cache). Then saving >>> the current page (or going back and clicking the "Save link as" entry) >>> works because it fetches it from the cache. >>> >>> It is planned to solve this some time in the future, but involves >>> complex changes. In the meanwhile, you can use this workaround. >>> >>> Best, >>> Rodrigo. >>> _______________________________________________ >>> Dillo-dev mailing list -- dillo-dev(a)mailman3.com >>> To unsubscribe send an email to dillo-dev-leave(a)mailman3.com >>> >> >_______________________________________________ >Dillo-dev mailing list -- dillo-dev(a)mailman3.com >To unsubscribe send an email to dillo-dev-leave(a)mailman3.com

July 12, 2026

Re: [PATCH] Fix typo in doc/user_help

by Rodrigo Arias

Hi Nikolas, Thanks for the patch, merged in: https://git.dillo-browser.org/dillo/commit/?id=fe83f43f07e1a83e4c05831c553b… Best, Rodrigo. On Sun, Jul 12, 2026 at 12:10:02AM -0400, Nikolas Nyby wrote: >--- > doc/user_help.in.html | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git a/doc/user_help.in.html b/doc/user_help.in.html >index 6b21a7f9..9f0ca589 100644 >--- a/doc/user_help.in.html >+++ b/doc/user_help.in.html >@@ -842,7 +842,7 @@ button over a link or over the current page can be configured to show additional > entries that will run programs defined in the dillorc configuration. The options > <code>link_action</code> and <code>page_action</code> define new entries > for the link and page menu respectively, multiple entries can be configured by >-writting them multiple times. >+writing them multiple times. > > <p> > The format to specify an action is >-- >2.53.0 > >_______________________________________________ >Dillo-dev mailing list -- dillo-dev(a)mailman3.com >To unsubscribe send an email to dillo-dev-leave(a)mailman3.com

July 12, 2026

[PATCH] Fix typo in doc/user_help

by Nikolas Nyby

--- doc/user_help.in.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user_help.in.html b/doc/user_help.in.html index 6b21a7f9..9f0ca589 100644 --- a/doc/user_help.in.html +++ b/doc/user_help.in.html @@ -842,7 +842,7 @@ button over a link or over the current page can be configured to show additional entries that will run programs defined in the dillorc configuration. The options <code>link_action</code> and <code>page_action</code> define new entries for the link and page menu respectively, multiple entries can be configured by -writting them multiple times. +writing them multiple times. <p> The format to specify an action is -- 2.53.0

July 12, 2026

Re: Save link as... silent failure on gopher protocol

by Diego

¿Can i have some feedback? ¿Do the patchs work for you? ¿do it seem a practical idea? ¿etc? cheers! Diego. El vie, 3 jul 2026 a las 14:17, Diego (<darkspirit5000(a)gmail.com>) escribió: > Hello, I'm sending two patches with an idea to solve this problem. > It's a proof of concept that I'm offering to develop and complete, > although I have very little free time. > > The first patch works with the latest dillo release (3.3.0) but also works > with the current repository. > It implements changes in dillo, download.dpi, and the file and data DPIs > as examples. > The second patch works with the latest gopher.dpi repository. > > The main idea is that the DPIs that handle protocols save the URL and > write the file themselves, coordinating with download.dpi and dillo. > > To do this, they implement a new DPI command: `save_url` > d_cmd = a_Dpip_build_cmd("cmd=%s url=%s destination=%s", "save_url", url, > dl_dest); > > Dillo initiates a download, sending it to download.dpi as before. If it's > HTTP* or FTP*, it downloads directly as it does now. Otherwise, it will > send a `save_url` command to Dillo to coordinate. This allows Dillo to > notify the user, verify the security of the change, etc.Currently, Dillo > only checks if there's a DPI that handles the requested protocol. > > (A new function (`a_Dpiapi_is_service_handled(server_str)`) queries `dpid` > without executing the DPI. No code is modified in `dpid`. Modifying `dpid` > or executing the DPI would allow querying the capabilities of the DPIs, but > it doesn't seem necessary.) > > - If a DPI is present, it sends the `save_url` command to the DPI that > coordinates with `download.dpi` via a secondary channel so that downloads > can continue even if all Dillo windows are closed. > > - If the protocol isn't handled, it notifies download.dpi through the > secondary channel (this reduces the amount of code). > > The next step would be to implement `save_url` in other protocol DPIs. > > A possible change to download.dpi once all is done is to leave > download.dpi it as just a GUI for DPIs and extract the code to download > HTTP to a DPI. (There's already ftp.dpi) > > One last thing: can you recommend a simple Git manual? > > > Saludos > Diego. > > El lun, 25 may 2026 a las 21:23, Rodrigo Arias (<rodarima(a)gmail.com>) > escribió: > >> Hi, >> >> On Mon, May 25, 2026 at 09:25:58AM -0700, Ben Collver wrote: >> >Good day, >> > >> >I am using dillo 3.3.0 on Slackware64 15.0. >> > >> >If I open a gopher directory, right-click on an item, and click >> >Save link as..., this opens a file save dialog. If i click OK, it >> >dismisses the dialog. I expected it to save something, but it >> >creates no new files. >> > >> >Gopher URI: gopher://gopher.pglaf.org/1/4/0/2/8/40282/ >> >Top item: 40282-0 >> > >> >I found the following workaround: >> > >> >* Left click 40282-0 >> >* Click Save button in browser toolbar >> > >> >This creates a new file as expected. >> >> Yes, this is a known limitation of the downloads in Dillo. Using the >> "Save link as" to fetch a new resource will use wget under the hood, >> which only allows http(s). You can see the message in the console: >> >> > UIcmd_save: /tmp/40282-0.txt >> > ** WARNING **: Ignoring download request for >> > 'gopher://gopher.pglaf.org/0/4/0/2/8/40282/40282-0.txt': not in cache >> > and not downloadable. >> >> Browsing to the target file makes the gopher plugin fetch the file and >> place it in the Dillo cache (you can see it in about:cache). Then saving >> the current page (or going back and clicking the "Save link as" entry) >> works because it fetches it from the cache. >> >> It is planned to solve this some time in the future, but involves >> complex changes. In the meanwhile, you can use this workaround. >> >> Best, >> Rodrigo. >> _______________________________________________ >> Dillo-dev mailing list -- dillo-dev(a)mailman3.com >> To unsubscribe send an email to dillo-dev-leave(a)mailman3.com >> >

July 8, 2026

Re: Save link as... silent failure on gopher protocol

by Diego

Hello, I'm sending two patches with an idea to solve this problem. It's a proof of concept that I'm offering to develop and complete, although I have very little free time. The first patch works with the latest dillo release (3.3.0) but also works with the current repository. It implements changes in dillo, download.dpi, and the file and data DPIs as examples. The second patch works with the latest gopher.dpi repository. The main idea is that the DPIs that handle protocols save the URL and write the file themselves, coordinating with download.dpi and dillo. To do this, they implement a new DPI command: `save_url` d_cmd = a_Dpip_build_cmd("cmd=%s url=%s destination=%s", "save_url", url, dl_dest); Dillo initiates a download, sending it to download.dpi as before. If it's HTTP* or FTP*, it downloads directly as it does now. Otherwise, it will send a `save_url` command to Dillo to coordinate. This allows Dillo to notify the user, verify the security of the change, etc.Currently, Dillo only checks if there's a DPI that handles the requested protocol. (A new function (`a_Dpiapi_is_service_handled(server_str)`) queries `dpid` without executing the DPI. No code is modified in `dpid`. Modifying `dpid` or executing the DPI would allow querying the capabilities of the DPIs, but it doesn't seem necessary.) - If a DPI is present, it sends the `save_url` command to the DPI that coordinates with `download.dpi` via a secondary channel so that downloads can continue even if all Dillo windows are closed. - If the protocol isn't handled, it notifies download.dpi through the secondary channel (this reduces the amount of code). The next step would be to implement `save_url` in other protocol DPIs. A possible change to download.dpi once all is done is to leave download.dpi it as just a GUI for DPIs and extract the code to download HTTP to a DPI. (There's already ftp.dpi) One last thing: can you recommend a simple Git manual? Saludos Diego. El lun, 25 may 2026 a las 21:23, Rodrigo Arias (<rodarima(a)gmail.com>) escribió: > Hi, > > On Mon, May 25, 2026 at 09:25:58AM -0700, Ben Collver wrote: > >Good day, > > > >I am using dillo 3.3.0 on Slackware64 15.0. > > > >If I open a gopher directory, right-click on an item, and click > >Save link as..., this opens a file save dialog. If i click OK, it > >dismisses the dialog. I expected it to save something, but it > >creates no new files. > > > >Gopher URI: gopher://gopher.pglaf.org/1/4/0/2/8/40282/ > >Top item: 40282-0 > > > >I found the following workaround: > > > >* Left click 40282-0 > >* Click Save button in browser toolbar > > > >This creates a new file as expected. > > Yes, this is a known limitation of the downloads in Dillo. Using the > "Save link as" to fetch a new resource will use wget under the hood, > which only allows http(s). You can see the message in the console: > > > UIcmd_save: /tmp/40282-0.txt > > ** WARNING **: Ignoring download request for > > 'gopher://gopher.pglaf.org/0/4/0/2/8/40282/40282-0.txt': not in cache > > and not downloadable. > > Browsing to the target file makes the gopher plugin fetch the file and > place it in the Dillo cache (you can see it in about:cache). Then saving > the current page (or going back and clicking the "Save link as" entry) > works because it fetches it from the cache. > > It is planned to solve this some time in the future, but involves > complex changes. In the meanwhile, you can use this workaround. > > Best, > Rodrigo. > _______________________________________________ > Dillo-dev mailing list -- dillo-dev(a)mailman3.com > To unsubscribe send an email to dillo-dev-leave(a)mailman3.com >

July 3, 2026

Re: [PATCH] Fix header parsing bug with malicious header fields

by Rodrigo Arias

Hi, >diff --git a/src/cache.c b/src/cache.c >index 154bef5c..5bd8a5dc 100644 >--- a/src/cache.c >+++ b/src/cache.c >@@ -287,7 +287,7 @@ static int Cache_bufsize(CacheEntry_t *e) > * Inject full page content directly into the cache. > * Used for "about:splash". May be used for "about:cache" too. > * >- * The @param data_ds buffer is copied into the entry buffer, so it is >+ * @param buf is copied into the entry buffer, so it is the > * responsibility of the caller to free it. > */ > void a_Cache_entry_inject(const DilloUrl *Url, >@@ -765,9 +765,8 @@ static Dlist *Cache_parse_multiple_fields(const char *header, > j--; > field = dStrndup(header + i, j); > dList_append(fields, field); >- } else { >- while (header[i] != '\n') i++; > } >+ while (header[i] != '\n') i++; > } > > if (dList_length(fields) == 0) { Thanks!, merged in two commits with a comment: https://git.dillo-browser.org/dillo/commit/?id=7ed29a43c18a960946fe47f37004… https://git.dillo-browser.org/dillo/commit/?id=9b7b799c7e47ca6e2b91aec82bd5… Best, Rodrigo.

June 21, 2026

Re: Nordstjernen web browser

by Bobby Hiltz

> Banned, > Rodrigo. Probably the best option. It is totally possible that that email account is a bot too. The commits haven't stopped! I am annoyingly anti-AI, and it appears Lobsters had the same feelings about this project (https://lobste.rs/s/adztcr/nordstjernen_web_browser) And the claims? Stable? Written from scratch? Private? LEGENDARY? Good call. Thanks, Bobby

June 16, 2026

Re: Nordstjernen web browser

by J. M. Castroagudín Silva

On Mon, Jun 15, 2026 at 7:09 PM Rodrigo Arias <rodarima(a)gmail.com> wrote: > > Hi, > > Hmm, from the repo: > > >Minimalism: The whole engine is about 116,000 lines of C (plus a thin > >C++ Qt shell) — small enough for one person to read and audit > >end-to-end. > > >Don't ask "do you want me to proceed?", "should I continue?", "ready to > >commit?" — just do it. The user interrupts if they disagree. > > >Don't leave traces that the code has been written by AI LLM, in commit > >messages and git author and git committer. And yet, there are countless commits made by claude: https://github.com/nordstjernen-web/nordstjernen/commits/main/ Amazing, the amount of resources burned for a technology so damn abysmal It would be funny if it wasn't so sad :( > > Burn baby burn! > > https://www.theguardian.com/environment/2026/feb/13/elon-musk-xai-datacente… > > Banned, > Rodrigo. > _______________________________________________ > Dillo-dev mailing list -- dillo-dev(a)mailman3.com > To unsubscribe send an email to dillo-dev-leave(a)mailman3.com -- Saúde, J. M. Castroagudín

June 15, 2026