Hal-5700X@lemmy.world to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 years agoCourt: Cloudflare is Liable for Pirate Site, But Not as a DNS Providertorrentfreak.comexternal-linkmessage-square32fedilinkarrow-up1121arrow-down13
arrow-up1118arrow-down1external-linkCourt: Cloudflare is Liable for Pirate Site, But Not as a DNS Providertorrentfreak.comHal-5700X@lemmy.world to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.comEnglish · 2 years agomessage-square32fedilink
minus-squareSethayy@sh.itjust.workslinkfedilinkEnglisharrow-up2·2 years agoI’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?
minus-squareSchizoDenji@lemm.eelinkfedilinkEnglisharrow-up4·2 years agoThe problem isn’t about logins but tracking the network traffic.
minus-squareSethayy@sh.itjust.workslinkfedilinkEnglisharrow-up1·2 years agoYeah you’d need to dynamically track login/IP association, but that wouldn’t be particularly hard either
minus-squareSchizoDenji@lemm.eelinkfedilinkEnglisharrow-up2·2 years agoYeah but private trackers need to adopt this
minus-squareWarmApplePieShrek@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up1·2 years agoMost public trackers do this. Schizo’s information is far outdated.
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.