- Dillo-dev - lists.mailman3.com

dillo.org web site

by jcid＠dillo.org

[here goes the attachement] -- Cheers Jorge.-

June 6, 2012

dillo.org web site

by jcid＠dillo.org

On Tue, Jun 05, 2012 at 02:52:08PM -0800, Roger wrote: > > On Tue, Jun 05, 2012 at 02:03:12PM -0400, Jorge Arellano Cid wrote: > >On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: > >> > >> Jorge Arellano Cid wrote: > >> > >> > The domain was renewed, but I still can't see the website from > >> > Chile, although when I log to the wearlab it works [1]. > >> > >> Using dillo, Firefox and links, www.dillo.org works but dillo.org > >> returns nothing but some <script> elements from sedoparking.com . > > > > It doesn't work here... :( > > > > Yesterday I filled a "Case management" ticket at dotster > >(000domains.com) 24 hours have passed and not even a single > >automated answer has come from them. > > > > Can someone in the US please help us with this? There's a phone > >number to call 800-401-5220. The case ticket number is 01278137. > >If somebody volunteers please write me to send you the account > >credentials. > > Any takers? I can do so, but I don't want to duplicate efforts, as it might > look suspicious with more then two people calling in. Today I login into 000domains to see what happened with the ticket and to my surprise there's an internal error message saying they can't access my case management ticket (this is the attachment). This message gives a different phone number to call [1]. @Roger (or any volunteer): Can you please call this number and ask what the problem is. [1] +1 360-253-2210 Another way to solve the problem may be to point to a working nameserver elsewhere too (the API seems to allow this option). I'll ask Andreas K. whether we can point to the wearlab DNS in the interim. -- Cheers Jorge.-

June 6, 2012

dillo.org web site

by rogerx.oss＠gmail.com

> On Tue, Jun 05, 2012 at 02:03:12PM -0400, Jorge Arellano Cid wrote: >On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: >> >> Jorge Arellano Cid wrote: >> >> > The domain was renewed, but I still can't see the website from >> > Chile, although when I log to the wearlab it works [1]. >> >> Using dillo, Firefox and links, www.dillo.org works but dillo.org >> returns nothing but some <script> elements from sedoparking.com . > > It doesn't work here... :( > > Yesterday I filled a "Case management" ticket at dotster >(000domains.com) 24 hours have passed and not even a single >automated answer has come from them. > > Can someone in the US please help us with this? There's a phone >number to call 800-401-5220. The case ticket number is 01278137. >If somebody volunteers please write me to send you the account >credentials. Any takers? I can do so, but I don't want to duplicate efforts, as it might look suspicious with more then two people calling in. Probably should have privately emailed some of us first, then sent a public email, unless you've already tried calling too. Well called anyways and it appears to be a Mexico or South American based phone number and not a US one based on the language used. The girl answering the phone does sound really pretty, but my hispanol (spanish) is a little rough here. Depressing. ;-) I'm sure this will provoke some interest with the rest of you guys calling the number too. -- Roger http://rogerx.freeshell.org/

June 5, 2012

dillo.org web site

by jcid＠dillo.org

On Tue, Jun 05, 2012 at 11:28:40AM +0100, Jeremy Henty wrote: > > Jorge Arellano Cid wrote: > > > The domain was renewed, but I still can't see the website from > > Chile, although when I log to the wearlab it works [1]. > > Using dillo, Firefox and links, www.dillo.org works but dillo.org > returns nothing but some <script> elements from sedoparking.com . It doesn't work here... :( Yesterday I filled a "Case management" ticket at dotster (000domains.com) 24 hours have passed and not even a single automated answer has come from them. Can someone in the US please help us with this? There's a phone number to call 800-401-5220. The case ticket number is 01278137. If somebody volunteers please write me to send you the account credentials. <ticket text> Hi, I've been using the service for 12 years. I renewed the service on June 01, after a few days it expired (May 28). Today is June 04, and DNS management doesn't work. It points to a parking place. jcid at infinity:~$ nslookup www.dillo.org ns1.nameresolve.com Server: ns1.nameresolve.com Address: 66.96.142.146#53 Name: www.dillo.org Address: 63.251.171.80 Name: www.dillo.org Address: 66.150.161.141 Name: www.dillo.org Address: 134.102.206.165 Name: www.dillo.org Address: 69.25.27.173 Name: www.dillo.org Address: 66.150.161.140 Name: www.dillo.org Address: 69.25.27.170 Name: www.dillo.org Address: 63.251.171.81 TIA. </ticket text> -- Cheers Jorge.-

June 5, 2012

dillo.org web site

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > The domain was renewed, but I still can't see the website from > Chile, although when I log to the wearlab it works [1]. Using dillo, Firefox and links, www.dillo.org works but dillo.org returns nothing but some <script> elements from sedoparking.com . dnsip returns the same result for dillo.org and www.dillo.org: 134.102.206.165 63.251.171.80 63.251.171.81 66.150.161.140 66.150.161.141 69.25.27.170 69.25.27.173 Regards, Jeremy Henty

June 5, 2012

[patch] dlib cleanup

by onepoint＠starurchin.org

Jorge Arellano Cid wrote: > Some C libs leave errno unset, and others always set it to ENOMEM. > Please excuse my ignorance, but what other error conditions may > malloc return? According to the man pages on my Linux system: The Unix98 standard requires malloc(), calloc(), and realloc() to set errno to ENOMEM upon failure. Glibc assumes that this is done (and the glibc versions of these routines do this); if you use a private malloc implementation that does not set errno, then certain library routines may fail with- out having a reason in errno. So, unless we support systems that do not conform to Unix98, then I read this as saying that ENOMEM is the only error we will see. Regards, Jeremy Henty

June 5, 2012

dillo.org web site

by rogerx.oss＠gmail.com

> On Mon, Jun 04, 2012 at 12:26:07PM -0400, Jorge Arellano Cid wrote: >Hi there, > > The domain was renewed, but I still can't see the website from Chile, >although when I log to the wearlab it works [1]. > > Is everybody seeing having the same problem? Blank white page here in Alaska. whois shows the address as owned by Jorg. Mon Jun 4 19:21:52 AKDT 2012 -- Roger http://rogerx.freeshell.org/

June 5, 2012

dillo.org web site

by higuita7＠yahoo.co.uk

Hi > > in whois, hence I assume it is just a DNS configuration issue?! > Hmmm, the DNS is managed by the same provider [1]. yep, its a DNS problem, the domain points to the nameresolve.com dns servers and they are pointing both the www and the domain to the default parking pages and to the IP 134.102.206.165 (the correct page) So you have to make sure that the domain only have one A record for those entries, and if its already just one A record, its probably a bug in the nameresolve.com, that didnt removed the dns parking entries from the domain. ~/$ dnstracer -s . www.dillo.org -o Tracing to www.dillo.org[a] via A.ROOT-SERVERS.NET, maximum of 3 retries A.ROOT-SERVERS.NET [.] (2001:0503:ba3e:0000:0000:0000:0002:0030) |\___ b0.org.afilias-nst.org [org] (2001:0500:000c:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) Got authoritative answer | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) Got authoritative answer | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) Got authoritative answer | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) Got authoritative answer |\___ b0.org.afilias-nst.org [org] (199.19.54.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ a2.org.afilias-nst.info [org] (2001:0500:0040:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a2.org.afilias-nst.info [org] (199.249.112.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (2001:0500:000e:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (199.19.56.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ c0.org.afilias-nst.info [org] (2001:0500:000b:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ c0.org.afilias-nst.info [org] (199.19.53.1) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ d0.org.afilias-nst.org [org] (2001:0500:000f:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ d0.org.afilias-nst.org [org] (199.19.57.1) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ b2.org.afilias-nst.org [org] (2001:0500:0048:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) \___ b2.org.afilias-nst.org [org] (199.249.120.1) |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 69.25.27.173 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 63.251.171.81 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 66.150.161.140 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 134.102.206.165 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 66.150.161.141 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 69.25.27.170 ns1.nameresolve.com (66.96.142.146) www.dillo.org -> 63.251.171.80 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 66.150.161.140 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 69.25.27.170 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 63.251.171.80 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 69.25.27.173 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 66.150.161.141 ns2.nameresolve.com (65.254.254.170) www.dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 69.25.27.173 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 66.150.161.140 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 134.102.206.165 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 66.150.161.141 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 69.25.27.170 ns3.nameresolve.com (66.96.142.148) www.dillo.org -> 63.251.171.80 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 66.150.161.140 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 69.25.27.170 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 134.102.206.165 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 63.251.171.80 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 69.25.27.173 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 66.150.161.141 ns4.nameresolve.com (65.254.254.172) www.dillo.org -> 63.251.171.81 ~/$ dnstracer -s . dillo.org -o Tracing to dillo.org[a] via A.ROOT-SERVERS.NET, maximum of 3 retries A.ROOT-SERVERS.NET [.] (2001:0503:ba3e:0000:0000:0000:0002:0030) |\___ d0.org.afilias-nst.org [org] (2001:0500:000f:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) Got authoritative answer | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) Got authoritative answer | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) Got authoritative answer | \___ ns3.nameresolve.com [dillo.org] (66.96.142.148) Got authoritative answer |\___ d0.org.afilias-nst.org [org] (199.19.57.1) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ b0.org.afilias-nst.org [org] (2001:0500:000c:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) |\___ b0.org.afilias-nst.org [org] (199.19.54.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a0.org.afilias-nst.info [org] (2001:0500:000e:0000:0000:0000:0000:0001) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | \___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) |\___ a0.org.afilias-nst.info [org] (199.19.56.1) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ c0.org.afilias-nst.info [org] (2001:0500:000b:0000:0000:0000:0000:0001) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ c0.org.afilias-nst.info [org] (199.19.53.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | |\___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) | \___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ b2.org.afilias-nst.org [org] (2001:0500:0048:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ b2.org.afilias-nst.org [org] (199.249.120.1) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) |\___ a2.org.afilias-nst.info [org] (2001:0500:0040:0000:0000:0000:0000:0001) | |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) | |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) | |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) | \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) \___ a2.org.afilias-nst.info [org] (199.249.112.1) |\___ ns4.nameresolve.com [dillo.org] (65.254.254.172) (cached) |\___ ns3.nameresolve.com [dillo.org] (66.96.142.148) (cached) |\___ ns2.nameresolve.com [dillo.org] (65.254.254.170) (cached) \___ ns1.nameresolve.com [dillo.org] (66.96.142.146) (cached) ns3.nameresolve.com (66.96.142.148) dillo.org -> 66.150.161.141 ns3.nameresolve.com (66.96.142.148) dillo.org -> 69.25.27.170 ns3.nameresolve.com (66.96.142.148) dillo.org -> 63.251.171.81 ns3.nameresolve.com (66.96.142.148) dillo.org -> 66.150.161.140 ns3.nameresolve.com (66.96.142.148) dillo.org -> 63.251.171.80 ns3.nameresolve.com (66.96.142.148) dillo.org -> 69.25.27.173 ns3.nameresolve.com (66.96.142.148) dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) dillo.org -> 66.150.161.141 ns2.nameresolve.com (65.254.254.170) dillo.org -> 134.102.206.165 ns2.nameresolve.com (65.254.254.170) dillo.org -> 69.25.27.170 ns2.nameresolve.com (65.254.254.170) dillo.org -> 69.25.27.173 ns2.nameresolve.com (65.254.254.170) dillo.org -> 66.150.161.140 ns2.nameresolve.com (65.254.254.170) dillo.org -> 63.251.171.81 ns2.nameresolve.com (65.254.254.170) dillo.org -> 63.251.171.80 ns1.nameresolve.com (66.96.142.146) dillo.org -> 63.251.171.80 ns1.nameresolve.com (66.96.142.146) dillo.org -> 66.150.161.140 ns1.nameresolve.com (66.96.142.146) dillo.org -> 134.102.206.165 ns1.nameresolve.com (66.96.142.146) dillo.org -> 66.150.161.141 ns1.nameresolve.com (66.96.142.146) dillo.org -> 69.25.27.170 ns1.nameresolve.com (66.96.142.146) dillo.org -> 69.25.27.173 ns1.nameresolve.com (66.96.142.146) dillo.org -> 63.251.171.81 ns4.nameresolve.com (65.254.254.172) dillo.org -> 66.150.161.141 ns4.nameresolve.com (65.254.254.172) dillo.org -> 63.251.171.81 ns4.nameresolve.com (65.254.254.172) dillo.org -> 69.25.27.173 ns4.nameresolve.com (65.254.254.172) dillo.org -> 69.25.27.170 ns4.nameresolve.com (65.254.254.172) dillo.org -> 66.150.161.140 ns4.nameresolve.com (65.254.254.172) dillo.org -> 134.102.206.165 ns4.nameresolve.com (65.254.254.172) dillo.org -> 63.251.171.80 higuita -- Naturally the common people don't want war... but after all it is the leaders of a country who determine the policy, and it is always a simple matter to drag the people along, whether it is a democracy, or a fascist dictatorship, or a parliament, or a communist dictatorship. Voice or no voice, the people can always be brought to the bidding of the leaders. That is easy. All you have to do is tell them they are being attacked, and denounce the pacifists for lack of patriotism and exposing the country to danger. It works the same in every country. -- Hermann Goering, Nazi and war criminal, 1883-1946

