Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
- Original Message - From: David McNab [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Thursday, May 03, 2001 3:53 PM Subject: Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now! Question: Did you seperate presentation and functionality like a good OO designer? To a fair extent, yes. I've given it a try. But after a 7 year break from programming, I've only recently started converting my thinking from structured design/programming to OO, and switching from C to C++, so while I've tried to achieve a reasonable level of encapsulation, you will inevitably find faults with the design. For instance, classes don't follow a strict hierarchy - they tend to invoke each other willy-nilly. This is probably sacrilegous to OO purists. Don't worry, I'm hardly an OO purist. Also, GTK+ is basicly all written in plain C, but is still very object oreinted, which is good. ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
David McNab wrote on 4/29/01 5:30 pm: From: Ian Clarke [EMAIL PROTECTED] rg Thanks for your questions, Ian. Please take the time to digest my response. I have some concerns over this approach. What is required for someone to access FreeWeb? I get the impression that it: * Is Windows only I've had reports of it working in Linux under Wine. But that's not an excuse. I have only recently learned some of the basics of Windows GUI programming, and know nothing about native Linux GUI. To run there, much or most of it will need to be re-written for (say) KDE or Gnome. You'll note from the website (http://freeweb.sourceforg e.net) that I'm inviting experienced KDE and Mac programmers. OK, I knew I would have to learn GTK++ at some point, so it might as well be now. That will get anyone with GTK++ installed working with it (including people running KDE and even some Windows and Mac users (I think)). Question: Did you seperate presentation and functionality like a good OO designer? Timm Murray --- Theory is when you know how it works, but fails. Practice is when something works, but you don't know why. Here, Theory and Practice come together. Nothing works, and nobody knows why. ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
On Mon, Apr 30, 2001 at 12:28:16PM +1200, David McNab wrote: When a site is published, a DNS record with the site's SSK public key and the site's domain name is written to this key index. A 'DNS daemon' harvests these records and writes them to another SSK - the FreeWeb DNS SSK, whose public key is hard-wired into the FreeWeb software. I trust that I'm not going to be asked to explain why the FreeWeb DNS SSK's private key is not also built into FreeWeb ;) Ok, but this basically gives the controller of that private key (namely you) the power to censor any sites which are linked to via your DNS mechanism (by refusing to copy them into the private subspace). The system could also be shut down by spamming the submission key index. This defeats the whole point of Freenet. It is also totally unnescessary, if people want friendly ways to access their sites in Freenet, why not use KSKs - that is what they are there for? This additional layer is unnescessary and encourages incompatabilities since only FreeWeb users will be able to access sites which are advertised with a .free domain - where as it would be trivial to make FreeWeb 100% compatable with existing tools by abandoning this mechanism. Ian. PGP signature
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
From: Ian Clarke [EMAIL PROTECTED] This additional layer is unnescessary and encourages incompatabilities since only FreeWeb users will be able to access sites which are advertised with a .free domain - where as it would be trivial to make FreeWeb 100% compatable with existing tools by abandoning this mechanism. Not true. The name of the existing DNS index is freeweb0.1a-1 The entries on that index are machine-parseable, in the form: freeweb:site-ssk-public-key/SSKpath:site description Any, repeat, *ANY*, freenet user can surf FreeWeb sites. David ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
I'm in irc.debian.org#freenet Got time for a quick chat? - Original Message - From: Ian Clarke [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Friday, May 04, 2001 11:48 AM Subject: Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now! ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
From: Ian Clarke [EMAIL PROTECTED] Thanks for your questions, Ian. Please take the time to digest my response. I have some concerns over this approach. What is required for someone to access FreeWeb? I get the impression that it: * Is Windows only I've had reports of it working in Linux under Wine. But that's not an excuse. I have only recently learned some of the basics of Windows GUI programming, and know nothing about native Linux GUI. To run there, much or most of it will need to be re-written for (say) KDE or Gnome. You'll note from the website (http://freeweb.sourceforge.net) that I'm inviting experienced KDE and Mac programmers. If no-one steps forward, then I'll go ahead in time and learn KDE GUI programming myself and cut a Linux version. As for a Mac version - that'll take longer, since I don't have a Mac and am hard put to justify purchasing one. There is absolutely *NO* intention of it remaining Windows-only. Windows is just a convenient platform for the initial proof-of-concept, which this alpha release essentially is. * Is closed source (I find the argument that the code is too disorgainised to release yet to be somewhat unconvincing) FreeWeb uses JNI to invoke Freenet java methods, particularly CLI clients, and freenetmirror. Note that it sets the freenet.CLI.library flag, which has been removed in the latest release of Freenet - without this flag, FreeWeb will fall over in the middle of publishing sites. (I did ask on dev for the library flag to be left intact for a while - this was ignored) Thus, FreeWeb requires a retrograde Freenet - 0.3.7.0 thru 0.3.8.1, or else it won't work. :(( Currently I'm developing an FCP C library called ezFCPlib, a portable, programmer-friendly API, which will replace the whole back end. Expected time of implementation (with support of much of the old and new freenet metadata) is one week. On the surfing side, FreeWeb uses FProxy - I'm also to replace the proxy's back end with calls to ezFCPlib, and am rewriting 80% of the proxy server code (in response to complaints of the proxy code blocking cookies, plus my total dissatisfaction at the present state of the proxy code). I could release source now, but it won't work with latest freenet, also, it will have little architectural resemblance to what FreeWeb is very shortly to become. The source as it stands will be misleading. Plus, it will encourage bad freenet programming practice. But if people find the delay in source release unacceptable, even given the above, I'll release it. Be warned though - it's a mess. I'd probably put it out in a 'daily zip' format. I would much rather put it out when I've done the migration to FCP. In medium and longer term, what's the problem with a slight initial delay. One year from now, who's gonna give a damn that I took 3 or 4 weeks to release source? * Relies on some central DNS server to convert .free domains to FProxy domains That is *NOT* true! FreeWeb includes a program called 'fwgetdns', which reads all the keys in the FreeWeb in-freenet keyindex and converts them into DNS records for a user's local cache. The doco explicitly tells the user how to delete this cache, in situations where privacy of access to their PC may be compromised. Therefore, this 'some central DNS server' is a convenience, not a requirement. When a site is published, a DNS record with the site's SSK public key and the site's domain name is written to this key index. A 'DNS daemon' harvests these records and writes them to another SSK - the FreeWeb DNS SSK, whose public key is hard-wired into the FreeWeb software. I trust that I'm not going to be asked to explain why the FreeWeb DNS SSK's private key is not also built into FreeWeb ;) I am in total agreement with Brandon's supportive correspondence, and will be adding a facility whereby anyone can set themself up as a DNS registry. In this scenario, FreeWeb DNS registrars would be encouraged to enable their registries to harvest all records from all other registries, so that every registry ideally has all records. Also, end surfers can nominate a 'hit order' for registries - for all .free requests, they can nominate the search order among the available registries. If one registry starts suffering DOS attacks, say, users can drop that registry from their list. Now that's another topic - FreeWeb DNS is totally vulnerable to DOS attack if the name of the key index is easily known. But the only alternative is to use some out-of-band means for DNS registration. * Mandates that anyone who wishes to use a .free domain uses FreeWeb, thus forcing them to tolerate the above-mentioned restrictions. I can see how one could form such a perception. That is certainly *not* the intention. To allay fear and loathing, I'll put up an algorithm document which will allow anyone to access FreeWeb. But you don't even need this. To publish sites to .free, and to surf such sites, all anyone needs to know is: 1) the in-freenet key index
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
On Sun, Apr 22, 2001 at 08:44:27PM -0700, Mr . Bad wrote: "DM" == David McNab [EMAIL PROTECTED] writes: DM For example, Mr Bad, how would you like people to be able to DM click on: www.pigdog.free ? Sure! Why not? Sorry, but this FreeWeb thing is zinging way over my head. I guess I don't quite understand it. But OK! Sounds fine! Definitely got the buzz going on Slashdot, for example. I'll take the following domains please: nbc.free mcdonalds.free coke.free cocacola.free coca-cola.free microsoft.free intel.free freenetproject.free markjroberts.free lesbiansnails.free rebirthing.free -- # tavin cole # # "The process of scientific discovery is, in effect, # a continual flight from wonder." # - Albert Einstein ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
On Mon, Apr 23, 2001 at 12:14:35AM -0500, Owen Williams wrote: On 23 Apr 2001 01:02:19 -0400, Tavin Cole wrote: Why do I get the idea that ICANN wouldn't like the idea of people setting up their own top-level domains? Never you mind that, because ICANN and he did! hehehe now everyone go use my software because it has no single point of failure and works and stuff! http://www.sit.wisc.edu/~ogwilliams/FreeSearch/ owen Well, you forgot the one really big single point of failure... Freenet! -- # tavin cole # # The process of scientific discovery is, in effect, # a continual flight from wonder. # - Albert Einstein ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now!
I need a site SSK public key for each of these. So for each domain you submit, you'll need to have a pre-existing site at: 'freenet:MSK@SSK@somedamnsskpublickey/domainname//' For example, if you want microsoft.free, I'll need you to create a DBR-based MSK site: freenet:MSK@SSK@my-ssk-public-key/microsoft// Note - omit the '.free' from your subkey! Note also - FreeWeb uses freenetmirror as its upload engine, so any site uploaded with freenetmirror is compatible (as long as it uses DBR). Cheers David - Original Message - From: Tavin Cole [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, April 23, 2001 3:50 PM Subject: Re: [freenet-chat] Attn - all freenet site authors - grab your FreeWeb domains now! On Sun, Apr 22, 2001 at 08:44:27PM -0700, Mr . Bad wrote: DM == David McNab [EMAIL PROTECTED] writes: DM For example, Mr Bad, how would you like people to be able to DM click on: www.pigdog.free ? Sure! Why not? Sorry, but this FreeWeb thing is zinging way over my head. I guess I don't quite understand it. But OK! Sounds fine! Definitely got the buzz going on Slashdot, for example. I'll take the following domains please: nbc.free mcdonalds.free coke.free cocacola.free coca-cola.free microsoft.free intel.free freenetproject.free markjroberts.free lesbiansnails.free rebirthing.free -- # tavin cole # # The process of scientific discovery is, in effect, # a continual flight from wonder. # - Albert Einstein ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat ___ Chat mailing list [EMAIL PROTECTED] http://lists.freenetproject.org/mailman/listinfo/chat
