118

Court: Cloudflare is Liable for Pirate Site, But Not as a DNS Provider (torrentfreak.com)

submitted 11 months ago by hal_5700X@lemmy.world to c/piracy@lemmy.dbzer0.com

32 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] JustMy2c@lemm.ee 4 points 11 months ago

Plz can explain. Dumb user of 1337x 😢😔

(which didn't work when traveling Europa...)

[-] SchizoDenji@lemm.ee 1 points 11 months ago

Tor is an implementation of i2p. Basically it's a new protocol that obfuscates everything end to end.

On public trackers you'd be fine since it's public and ip doesn't matter. But on private trackers, they usually need your ip to track your activity on the tracker, but with i2p it would be nigh impossible to do so.

[-] kylian0087@lemmy.world 5 points 11 months ago* (last edited 11 months ago)

Tor is not a implementation of I2P. They are 2 different technologies with different usecases.

Tor ussage nodes and hops to obfuscate trafics origin while I2P obfuscates the entire network layer. With I2P every nodes IP is know to every node. Wile this is not the case for tor. Thirth hop doesnt know the IP of the first hop.

Also tor is heavily used to access the clearnet while I2P is not designed with clearnet in mind.

[-] WarmApplePieShrek@lemmy.dbzer0.com 1 points 11 months ago

You still got it half wrong. I2P hops don't know each other. The big difference is I2P tries to make every user a relay while only Tor relays are relays. Hence Tor torrenting is not recommended because it overloads the limited relays, I2P torrenting is fine because you expand the pool of relays at the same time. I2P doesn't really have exit nodes, too, so it's a separate network from the internet.

[-] kylian0087@lemmy.world 1 points 11 months ago* (last edited 11 months ago)

I never said the hops are know on I2P. All the nodes are though because it is a P2P network. Perhaps some bad wording on my part. But yeah your are right