June 4, 2012

dillo.org web site

by jcid＠dillo.org

HI, On Mon, Jun 04, 2012 at 06:53:06PM +0200, Axel Beckert wrote: > Hi, > > On Mon, Jun 04, 2012 at 12:26:07PM -0400, Jorge Arellano Cid wrote: > > The domain was renewed, but I still can't see the website from Chile, > > although when I log to the wearlab it works [1]. > > > > Is everybody seeing having the same problem? > > > > [1] lynx www.dillo.org > > Looks fishy from here in Switzerland. I get the same DNS entries as > Sebastian and they seem to point to some Domain parking page by the > well-known domain broker Sedo with only advertisement links on it. > > But "whois dillo.org" states that the domain belongs to Jorge. Henning wrote: > I am getting a placeholder ad/spam-link page. You are still registered > in whois, hence I assume it is just a DNS configuration issue?! Hmmm, the DNS is managed by the same provider [1]. Well, dotster uses four DNS servers: ns[1-4].nameresolve.com and here I get: jcid at infinity:~$ nslookup www.dillo.org ns1.nameresolve.com Server: ns1.nameresolve.com Address: 66.96.142.146#53 Name: www.dillo.org Address: 63.251.171.80 Name: www.dillo.org Address: 66.150.161.141 Name: www.dillo.org Address: 134.102.206.165 Name: www.dillo.org Address: 69.25.27.173 Name: www.dillo.org Address: 66.150.161.140 Name: www.dillo.org Address: 69.25.27.170 Name: www.dillo.org Address: 63.251.171.81 so it looks like I should contact them... [1] http://www.dotster.com/domains/tools.bml -- Cheers Jorge.-

