this post was submitted on 21 Oct 2026
48 points (96.2% liked)

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

70897 readers
40 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

We heartily recommend visiting the free port of freemediaheckyeah (aka FMHY) while you sail the high seas, for all the freshest links the ocean has to offer.

📜 c/Piracy Wiki (Community Edition):

🏴‍☠️ Other communities

FUCK ADOBE!

Torrenting/P2P:

Gaming:

💰 Please help cover server costs.

Ko-Fi Liberapay
Ko-fi Liberapay

founded 3 years ago
MODERATORS
db0@lemmy.dbzer0.com
Flatworm7591@lemmy.dbzer0.com
RandomLegend@lemmy.dbzer0.com
Andromxda@lemmy.dbzer0.com
CosmicTurtle0@lemmy.dbzer0.com
tenchiken@lemmy.dbzer0.com
unruffled@anarchist.nexus
48
Iroh has started an IPFS alternative project (www.iroh.computer)
submitted 5 days ago* (last edited 5 days ago) by jajalayer@lemmy.dbzer0.com to c/piracy@lemmy.dbzer0.com
13 comments fedilink hide all child comments
 

The new iroh-blobs design restores the initial "one unique identifier for each file" ethos of IPFS (abandonned by IPFS), to reduce swarm fragmentation. It takes the standard Blake3 hashing algorithm to generate file CIDs (equivalent to Bittorrent magnet infohash).

The protocol uses the Mainline Bittorrent DHT (not a custom DHT). There is no notion of block CIDs (no potential deduplication, but also less scalability issues for announcing each block CID on the DHT).

So that's a lot of design simplifications that will improve implementation time.

If you are interested, have a try at Iroh-share, a CLI and TUI Rust implementation.

you are viewing a single comment's thread
view the rest of the comments
[–] zzffyfajzkzhnsweqm@sh.itjust.works 1 points 5 days ago (2 children)

I really like two of their points:

  • anonymous by design
  • distributed as a library

I really hate because such projects as IPFS required me to install some extention and a niche component that is hard to understand. While it is easy for me to do it I have abandoned all hope that project like this would gain some broader popularity.

For example qbittorrent is already hard to use for most people and it does not require to install extention and background service. You just install an app.

[–] percent@infosec.pub 2 points 1 day ago (1 children)

FWIW, you can access IPFS content with an in-browser IPFS gateway now, so no need to install anything: https://inbrowser.link/

You'll still need to install something if you want to add/pin content, etc., but the in-browser gateway is convenient for sharing links to IPFS stuff with someone who doesn't know what IPFS is.

[–] zzffyfajzkzhnsweqm@sh.itjust.works 1 points 1 day ago (1 children)

Yes. But relying whole infrastructure on some central gateways goes in the opposite direction of the project goals.

[–] percent@infosec.pub 1 points 1 day ago

Yeah I think that's one of the reasons why they made the in-browser gateway. (Also the old http gateway servers mostly sucked)

[–] jajalayer@lemmy.dbzer0.com 2 points 4 days ago* (last edited 4 days ago) (1 children)

For Iroh-blobs, Dropwire would be the easy-to use all-in-one app (not appropriate for mass sharing just yet). Then there is the iroh-http library, allowing to use Iroh-blobs on a web browser (without installing anything; a website similar to instant.io / webtorrent.io).
Also note that most of the big Bittorrent peers have a pretty sophisticated setup anyway (allways-on machine with raid array; bittorrent daemons; remote client; VPN; download automation indexers; media library etc).

[–] zzffyfajzkzhnsweqm@sh.itjust.works 1 points 4 days ago

Awesome. Thank you :)