118
Court: Cloudflare is Liable for Pirate Site, But Not as a DNS Provider
(torrentfreak.com)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Nov 2023
118 points (97.6% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
55056 readers
318 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 2 years ago
MODERATORS
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.
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.
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.
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
I've thought about this and wouldn't it be way more private (and realistically secure given changing IPS) to just use a cryptographical key each login? Like everywhere else on the web?
The problem isn't about logins but tracking the network traffic.
Yeah you'd need to dynamically track login/IP association, but that wouldn't be particularly hard either
Yeah but private trackers need to adopt this
Most public trackers do this. Schizo's information is far outdated.