Hi Alan, On Mon, Mar 19, 2007 at 08:45:38AM -0300, Alan Carvalho de Assis wrote:

Hi Jorge,

2007/3/12, Jorge Arellano Cid <jcid@dillo.org>:

...

Hi Alan.

Unfortunately there's no much point in doing it without developers...

(except for the hope of attracting developers :-)

I don't understand why nice projects as Dillo, Linux-Tiny and other don't attract developers.

Actually, Dillo attracts developers, it is the high time dedication and specific expertise it demands what stops most of them.

...

I'll watch the video tis week!

And I did. Congratulations, a very interesting demo!

I think will be hard to integrate Dillo inside it, the BIOS flash (2MB) don't left space, but maybe using LZMA I will get 500KB.

jcid@infinity:~/C/Dillo/proto/dillo-f15/src$ ls -l dillo-fltk.gz -rwxr-xr-x 1 jcid users 373895 Mar 20 08:14 dillo-fltk.gz*

Did you tested to compile Dillo FLTK with uClibc?

Not personally but other guys have succeeded in doing it. -- Cheers Jorge.-

Hi, first sorry about pre-posting. You are right, but Jorge can keep it closed if he want. We need to convince he it is not the best way. He will not be successful keeping it closed or keeping tight control over dillo resource inclusion. People needs i18n, ssl, javascript, flash, etc... Maybe a best approach can be keep resource configurable, then you can compile dillo for a deep embedded system with minimal resources or compile it for a small linux distro with full resources. God save Dillo, Alan 2007/3/20, Mark South <marksouth2000@yahoo.co.uk>:

Hi.

I should introduce myself, because I've never posted, although I've been lurking on this list for a long time. I'm more a distro hacker than a browser hacker. But enough about that.

I still remember how I was delighted when I discovered dillo, and how small it was, and its amazing power-to-weight ratio.

There is clearly a need for a browser like dillo. Firefox, Seamonkey, Opera, all use a lot of memory and run slowly on all but modern machines. There are numerous Linux distros consisting entirely of software that will run happily on a 64 MB PII, except for the huge lump of a browser. DSL has Firefox and Puppy has Seamonkey, for example. (They both have dillo but don't consider it sufficient on its own.) This is something like putting armour plate on a formula one car.

If dillo had tabs (without prescribing the window manager), multiple languages, and solid enough cookie and SSL supprt that one could read webmail from it easily, it would be the browser that fit most perfectly with the small Linux distros. And yet they are all talking about dropping it because it's no longer much use on the modern web.

And yet every day I wish that I had in my hands a dillo that was just that tiny bit more capable than 0.8.5 is, and was known to be under active development and maintenance. Something more general than lynx/links/elinks and a lot lighter on resources than Gecko-based browsers and that ilk.

Like many others, I have gradually become pessimistic about dillo ever being revived. I have watched it being dropped from distro after distro, and even pleaded with the port maintainer (unsuccessfully) for it to be kept in OpenBSD.

Clearly there is a problem here, and it's not to do with FLTK not releasing (they do) or lack of interest in a light-to-mid-weight browser, because loads of people want exactly that.

--- Jorge Arellano Cid <jcid@dillo.org> wrote:

...

On Mon, Mar 19, 2007 at 08:45:38AM -0300, Alan Carvalho de Assis wrote:

...

I don't understand why nice projects as Dillo, Linux-Tiny and other don't attract developers.

Sourceforge has like 100,000+ projects listed. There is no shortage of willing developers out there. So why doesn't dillo get developers?

One reason for projects to lose their attractiveness is when project ownership narrows too far. This is happening right now with at least 2 Linux distros that I could name, but won't. People in the community are becoming reluctant to contribute to a project that is held under the narrow control of a small cadre.

On the other hand, projects that have wide ownership are thriving and multiplying.

...

Actually, Dillo attracts developers, it is the high time dedication and specific expertise it demands what stops most of them.

Are you sure about that? I ask because I'm not convinced it's a shortage of smart people in the world.

I worry that it's the relentless focus on getting funding before development starts again, or the indecision caused by being unable to decide whether to proceed with forking off a new project from 0.8.5, the last version that would build on multiple platforms, or to wait for Jorge to release the FLTK code that he has and let people work on it.

If Jorge were to declare that he will never release the FLTK port, there are people out there who would probably continue development starting from the 0.8.5 codebase.

If Jorge were to declare that he will make the existing FLTK code available for others to develop, I'd be surprised if several people didn't step forward to help.

So, from where I'm sitting, it looks like the real problem is uncertainty about which way to go, and perhaps if Jorge were to let go of either his hopes of making a living from dillo or of total control of the dillo code, there might be a way forward for further development.

I would further suggest that if Jorge doesn't have the time for development work on dillo, he would nevertheless be the first choice for the overall architect of the ongoing development. Being architect of a successful project that releases useful code may be a better result, career-wise, than being commercial owner of a project that failed to release a complete unit version and faded away. But that would be for Jorge to decide. I hope that he will decide, one way or the other, and decide soon, and make that decision public soon as well.

Now, I expect that I'll get a few hasty flames in response to this mail, but I don't mean to attack anyone personally. That said, there is a *very* small number of people who could make a huge difference to the dillo project by their actions, and I hope that they will read this message as constructive.

I would still hope, and would definitely like to be able, to draw on dillo as a working solution in the future, as would many others.

Sincere best wishes to *all* recipients on the dillo-dev- list, Mark

PS Apologies for the length of this message. I guess it shows that I kept quiet for too long.

___________________________________________________________ Now you can scan emails quickly with a reading pane. Get the new Yahoo! Mail. http://uk.docs.yahoo.com/nowyoucan.html

_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

-- ------------------------------------------------------------ | Alan Carvalho de Assis | ------------------------------------------------------------ -- Não importa o que os outros irão pensar, A cura para a infelicidade é a felicidade

Hi, 2007/3/20, Justus Winter <4winter@informatik.uni-hamburg.de>:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

Hey folks :)

