November 2008 - Dillo-dev - lists.mailman3.com

Dillo too fast?

by thomas-forum＠orgis.org

Did anyone else encounter this from google? Not sure if this is something specific in dillo's network behaviour... > We're sorry... > ... but your query looks similar to automated requests from a computer virus or spyware application. To protect our users, > we can't process your request right now. It's at least the second time I got this now, after issuing a search, seeing that there was a typo, resissuing. It is not that rare that this happens, but it is rare that google slaps me in the face for it ... and I _think_ it has been dillo before, too. But not sure. Anyhow, does someone know what is behind that "virus check"? > If you're continually receiving this error, you may be able to resolve the problem by deleting your Google cookie and > revisiting Google. For browser-specific instructions, please consult your browser's online support center. Hm... I don't have any cookie from 'em. Perhaps that is the key? Alrighty then, Thomas.

Nov. 7, 2008

Another mention of Dillo-2

by onepoint＠starurchin.org

"Dillo 2.0 is fast, but limited" http://www.linux.com/feature/151983 Summary: "It's *fast*, even faster than Dillo-1, but too limited to be of use to much people.". It singles out lack of JavaScript, pointing out that most business sites need it (although I'd imagine most business sites would need full SSL support too). Jeremy Henty

Nov. 6, 2008

Repost: D_SUN_LEN cleanup (and a typo fix)

by jcid＠dillo.org

On Wed, Nov 05, 2008 at 02:26:48PM +0000, Jeremy Henty wrote: > > This is a repost of three tidy-up patches that have been left hanging > without resolution. Please comment. > > 1. Remove unused D_SUN_LEN declarations from DPIs. (The DPIs connect > to their sockets with accept() which doesn't use D_SUN_LEN.) > > 2. Use D_SUN_LEN whenever calling connect() on a struct sockaddr_un. > (Some of the calls already did this, this patch makes all of them > do so.) > > 3. Update a GPL reference in a comment from version 2 to version 3. Committed! -- Cheers Jorge.-

Nov. 5, 2008

Repost: D_SUN_LEN cleanup (and a typo fix)

by onepoint＠starurchin.org

This is a repost of three tidy-up patches that have been left hanging without resolution. Please comment. 1. Remove unused D_SUN_LEN declarations from DPIs. (The DPIs connect to their sockets with accept() which doesn't use D_SUN_LEN.) 2. Use D_SUN_LEN whenever calling connect() on a struct sockaddr_un. (Some of the calls already did this, this patch makes all of them do so.) 3. Update a GPL reference in a comment from version 2 to version 3. Regards, Jeremy Henty

Nov. 5, 2008

Re: Interested in joining dillo project

by jcid＠dillo.org

On Fri, Oct 31, 2008 at 11:43:35PM +0100, PHELIZOT Yvan wrote: > Hi, > > That me again. And i have a lot of questions: > About management: > * Does we have a functionnalities/features list? We had one inside the funding initiative in the past. It was purposedly removed from the web site because it was not updated (obsolete), and because the funding effort yielded no results. You can still find some info here: http://www.dillo.org/funding/funding.html (go to "Technical Overview"). > For example, i have > seen that png and jpeg are not supported, so does it included in the > file...? That's false. Where did you find that misinformation? > * Is there a task list? to know what to do and with which priority > > Dev : > * How many developpers, testers, ... work on the project? Please check the website. "Current Plans", "Authors", etc. > Software: > * Does the software has a "quirk" mode? Something akin, give read to dillorc. w3c_plus_heuristics=YES -- Cheers Jorge.-

Nov. 5, 2008