this post was submitted on 12 Jan 2024
1110 points (99.0% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54716 readers
268 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 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I'm not sure that this is how it works in practice, but ideally: Unless you are registered in their stance / are browsing directly in their website, your client shouldn't be making any direct requisitions to their instance, so there is nothing they can infer your IP from. (Everything you interact with is comes directly your instance - the only thing that interacts with other instances is the server) That said, it's possible for some links to direct to the original stance, in which case your client will have to make requests directly to the original instance hosting the content... looking around in this page a bit, it looks like the Community images (banner, icon etc.) are linking directly to the original instance, so I guess that's a little bit of a problem - but just that shouldn't be enough information for them to connect the dots between the IP address fetching the image and the account you're using to browse
Don't images also link back to the original instance?