this post was submitted on 18 Jun 2025
93 points (100.0% liked)

Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ

62255 readers
212 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):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:


💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 10 points 5 days ago (17 children)

Can someone considerably smarter than me, with time to spare, please just find a way to federate/decentralize DNS.

I can fathom that it is complicated, maybe even impossible in the current setup, but the internet we all grew to love dies a little bit more each time the mouth breathers try to restrict it on behalf of capitalism.

Maybe remembering ip addresses can fill the void of not having to remember phone numbers anymore?

[–] [email protected] 21 points 5 days ago (12 children)

I mean, as far as I know, DNS is decentralized. Anyone can host their own DNS server, or change which server their network/device uses. Google's is just very commonly used because 8.8.8.8 is easy to remember, but there are thousands of others run by entities big and small, and there's nothing stopping you from running your own (assuming you manage to get a hold of a static IPv4)

[–] quediuspayu 2 points 5 days ago* (last edited 5 days ago) (3 children)

Do I need a static ip if I plan to only use it locally from my home network?

[–] [email protected] 4 points 4 days ago

What I suggest/have done:

  1. Rent a cheap VPS in a non-five eyes country that comes with a static ipv4.

  2. SSH on random port with certificate auth only. No root, no password auth.

  3. setup WireGuard server with random port.

  4. firewall block all incoming except ssh and WireGuard port at first.

  5. set home server to connect via wireguard as sole client to VPS.

  6. individually add any ports you want to go to the home server from the internet as NAT forwarded ports. Basically WWW -> VPS -> Home.

  7. have a separate WireGuard VPN for outgoing from the home server.

  8. profit?

But it’s crazy complicated. At least it was for me. Not for the faint hearted imo.

load more comments (2 replies)
load more comments (10 replies)
load more comments (14 replies)