June 4, 2012

dillo.org web site

by abe＠deuxchevaux.org

Hi, On Mon, Jun 04, 2012 at 12:26:07PM -0400, Jorge Arellano Cid wrote: > The domain was renewed, but I still can't see the website from Chile, > although when I log to the wearlab it works [1]. > > Is everybody seeing having the same problem? > > [1] lynx www.dillo.org Looks fishy from here in Switzerland. I get the same DNS entries as Sebastian and they seem to point to some Domain parking page by the well-known domain broker Sedo with only advertisement links on it. But "whois dillo.org" states that the domain belongs to Jorge. Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | abe at deuxchevaux.org (Mail) X See http://www.asciiribbon.org/ | abe at noone.org (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://noone.org/abe/ (Web)

June 4, 2012

dillo.org web site

by sgeerken＠dillo.org

On Mon, Jun 04, Jorge Arellano Cid wrote: > The domain was renewed, but I still can't see the website from Chile, > although when I log to the wearlab it works [1]. > > Is everybody seeing having the same problem? I've tested a couple of browsers, and "ping": in all cases, "www.dillo.org" works, while "dillo.org" does not work. A DNS lookup looks a bit strange: sg at sg4:~$ nslookup www.dillo.org Server: 192.168.178.1 Address: 192.168.178.1#53 Non-authoritative answer: Name: www.dillo.org Address: 134.102.206.165 Name: www.dillo.org Address: 63.251.171.80 Name: www.dillo.org Address: 63.251.171.81 Name: www.dillo.org Address: 66.150.161.140 Name: www.dillo.org Address: 66.150.161.141 Name: www.dillo.org Address: 69.25.27.170 Name: www.dillo.org Address: 69.25.27.173 sg at sg4:~$ nslookup dillo.org Server: 192.168.178.1 Address: 192.168.178.1#53 Non-authoritative answer: Name: dillo.org Address: 66.150.161.140 Name: dillo.org Address: 66.150.161.141 Name: dillo.org Address: 69.25.27.170 Name: dillo.org Address: 69.25.27.173 Name: dillo.org Address: 134.102.206.165 Name: dillo.org Address: 63.251.171.80 Name: dillo.org Address: 63.251.171.81 The correct adress should be 134.102.206.165. I assume that there are still some invalid entries in DNS caches. Sebastian

