Jorge wrote:
On Tue, Jul 28, 2009 at 10:01:12PM -0700, bf wrote:
--- On Fri, 7/24/09, Jorge Arellano Cid <jcid@dillo.org> wrote:
From: Jorge Arellano Cid <jcid@dillo.org> Subject: [Dillo-dev] Planning To: "Dillo mailing list" <dillo-dev@dillo.org> Date: Friday, July 24, 2009, 11:33 AM Hi,
? Here? are? some? pending? issues which I've partially sorted by priority (at least the top half). Please add the missing ones and let's try to finish sorting it, with a view to planify our work.
* Add blocker (this also has to do with privacy). ???A? full? RE-based? one? may? have? significant? overhead (test required),? but? simple string-matching may do most of the trick. I've? also? thought? for? a? long? time? that? a "don't load from other? sites"? preference? may? help a lot. The whole topic needs some thought but it's not hard to implement. ???e.g. doubleclick.
Or you could just point users to privoxy, junkbuster, WWWOFFLE, and/or polipo.
Perhaps so. I would like some way to make it so that dillo would always ask me before following redirections, but maybe I should just argue for a pref for that specific thing rather than going for a whole general adblockerplus deal.
I don't see any mention of a limit on concurrent connections that was proposed earlier, and as far as I know it hasn't been implemented. In addition to the reasons given earlier, it is very frustrating to have to implement your own traffic-shaping just to avoid being blocked by a rate/connection-limiting firewall, or to avoid being blocklisted by a site you had hoped to visit. I'd hate to see dillo gain a reputation as a problematic UserAgent, and perhaps be blocked by some heavy-handed administrators.
If I had magical make-Jorge-do-my-bidding powers, this would be on the top of my list.
* Document CCC, dlib and dillo in doxygen format.
The situation seems to me as follows: pre-doxygen: easy-to-read code, useless documentation post-doxygen: hard-to-read code, useless documentation
Please Johannes or corvid, sort the titles of the items we have so far in this thread so we can sort them and do our planning.
I guess I'll paw through it and stuff everything into Plans.html.