I completely agree with Marc on this topic. I have been following this list for some time now and I have heard all kinds of people proposing interesting uses for dillo and I like to add one more to this list.

I have done some research in web security, mostly session riding based attacks. Dillo, with its missing javascript interpreter and css engine being a feature this time, is not vulnerable against most session riding attacks.

Though most session riding attacks require javascript, it has been shown, that port scanning and web server fingerprinting is possible using only html and css.

So why not use dillo on workstations in your internal network to protect your intranet web applications against malicious javascript and css?

Also with its small codebase (compared to geckos), some kind of auditing might be possible.

But on the other hand, more and more web sites and web applications require css (which is definitively a good thing) and javascript (which may not be a good thing). The web is a moving target, and everyone developing a web browser is playing catch up with the standards and with the ever growing demands of users and developers.

And I for one think, that no one of the big four is doing very well...

Dillo development has stagnated. So with every day that passes, dillos practicability, the number of users and the number of developers interested in doing some work for dillo decreases.

I can understand Jorges bitterness, but this wont get dillo anywhere. If its more work for a company (-> money and time) to get dillo up to speed to meet their needs than to strip down gecko or khtml until it fits into their devices (or whatever they want to do with it), they wont choose dillo.

With every single day, the value of the dillo codebase decreases. And on some day it wont matter if it is ever released or not, because it is completely useless for the applications and sites out there. Maybe this day has already passed without any one noticing.

By the way, I keep referring to "the code". Yes I know that the GTK branch is out there. Yes, I have taken a look at it and yes, I began to develop an plugin, but I realized that the plugin interface was lacking some important things (registering uri handlers comes to mind - it is hardly an plugin if you need to touch and recompile parts of dillo).

So I stopped before I began any serious work. Dillo felt dead. No one is going to invest time in an project which was somewhat abandoned by its main developer. No offense, but this is how it feels.

Most free software developers are working on these kind of projects in their leisure time, they want to have fun. If dillo wants to attract developers, developing dillo needs to be fun. There are lots and lots of free software projects that discussed how to make developing their software fun. Things like giving write access to repositories to developers interested in development, creating branches or creating a wiki could help.

It is somewhat true, that one or two developers working on dillo full time would be nice, but as long as no one pays for this, I don't see how this is possible. But this all or nothing attitude will kill dillo in the long term.

Jorge, consider releasing this patch of yours. You have got very little to loose (or am I missing something?) but this might spark some interest in dillo development again.

Just my thoughts...

Sure, I agree with you! As can be seen at: http://www.dellideastorm.com LinuxBIOS is the 10 most voted idea to Dell implement. If you get Dillo running inside the LinuxBIOS the interest in this web-browser will increase newly, then now it the time to Dillo show its worth. Jorge, consider this.

Cheers, Justus

Cheers, Alan

Hi Jorge, 2007/3/31, Jorge Arellano Cid <jcid@dillo.org>:

Guys, please allow me to say that these comments hurt...

I do sincerely appreciate the interest that you show in Dillo; to me it means you understand the concept of it and have hopes in the project evolving to its vision.

Me too. I dedicated seven years of my life to developing Dillo full time. Living on donations, in poor neighborhoods, rejecting high salaries, and trying to explain my (non-technical) family I was not crazy for doing it. All this time the code has been open and GPLd. Anyone could have done the same I did for the project.

Sebastian made a huge effort too. Having a job and developing a web browser is a very demanding task, and he did even more than that. I highly respect the man.

In Germany we decided with him to keep the Dillo FLTK2 closed until we both agreed to release. This was mainly because a company was to hire us to develop it and declined on the last minute.

I once asked in this list how many developers were willing to work on Dillo FLTK2 if released. One answer still stands.

