This is completely pointless. Simply post the article (with links to older editions) under an USK, and give that USK key to whoever you want to be able to read it.
>From an application developers perspective, Freenet is not a network, it is a distributed file storage system. The concept of sending a file to a receiver is meaningless in this context; you simply write the file to Freenet, after which everyone who knows the key can read it, at least in theory. Trying to build a network on top of a filesystem (Freenet API) running over a network (Freenet FNP connections) running over a network (Internet) is an extremely misguided idea. On Wed, 16 Jan 2008 15:53:02 +0000, Michael Rogers wrote: > This is an old idea of mine that could be implemented with N2NMs - similar > to Syndie but with an F2F distribution mechanism. > > A journal is a series of articles signed with the author's private key. > The articles in the journal may be written by the user or reposted from > other journals, either manually or automatically (syndication). When a > user writes or reposts an article it's sent to her online friends and > queued for her offline friends. Articles can be marked 'friends only', in > which case they should never be reposted, but obviously this can't be > enforced - you just have to trust your friends. > > A user who reads a reposted article and wants to subscribe to the author's > journal (to read and/or syndicate it) sends a subscription request to the > friend in whose journal she read the article. If the friend is already > subscribed to the requested journal, she forwards subsequent articles to > the requester. If the friend reposted an individual article but doesn't > subscribe to the journal herself, she can forward the request to the > friend in whose journal she read the article, and so on. (Requests to > offline users are queued.) Eventually the publisher or a subscriber will > be found and the new subscription path can be established. > > Any thoughts? > > Cheers, > Michael
