Mar 04, 2014, 17:54 pm
In this thread I'm referring to this project:
https://pirates-forum.org/Thread-How-The...p-For-Good
I'm mainly just submitting my thoughts here, I actually had the idea a few weeks before the TorrentFreak article but I'm not active enough to undertake such a project. It was more of a thought exercise. This is my idea of the implementation, as there isn't much technical details about your development mine may be drastically different, so uhh take from it what applies. Also this could be done a bit broader, like for anyone to host their site on P2P, the site users would opt in to host. Would be very good for things like WikiLeaks or Wikipedia or any free, open-source collaboration as those organizations often have trouble with funding for servers.
My implementation would have most nodes hosting a large part (or all like Bitcoin?) of the torrent database, a user database and a staff database. The user database is there so people can post torrents and comments under an alias - just a username, status (VIP, trusted, etc.) and public PGP key for that username. This will prevent impersonation and malicious edits by attackers. Basically when submitting torrents under a username or performing edits you would PGP sign the submittal. For anonymous additions there would be no need but they cannot edit or remove their torrents.
Also I think for removing torrents by staff (TPB does this in a few exceptional cases right? like child porn or whatever) there can be PGP keys in the staff DB. When a request is signed with these it is performed on whatever torrent in the same way the owner could. They could also elevate user statuses to VIP and Trusted and whatnot.
An initial submit would be the same as a "propagation" submit, the nodes would not know they are the first to receive it. Propagation submits would happen in the first 12 hours a torrent is submitted (could be adjusted later.. probably takes a lot less) which nodes would know from the timestamp.
It has to propagated so that it is dispersed among most of the network so it doesn't get "lost".
I think the interface would be best implemented as a separate application like I2P or Tor rather than a browser bundle (Why not both?
). You would navigate to 127.0.0.1:666/tpb for example and be greeted with your LOCAL copy. Then maybe for searches if your local torrent db does not have the torrent you can always get it to start messaging nodes with the search to see if there is torrents it doesn't have. To reduce internet usage maybe they could send a list of just magnets and it will request back the magnets it doesn't have.
Well I hope this is helpful for someone,
AwfulProgrammer
https://pirates-forum.org/Thread-How-The...p-For-Good
I'm mainly just submitting my thoughts here, I actually had the idea a few weeks before the TorrentFreak article but I'm not active enough to undertake such a project. It was more of a thought exercise. This is my idea of the implementation, as there isn't much technical details about your development mine may be drastically different, so uhh take from it what applies. Also this could be done a bit broader, like for anyone to host their site on P2P, the site users would opt in to host. Would be very good for things like WikiLeaks or Wikipedia or any free, open-source collaboration as those organizations often have trouble with funding for servers.
My implementation would have most nodes hosting a large part (or all like Bitcoin?) of the torrent database, a user database and a staff database. The user database is there so people can post torrents and comments under an alias - just a username, status (VIP, trusted, etc.) and public PGP key for that username. This will prevent impersonation and malicious edits by attackers. Basically when submitting torrents under a username or performing edits you would PGP sign the submittal. For anonymous additions there would be no need but they cannot edit or remove their torrents.
Also I think for removing torrents by staff (TPB does this in a few exceptional cases right? like child porn or whatever) there can be PGP keys in the staff DB. When a request is signed with these it is performed on whatever torrent in the same way the owner could. They could also elevate user statuses to VIP and Trusted and whatnot.
An initial submit would be the same as a "propagation" submit, the nodes would not know they are the first to receive it. Propagation submits would happen in the first 12 hours a torrent is submitted (could be adjusted later.. probably takes a lot less) which nodes would know from the timestamp.
It has to propagated so that it is dispersed among most of the network so it doesn't get "lost".
I think the interface would be best implemented as a separate application like I2P or Tor rather than a browser bundle (Why not both?
). You would navigate to 127.0.0.1:666/tpb for example and be greeted with your LOCAL copy. Then maybe for searches if your local torrent db does not have the torrent you can always get it to start messaging nodes with the search to see if there is torrents it doesn't have. To reduce internet usage maybe they could send a list of just magnets and it will request back the magnets it doesn't have.Well I hope this is helpful for someone
,AwfulProgrammer