From some time ago I think it would be good to release the new code. I have emailed several times with no answer.

Finally, I currently fail to see I'm the problem, but it could be. No person saying otherwise is a strong sign.

I appreciate your dedication to Dillo, you was (are) a good father to this project. As all father you want to protect your child and have fear the way it can follow. But Dillo need to evolve to support features only existents in modern browsers as i18n, javascript, https, tabs, flash (gnash), etc. I know you always had fear that Dillo become very fat and run away from the original intention of project. But maybe you can found a way to balance between these 2 variables (features / size and/or speed), maybe a modular system (using the Dillo plugin system for example). Keeping the source code closed you will not get developers and day after day this code base will become deprecated and don't will get new features. This is the evolution theory of Darwin, if it don't evolve it will die and will be replaced by other (Minimo?, NetSurf?, other). Please Jorge think about this. Now that Linux is become the mainstream on smart phone market, Dillo can get a break (get a chance), but keeping it closed source (on closed curtains) will be more difficult to company see the Dillo potential.

-- Sincerely Jorge.-

Best regards, Alan

* Matthias Franz:

On Fri, Mar 30, 2007 at 10:59:58PM -0400, Jorge Arellano Cid wrote:

...

I once asked in this list how many developers were willing to work on Dillo FLTK2 if released. One answer still stands.

Let's up that number then. Make it two. When (not if) Dillo FLTK2 is released, I will gladly contribute to its advancement, including working on its core.

But it may not the best approach to ask people to declare in advance that they will contribute to Dillo.

I cannot say I do not disagree with that. Regards, Alexander -- PGP key available

On Sun, Apr 01, 2007 at 06:47:15PM +0200, Alexander Becher wrote:

Let's up that number then. Make it two. When (not if) Dillo FLTK2 is released, I will gladly contribute to its advancement, including working on its core. +1. Time is scarce for me at the moment, but I'm very interested in contributing to Dillo on FLTK2.

Leslie -- NEW homepage: https://viridian.dnsalias.net/~sky/homepage/ gpg --keyserver pgp.mit.edu --recv-keys DD4EBF83

Hi Jorge, 2007/4/5, Jorge Arellano Cid <jcid@dillo.org>:

... sic In fact, I think it was more or less 6 months ago, after some emails with Andrew Tanenbaum, who finally helped me to see that it was a good time to release the code again.

Since then, I've tried to contact Sebastian to agree on this.

Then you just needs a "go" signal from Sebastian? I hope that Sebastian turns on the green light to Dillo FLTK source code. Thank you, Alan

So, I assume that Jorge has not been able to get Sebastian to respond to his calls? It looks like Dillo is on its way to becoming history....what a sad way to end.... Trotter --- Jorge Arellano Cid <jcid@dillo.org> wrote:

Guys,

Once again I want to thank you for the appreciation you have for Dillo as a project.

Now, if you read my original message again, you'll find:

...

Sebastian made a huge effort too. Having a job and developing a web browser is a very demanding task, and he did even more than that. I highly respect the man.

In Germany we decided with him to keep the Dillo FLTK2 closed until we both agreed to release.

and

...

From some time ago I think it would be good to release the new code. I have emailed several times with no answer.

In fact, I think it was more or less 6 months ago, after some emails with Andrew Tanenbaum, who finally helped me to see that it was a good time to release the code again.

Since then, I've tried to contact Sebastian to agree on this.

--

On the technical part:

...

But Dillo need to evolve to support features only existents in modern browsers as i18n, javascript, https, tabs, flash (gnash), etc.

- i18n : this was the main reason for choosing FLTK2 (utf-8). - https: I started this plugin and also wish it can be improved (later Garrett Kajmowicz helped a lot with this). - tabs : I also want Dillo to have TABs. It may take to much time until WM TABs support is as good as internal TABS. I designed a Dillo FLTK2 UI where this is easy to add (one of these days I may code it up... :-) - flash: This depends on a external interpreter. I have no problem in making the hooks. - javascript: This also depends on a external VM, and a supporting framework. It can be done but requires time. I'm not opposed as long as it can be disabled/enabled because it comes with severe security/privacy risks. - CSS : All of us want this! Sebastian made a huge and accurate work to make the CSS model a part of the internal widget structures. We only need to hook the parser. We even showed a prototype in France 2005 at LSM

Again, once released, the code will not improve alone, it needs dedicated developers/supporters willing to put their part in order to make the vision we share happen.

<<Long life to Dillo!>>

-- Cheers Jorge.-

PS: For those willing to take our word at face value, I want to state that it was never our intention to sell the code to proprietary hands. BTW, we never did.

_______________________________________________ Dillo-dev mailing list Dillo-dev@dillo.org http://lists.auriga.wearlab.de/cgi-bin/mailman/listinfo/dillo-dev

__________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com