June 4, 2012

dillo.org web site

by jcid＠dillo.org

Hi there, The domain was renewed, but I still can't see the website from Chile, although when I log to the wearlab it works [1]. Is everybody seeing having the same problem? [1] lynx www.dillo.org -- Cheers Jorge.-

June 4, 2012

[patch] dlib cleanup

by jcid＠dillo.org

On Sun, Jun 03, 2012 at 05:52:43PM +0400, 123 wrote: > On Sat, Jun 02, 2012 at 05:23:52PM -0400, Jorge Arellano Cid wrote: > > Hi, > > > > On Sun, Jun 03, 2012 at 12:13:41AM +0400, 123 wrote: > > > malloc.diff: added perror calls for malloc and realloc errors > > > > > > dstr.diff: dStr* functions cleanup > > > > > > dlist.diff: replaced recursive QuickSort with qsort from stdlib.h. > > > Tested with file.dpi where it is used for sorting directory listing. > > > > There're different criteria to write code. In dlib, a few lines > > are preferred to a single contracted one to make it simpler to > > understand. In the same spirit, scattered return statements are avoided > > to make code path following simpler. > > What about perror in malloc? It is still better than silent exit(1). Yes, it looks better. Some C libs leave errno unset, and others always set it to ENOMEM. Please excuse my ignorance, but what other error conditions may malloc return? > > For quick sort I remember having to implement it in dlib because > > stdlib's qsort varies among platforms. > > I can only find reports about problems in Solaris qsort related to > performance. There should be no known problems in platforms listed on > http://www.dillo.org/Compatibility.html and qsort is a part of > POSIX/SUS. > > qsort is also used in lout/container.cc so broken qsort will break > dillo anyway. AFAIR, there were some qsort receiving different types of arguments or behaving a bit different with some special border cases. I'll try to find what was it in the archives... Non uniform treatment in dlib/dillo is a bug. Unless we know that in container.cc we don't ever fall in one of the special cases. -- Cheers Jorge.-

