From toad at amphibian.dyndns.org Sat Dec 1 22:54:30 2007 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sat, 1 Dec 2007 22:54:30 +0000 Subject: [Tech] Freenet 0.7 build 1084 Message-ID: <200712012254.35799.toad@amphibian.dyndns.org> Freenet 0.7 build 1084 is now available. Please upgrade; hopefully your node will do this for you automatically. This build features some significant bug fixes for recent connectivity problems, some FCP fixes, we drop some obsolete code, and the beginnings of opennet announcement (which isn't used yet). Please report any bugs you find to the bug tracker (https://bugs.freenetproject.org ), via IRC, Frost (the freenet board) or support at freenetproject.org. Thanks for helping build Freenet. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/tech/attachments/20071201/7653285c/attachment.pgp From toad at amphibian.dyndns.org Sat Dec 1 23:23:29 2007 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Sat, 1 Dec 2007 23:23:29 +0000 Subject: [Tech] Fcp notes and issues In-Reply-To: <475014B8.108@arcor.de> References: <474FE5AA.4020304@arcor.de> <200711301130.41406.toad@amphibian.dyndns.org> <475014B8.108@arcor.de> Message-ID: <200712012323.32527.toad@amphibian.dyndns.org> Well, in the current API, you can either come up with a unique name, or not have any client-name-specific state i.e. either have no persistent requests or store them all on the global queue. I don't see how any other solution would help - if you start persistent requests, exit, another client steals your name, you give way to that client, then you'll have lost them. On Friday 30 November 2007 13:48, Juergen Urner wrote: > Matthew Toseland wrote: > > > > Collisions result from one of two scenarios: > > 1) The client doesn't have a unique name. This is a bug in the client. > > 2) Two copies of the client are run simultaneously. FCP is intended to be used > > by one computer, clients which care about this can further uniquify their > > names by e.g. adding the local username. > > > > First of all, sorry for taking so much of your time. I am aware that > this is a corner case. > > case1: > if a client can not come up with names that are guaranteed to be unique > within the client its a client bug. True. > > case2: > Correct me if I am wrong, but I'd assume case two applies on unrelated > clients > aswell, not only on multiple instances of the same client. If my assumption > is true, clients have to be prepaired to deal with the fact that a collision > might happen the very next moment. Either this or the node takes over > due to the fact that it is the only instance that can guarantee uniquness > in this case. > > > Sidenote: > I know how to come up with a name that is highly likely to be unique. I > implemented RFC 4122 in Python and am pretty much aware of the drill > and the limitations of of any approach in this direction. > > > Juergen > > > > > > > > > _______________________________________________ > Tech mailing list > Tech at freenetproject.org > http://emu.freenetproject.org/cgi-bin/mailman/listinfo/tech > > -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/tech/attachments/20071201/21971007/attachment.pgp From jUrner at arcor.de Sun Dec 2 04:24:35 2007 From: jUrner at arcor.de (Juergen Urner) Date: Sun, 02 Dec 2007 05:24:35 +0100 Subject: [Tech] Fcp notes and issues In-Reply-To: <200712012323.32527.toad@amphibian.dyndns.org> References: <474FE5AA.4020304@arcor.de> <200711301130.41406.toad@amphibian.dyndns.org> <475014B8.108@arcor.de> <200712012323.32527.toad@amphibian.dyndns.org> Message-ID: <47523383.7020801@arcor.de> Matthew Toseland wrote: > Well, in the current API, you can either come up with a unique name, or not > have any client-name-specific state i.e. either have no persistent requests > or store them all on the global queue. I don't see how any other solution > would help - if you start persistent requests, exit, another client steals > your name, you give way to that client, then you'll have lost them. > > ...or another client may flood mine with leftover requests. Very unlikely case, but no magic either if some future version of the protocol would equip clients to handle their own persistence. Thanks for listening, Juergen From toad at amphibian.dyndns.org Mon Dec 3 12:34:16 2007 From: toad at amphibian.dyndns.org (Matthew Toseland) Date: Mon, 3 Dec 2007 12:34:16 +0000 Subject: [Tech] Fcp notes and issues In-Reply-To: <47523383.7020801@arcor.de> References: <474FE5AA.4020304@arcor.de> <200712012323.32527.toad@amphibian.dyndns.org> <47523383.7020801@arcor.de> Message-ID: <200712031234.19616.toad@amphibian.dyndns.org> On Sunday 02 December 2007 04:24, Juergen Urner wrote: > Matthew Toseland wrote: > > Well, in the current API, you can either come up with a unique name, or not > > have any client-name-specific state i.e. either have no persistent requests > > or store them all on the global queue. I don't see how any other solution > > would help - if you start persistent requests, exit, another client steals > > your name, you give way to that client, then you'll have lost them. > > ...or another client may flood mine with leftover requests. Very > unlikely case, but no > magic either if some future version of the protocol would equip clients > to handle > their own persistence. There is nothing I can do about this afaics. If you need persistent non-global requests then USE A UNIQUE NAME. If not, then use a random name. > > Thanks for listening, Juergen -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://emu.freenetproject.org/pipermail/tech/attachments/20071203/caff7cac/attachment.pgp From batosai at batosai.net Mon Dec 3 14:22:05 2007 From: batosai at batosai.net (Julien Cornuwel aka batosai) Date: Mon, 03 Dec 2007 15:22:05 +0100 Subject: [Tech] FMS Message-ID: <4754110D.40008@batosai.net> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Someone just created a Freesite and a dedicated board (fms) which goal is to design a Freenet Messaging System : USK at 0npnMrqZNKRCRoGojZV93UNHCMN-6UU3rRSAmP6jNLE,~BG-edFtdCC1cSH4O3BWdeIYa8Sw5DfyrSV-TKdO5ec,AQACAAE/fms/3/ I really think it would be a good thing if the core developers would take part to that process as it could succeed in a network-friendly, spam-resistant and flood-resistant system. If the design is correct and approved, maybe someone (maybe me) would find the motivation to implement it as a plugin. Regards. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHVBEMo6N05NzaOvURAiTLAKCSNkgVJYSDqMiqwqJi39pDkfN2IACgwIye /sxiqMhQhK0i3j+rpIlebJ8= =8XDR -----END PGP SIGNATURE-----