The solution is VPN.[/quote]
the VPN will not help u, if officals want they can detect your ip adrass

But for french poeple (yes, I’m french, sorry for my english and for my president), it still means a lot :

The HADOPI law aim to shut down the internet connection of poeple sharing copyrighted stuff.
To find those poeple, they will use the IP as a single proff.

Talking about SeedFucker or BTpoison.php is only a proof of concept, a way to say to our politics : “your argument is invalid”.

And maybe at last will they accept a better solution than filtering, monitoring, spying and repression.

As for the cache, its like limited freenet, think outside the box.

Bittorrent may not be called bittorrent then. You do not request all the time random pieces from peers but just sometimes a random piece for your cache which can then be used to send it if someone requests a matching hash. One huge swarm, and maybe a hash (for pieces), instead of name, search mechanism based on Kazaa or Soulseek.

It has increase overhead but might be faster than freenet. This will make you, like freenet, not responsible for the (cached) data on your computer because you don’t know what it is (never tried freenet yet, just from reading the infos about it). And for the things you actually did download there is now plausible deniability like with truecrypt.

Its just an idea for evolution.

And not in Java, coz it’s poo. :P

I never said that in relation to the piece-sharing. What I said was “Although this sounds possible, perhaps even plausible, it’s extremely unlikely to happen”

And it is extremely unlikely, so much so that the odds on it happening are so skewed that the chances are it never will.

“data is not really random”

To all intents and purposes it is, and remember that the 256^256 only applies to 256 byte pieces, which are almost never used as they are impractically small. Want a 700MB file? That’ll be 2,867,200 pieces please. Generally pieces are much bigger than 256 bytes for very good reasons.

“An easier solution my be for all clients in a huge single swarm to cache some random pieces of torrents”

Are you seriously suggesting that every client downloads pieces from every torrent currently running on every tracker out there?

And how do you expect these clients to even know about each other?

And do you also mean that those clients never actually make requests for specific pieces which they require for the files they actually want to download? If so, what are the odds of anything ever actually completing?

“They can be uploaded to a request”

Thereby increasing everyone’s exposure and therefore their risk of being associated with something they didn’t even want in the first place.

To see if it has any chance of working it would need to be calculated what happens if everyone is in one huge swarm and all those shared files are online (not knowing which torrent isn’t an issue, the only thing needed is to compare the hash to all hashes of pieces you own).

An easier solution my be for all clients in a huge single swarm to cache some random pieces of torrents (request = just send me one) to spoil investigations. They can be uploaded to a request but never have the rest of the file.

http://wiki.theory.org/BitTorrentSpecification

Indeed matey.

Here’s a good starting point for them…

http://en.wikipedia.org/wiki/BitTorrent_(protocol)

Peace. : )