June 4, 2012

[patch] HTML parser bugfix

by jcid＠dillo.org

On Sun, Jun 03, 2012 at 09:00:55PM +0100, Jeremy Henty wrote: > > 123 wrote: > > > Attached patch removes logic that tries to detect unterminated > > quoted attributes and fixes this bug. > > I would be wary of applying this patch without further thought. I run > Dillo with a very similar patch and it breaks *many* more pages than > it fixes. It is unfortunately necessary to detect and recover from > quoting errors in attributes. For instance, the web is *full* of > pages with tags containing this: > > foo="bar"" > > If you don't detect and ignore that extra double quote you will break > many pages that every other browser renders perfectly well. > > It's not even that uncommon to see monstrosities like this: > > foo=""bar""" > > It is also common to see short attributes (often CSS lengths) > delimited with a mixture of single and double quotes, eg: > > size="12pt' > > For these reasons, sadly, it is IMHO not realistic to just drop the > misquote-detection logic. Ditto. (FWIW, maybe this is the fourth time this patch is received; In the past the submitter has always desisted after some more testing). -- Cheers Jorge.-

June 4, 2012

[patch] HTML parser bugfix

by p37sitdu＠lavabit.com

According to WHATWG [1] fragment <div title=""abc""">def</div> should be parsed without errors until 'a' character. abc""" should be parsed as attribute name with parse errors because of lack of space character and quotes inside attribute name. [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.ht…

June 4, 2012

[patch] HTML parser bugfix

by p37sitdu＠lavabit.com

On Sun, Jun 03, 2012 at 09:00:55PM +0100, Jeremy Henty wrote: > I would be wary of applying this patch without further thought. I run > Dillo with a very similar patch and it breaks *many* more pages than > it fixes. It is unfortunately necessary to detect and recover from > quoting errors in attributes. For instance, the web is *full* of > pages with tags containing this: > > foo="bar"" > > If you don't detect and ignore that extra double quote you will break > many pages that every other browser renders perfectly well. Then there should be some logic for detecting double quotes. Searching for < inside quotes is not the right way as it breaks valid pages like reddit main page. Can you give examples of real web pages with double quotes? > It's not even that uncommon to see monstrosities like this: > > foo=""bar""" <div title=""abc""">def</div> does not show tip "abc" for def in Firefox. It silently displays nothing in Dillo after patch, however. I will try to fix it. > It is also common to see short attributes (often CSS lengths) > delimited with a mixture of single and double quotes, eg: > > size="12pt' <div title="abc'>def</div> displays nothing in Firefox. What browser can render it?

June 3, 2012

[patch] HTML parser bugfix

by onepoint＠starurchin.org

123 wrote: > Attached patch removes logic that tries to detect unterminated > quoted attributes and fixes this bug. I would be wary of applying this patch without further thought. I run Dillo with a very similar patch and it breaks *many* more pages than it fixes. It is unfortunately necessary to detect and recover from quoting errors in attributes. For instance, the web is *full* of pages with tags containing this: foo="bar"" If you don't detect and ignore that extra double quote you will break many pages that every other browser renders perfectly well. It's not even that uncommon to see monstrosities like this: foo=""bar""" It is also common to see short attributes (often CSS lengths) delimited with a mixture of single and double quotes, eg: size="12pt' For these reasons, sadly, it is IMHO not realistic to just drop the misquote-detection logic. Regards, Jeremy Henty

June 3, 2012

[patch] HTML parser bugfix

by p37sitdu＠lavabit.com

The following HTML fragment is shown as BUG<">abc by Dillo. It is valid (checked with validator.w3.org) HTML. In Firefox it is shown as abc with '>BUG<' tooltip. <div title=">BUG<">abc</div> What happens is that Dillo see < character inside quotes, shows bug "attribute lacks closing quote" and breaks out of tag parsing loop. In fact it is not possible to say if there is a bug in HTML at that point. In WWW you can see this bug on http://reddit.com. Each entry on this page contains votehash', null, event)" > and bug meter shows bugs for them. Attached patch removes logic that tries to detect unterminated quoted attributes and fixes this bug.

June 3, 2012

[patch] dlib cleanup

by p37sitdu＠lavabit.com

On Sat, Jun 02, 2012 at 05:23:52PM -0400, Jorge Arellano Cid wrote: > Hi, > > On Sun, Jun 03, 2012 at 12:13:41AM +0400, 123 wrote: > > malloc.diff: added perror calls for malloc and realloc errors > > > > dstr.diff: dStr* functions cleanup > > > > dlist.diff: replaced recursive QuickSort with qsort from stdlib.h. > > Tested with file.dpi where it is used for sorting directory listing. > > There're different criteria to write code. In dlib, a few lines > are preferred to a single contracted one to make it simpler to > understand. In the same spirit, scattered return statements are avoided > to make code path following simpler. What about perror in malloc? It is still better than silent exit(1). > For quick sort I remember having to implement it in dlib because > stdlib's qsort varies among platforms. I can only find reports about problems in Solaris qsort related to performance. There should be no known problems in platforms listed on http://www.dillo.org/Compatibility.html and qsort is a part of POSIX/SUS. qsort is also used in lout/container.cc so broken qsort will break dillo anyway.

June 3, 2012

[patch] typedefs and identifiers with leading underscores

by p37sitdu＠lavabit.com

Updated patch to fix warning in jpeg.c.

June 3, 2012

[patch] downloads dpi progress bar

by p37sitdu＠lavabit.com

Now progress bar is implemented as custom widget on top of Fl_Widget class. But FLTK already has Fl_Progress class for the same thing. Progress bar looks the same with two exceptions: 1. No tooltip: it is not displayed for Fl_Progress even when set. Normally progress bars, labels and other widgets for status information don't have tooltips so I think it is ok. 2. When downloading file without Content-Length, progress bar is always empty. With current implementation it changes for one percent on every update and remains somewhere in the middle when download is finished. For me keeping it at zero looks better. Patch and python HTTP server for testing downloads without Content-Length attached.

June 3, 2012

[patch] dlib cleanup

by jcid＠dillo.org

Hi, On Sun, Jun 03, 2012 at 12:13:41AM +0400, 123 wrote: > malloc.diff: added perror calls for malloc and realloc errors > > dstr.diff: dStr* functions cleanup > > dlist.diff: replaced recursive QuickSort with qsort from stdlib.h. > Tested with file.dpi where it is used for sorting directory listing. There're different criteria to write code. In dlib, a few lines are preferred to a single contracted one to make it simpler to understand. In the same spirit, scattered return statements are avoided to make code path following simpler. For quick sort I remember having to implement it in dlib because stdlib's qsort varies among platforms. -- Cheers Jorge.-

June 2, 2012

[patch] dlib cleanup

by p37sitdu＠lavabit.com

malloc.diff: added perror calls for malloc and realloc errors dstr.diff: dStr* functions cleanup dlist.diff: replaced recursive QuickSort with qsort from stdlib.h. Tested with file.dpi where it is used for sorting directory listing.

June 2, 2012

[patch] typedefs and identifiers with leading underscores

by p37sitdu＠lavabit.com

There is no reason to have a name for structs when we just want to typedef them. BTW identifiers that begin with underscore are reserved. Attached patch fixes all typedefs.

June 2, 2012

Doxyfile

by Johannes.Hofmann＠gmx.de

On Sun, May 27, 2012 at 03:08:14AM +0400, 123 wrote: > By the way new Doxygen supports Markdown[1] and it is enabled by > default. It is easier to read and write than HTML. index.doc rewritten > using markdown is attached. Existing documentation (especially .txt > files) can be converted to markdown too. > > [1] http://daringfireball.net/projects/markdown/ I like the idea of using markdown for in source documentation and also your proposed cleanup of the Doxygen file looks nice, but I'm reluctant to touch the doxygen stuff. Sebastian was the one who put a lot of effort in the documentation and I don't want to break his work just for some cleanups. Cheers, Johannes

May 28, 2012

dillorc and src/keysrc

by Johannes.Hofmann＠gmx.de

On Sun, May 27, 2012 at 03:19:22PM +0400, 123 wrote: > By the way Scroogle is closed but it is still present in dillorc. > diff -r e77b384a9d4d dillorc > --- a/dillorc Sat May 26 13:58:42 2012 +0200 > +++ b/dillorc Sun May 27 15:18:33 2012 +0400 > @@ -113,7 +113,6 @@ > # You can enable multiple search_url strings at once and select from among > # them at runtime, with the first being the default. > search_url="http://duckduckgo.com/lite/?kp=-1&q=%s" > -search_url="Scroogle https://ssl.scroogle.org/cgi-bin/nbbwssl.cgi?Gw=%s" > search_url="Wikipedia http://www.wikipedia.org/w/index.php?search=%s&go=Go" > search_url="Free Dictionary http://www.thefreedictionary.com/%s" > search_url="Google http://www.google.com/search?ie=UTF-8&oe=UTF-8&q=%s" Thanks, committed. Cheers, Johannes

May 28, 2012

dillo.cc cleanup and bugfix

by p37sitdu＠lavabit.com

Reordered #includes. Fixed --geometry flag. It is --geometry in man page but -geometry in usage and only -geometry is recognized by program. Simplified getCmdOption. Removed State enum, it was overkill. It is also possible to remove support for mandatory arguments (opt_argc < 0) as it is not used, but it does not add LOC so I left it there. Removed check for about:blank as start_page, it is not a special case.

May 27, 2012

namespace comments in dw/*

by p37sitdu＠lavabit.com

Copied comments are almost in every source file.

May 27, 2012

Dillo working directory

by p37sitdu＠lavabit.com

In Paths::init Dillo changes working directory to /tmp. This way every time I try to open some page stored on the hard disk (Ctrl-O) I have to start in /tmp. What is the reason for changing WD to /tmp? BTW oldWorkingDir is not used anywhere.

May 27, 2012

Doxygen \todos

by p37sitdu＠lavabit.com

Forgot to attach.

May 27, 2012

Doxygen \todos

by p37sitdu＠lavabit.com

Patch replaces TODOs in dw/* files with \todos so they are listed on Doxygen Todo List. One BUG also replaced with \bug.

May 27, 2012

dillorc and src/keysrc

by p37sitdu＠lavabit.com

By the way Scroogle is closed but it is still present in dillorc.

May 27, 2012

Doxyfile

by p37sitdu＠lavabit.com

By the way new Doxygen supports Markdown[1] and it is enabled by default. It is easier to read and write than HTML. index.doc rewritten using markdown is attached. Existing documentation (especially .txt files) can be converted to markdown too. [1] http://daringfireball.net/projects/markdown/

May 26, 2012

Doxyfile

by p37sitdu＠lavabit.com

I have removed all boilerplate from Doxyfile, now it is much shorter and there are less empty/default vairables. I was looking for some way to change layout to something simplier (no CSS-based tabs for example), but looks it is easier to just disable CSS. Cleaned up Doxyfile attached. I have enabled DOT_MULTI_TARGETS to make building faster and left TODO for Dillo logo.

May 26, 2012

dpid patches

by joerg.sonnenberger＠web.de

On Sat, May 26, 2012 at 11:05:28PM +0400, 123 wrote: > One patch for using random instead of rand. [1] Guessing the intention here, I would recomment to use arc4random on systems that have it. time(0) should likely be spelled as time(NULL). > Reordered headers and removed old comments (what is ckt_write?). umask > is actually in sys/stat.h and not in unistd.h umask in sys/stat.h is correct. Joerg

May 26, 2012

dpid patches

by jcid＠dillo.org

On Sat, May 26, 2012 at 11:05:28PM +0400, 123 wrote: > One patch for using random instead of rand. [1] Ack. > Reordered headers and removed old comments (what is ckt_write?). umask > is actually in sys/stat.h and not in unistd.h Dillo compiles in several OSes/platforms, which sometimes have declarations in different files. This is the to-be-tested point. > (what is ckt_write?). ckd_write() an EINTR-protected write() (see dpid/dpid_common.c). > Also removed expired TODO item about dpi_service.[c|h]. Ack. -- Cheers Jorge.-

May 26, 2012

dillorc and src/keysrc

by p37sitdu＠lavabit.com

dillorc is in the root of repo and keysrc is in src/keysrc. Not a serious issue, but I think keysrc should be located in root too.

May 26, 2012

dpid patches

by p37sitdu＠lavabit.com

One patch for using random instead of rand. [1] Reordered headers and removed old comments (what is ckt_write?). umask is actually in sys/stat.h and not in unistd.h Also removed expired TODO item about dpi_service.[c|h]. [1] https://www.securecoding.cert.org/confluence/display/seccode/MSC30-C.+Do+no…

May 26, 2012

cleanup patches

by Johannes.Hofmann＠gmx.de

On Sat, May 26, 2012 at 03:59:12PM +0200, Alexander Voigt wrote: > Hi 123, > > why not introducing a macro like > > #define LENGTH(X) (sizeof (X) / sizeof (X)[0]) > > which could be used in all these for loops? I think this would make > the code simpler and less error prone. I'm not a fan of hiding this in macros. Something like struct foo * f = malloc(sizeof(struct foo) * 10); for(int i = 0; i < LENGTH(f); i++) { looks even more unsuspicious than with the sizeof stuff visible. Cheers, Johannes

May 26, 2012

cleanup patches

by Hole.destructor＠gmx.de

Hi 123, why not introducing a macro like #define LENGTH(X) (sizeof (X) / sizeof (X)[0]) which could be used in all these for loops? I think this would make the code simpler and less error prone. Best, Alexander

May 26, 2012

cleanup patches

by Johannes.Hofmann＠gmx.de

On Sat, May 26, 2012 at 09:26:39AM -0400, Jorge Arellano Cid wrote: > On Sat, May 26, 2012 at 02:02:17PM +0200, Johannes Hofmann wrote: > > On Sat, May 26, 2012 at 03:02:24PM +0400, 123 wrote: > > > One patch for README, one for dFree (no need to check for NULL) and > > > one for sizeof usage. > > > > thanks, committed. > > BTW, why is it better to have sizeof this way? > > - (sizeof(Css_shorthand_info) / sizeof(CssShorthandInfo)) > + (sizeof(Css_shorthand_info) / sizeof(Css_shorthand_info[0])) This way it stays correct even if someone changes the type of Css_shorthand_info to say CssShorthandInfo2. Not a big improvement, but I like it being consistently done like that. Cheers, Johannes

May 26, 2012

src/colors.c cleanup

by p37sitdu＠lavabit.com

- Fixed indentation. - Added LEN macro. - Reimplemented binary search using bsearch(3). - Changed NOTE: colors can be in any case, they are compared with dStrAsciiCasecmp.

May 26, 2012

cleanup patches

by jcid＠dillo.org

On Sat, May 26, 2012 at 02:02:17PM +0200, Johannes Hofmann wrote: > On Sat, May 26, 2012 at 03:02:24PM +0400, 123 wrote: > > One patch for README, one for dFree (no need to check for NULL) and > > one for sizeof usage. > > thanks, committed. BTW, why is it better to have sizeof this way? - (sizeof(Css_shorthand_info) / sizeof(CssShorthandInfo)) + (sizeof(Css_shorthand_info) / sizeof(Css_shorthand_info[0])) -- Cheers Jorge.-

May 26, 2012

cleanup patches

by Johannes.Hofmann＠gmx.de

On Sat, May 26, 2012 at 03:02:24PM +0400, 123 wrote: > One patch for README, one for dFree (no need to check for NULL) and > one for sizeof usage. thanks, committed. Cheers, Johannes

May 26, 2012

cleanup patches

by iveqy＠iveqy.com

Sry, my bad. Never mind 2012/5/26 Fredrik Gustafsson <iveqy at iveqy.com> > Why isn't the NULL-check needed? free(NULL) has an undefinied behavior... > > /Fredrik > > 2012/5/26 123 <p37sitdu at lavabit.com> > >> One patch for README, one for dFree (no need to check for NULL) and >> one for sizeof usage. >> >> _______________________________________________ >> Dillo-dev mailing list >> Dillo-dev at dillo.org >> http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >> > >

May 26, 2012

cleanup patches

by iveqy＠iveqy.com

Why isn't the NULL-check needed? free(NULL) has an undefinied behavior... /Fredrik 2012/5/26 123 <p37sitdu at lavabit.com> > One patch for README, one for dFree (no need to check for NULL) and > one for sizeof usage. > > _______________________________________________ > Dillo-dev mailing list > Dillo-dev at dillo.org > http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev >

May 26, 2012

cleanup patches

by p37sitdu＠lavabit.com

One patch for README, one for dFree (no need to check for NULL) and one for sizeof usage.

May 26, 2012

just a test msg

by jcid＠dillo.org

Hi there, For those of you wondering what all these tests are about, we were informed of problems with subscribing to dillo-dev by a new member, then we realized delivery was also not working, and today it seems things are starting to work again. More later... -- Cheers Jorge.-

May 25, 2012

just a test msg

by p37sitdu＠lavabit.com

test

May 25, 2012

just a test msg

by rogerx.oss＠gmail.com

> On Thu, May 24, 2012 at 05:24:28PM +0000, corvid wrote: > >test test test -- Roger http://rogerx.freeshell.org/

May 25, 2012