pouwelse__ basically we wanna reduce metadata leak. so its harder for 3rd parties to scan dhts/trackers to figure out what people are sharing. its seems a lot of lawyer trolling is happening this way.
clkao_ joined the channel
brycebaril has quit
clkao has quit
Cr8- has quit
calvinmetcalf joined the channel
pouwelse__: so the simple idea is instead of announcing the hash of the content you are sharing you would share the hash of the hash
jlord joined the channel
pouwelse__: and then when two clients find each other, before starting to exchange file data they'll send a challenge to each other that reveals if the remote peer also hash original the hash
pouwelse__: something simple like they'll take the content hash and hmac with the remote peer id (all peers have a random id) and send that to the other peer
substack: came up with a new bittorrent conspiracy theory today
substack: when you announce you share the hash of the torrent, which you can create if you have the same files independently of the person who created the torrent
substack: so its somewhat incriminating
substack: e.g. if you have the same pirated content and we make the same torrent independently it would be the same hash
substack: and trackers/dht have 'scrape' functions for listing all the peers who are seeding a hash
substack: i think the scrape thing in trackers is so trackers can copy swarm metadata so if a tracker goes down the chance another one has the same swarm metadata is higher
substack: i think they kept the hash strategy super simple on purpose to make the network itself harder to take down
substack: cause there are some really basic things they can do to avoid each peer sharing the hash directly