News for hackers. Stuff that matters.
Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @06:31AM (#6242760)
Email does not have to be real time.
Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @06:57AM (#6242837)
Maybe realtime was not the best choice of a word, but Freenet cannot handle email in any case.

Freenet is a global distributed p2p file database. Email does not fit that medium.

Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @08:09AM (#6243123)
> Email does not fit that medium.

Why not?

Email can be implemented in a global p2p file database. Every "email" simply adds another file. Privacy can be ensured with encryption (as long as the encryption is not broken, at least). See existing Freenet message boards for an example.

It may not be Internet RFC821/822 (and subsequent standards) Email, but it is email.

What part of this will not fit the Freenet model?

Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @08:16AM (#6243163)
How would you send the new file to your recipient?
Re:Forced Exposure by rlpb on Tuesday August 20, 2013 @08:29AM (#6243231)
The same way that message boards do this already on Freenet.

See https://freenetproject.org/understand.html.

Something like:

Publish a site using a USK (perhaps one per recipient), containing all encrypted messages sent recently. Update the site with an additional message when you need to send one. The recipient checks it for updates periodically.

I'm not sure if my understanding is inaccurate, but since Frost already achieves something like this, I don't see that it's automatically impossible such as what you seem to be inferring.

In fact, now that I look, there's: https://freenetproject.org/freemail.html

I'm dubious about the safety of using non-Freenet clients, but surely this demonstrates that it's possible to build a messaging system built over Freenet?

Re:Forced Exposure by kaoD on Tuesday August 20, 2013 @08:44AM (#6243302)
Yep, you're right.