this post was submitted on 21 Jul 2023
31 points (97.0% liked)

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

54716 readers
230 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
Ko-fi Liberapay

founded 1 year ago
MODERATORS
31
Torrent creator on Linux? (lemmy.dbzer0.com)
submitted 1 year ago* (last edited 1 year ago) by [email protected] to c/[email protected]
 

Is there any Torrent Creator on Linux that supports BEP-47 protocol (optimize alignment) ? It’s okay with or without GUI.

Currently using mktorrent, but does not support this important feature. I didn’t find anything on google.

Any suggestions? thanks.

EDIT: for creating v1 torrent.

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 1 points 1 year ago (2 children)

I'm having trouble understanding what BEP-47 exactly is. Care to enlighten me?

[–] [email protected] 6 points 1 year ago* (last edited 1 year ago)

I’m having trouble understanding what BEP-47 exactly is. Care to enlighten me?

Using padding files to prevent torrents containing multiple files from getting stuck at 99%.

The original Bittorent spec has a really stupid design decision in that it is just a long stream of concatenated files split into fixed size pieces. This means you always have to download parts of adjacent files to get the file you actually want. This leads to all sorts of unnecessary complexity when partially downloading a torrent of what do this with this left-over data, eg qB saves hidden "..parts" per torrent, which you can easily lose.

To get around this, padding files where introduced that "fill" the gap from the end of one file to the start of the next piece boundary where the next file starts with 0x00 filled padding files with naming corresponding to length. It's a cross-client standard defined in BEP47. Padding files are also required by necessity for hybrid Bittorrent v1+v2 torrents. Any remotely decent torrent client won't transfer or save these padding files, so the size doesn't really matter. And even if your client doesn't, some of the padding names will likely overlap and only be saved once.

https://www.reddit.com/r/DataHoarder/comments/nqwckn/stackoverflow_bought_out_should_we_be_worried/