Torrent creator on Linux?

seeder@lemmy.dbzer0.com to Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ@lemmy.dbzer0.com – 33 points –

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.

31

Torrent-file, also supports BitTorrent v2 — coming with piece alignment by default.

It seems that piece-alignment is not yet supported when creating a v1

Create a hybrid then, it will add BEP-47 to v1 separately (since hybrids can't exist without it) and you will have additional v2 support, with built-in piece alignment, double win.

Some clients currently do not support downloading hybrid and v2, and v2 has a flaw that can be modified remotely?

so, v2 and hybrid which containing v2 seem to be not a good choice.

I didn't see your comment earlier, pretty much all of them support hybrids, old transmissions till 3.01 are exclusions, and that's because their devs didn't implement their bencoding library according to BEP, but this flaw was fixed in the new versions awhile.

So you're loose to choose hybrids (or hell, even v2 only), protocol was around for a couple of years, don't believe what others' say, those are the pretty much lazy people with low technical background, who are afraid to upgrade their clients for years. Didn't catch that "remote" thing, but there could be no way of modifying data bound to sha256 hash.

BitTorrent v2 — is the future. I suppose there's no need telling its improvements.

Ahh.. This feature should be made known to more people, such as creators, uploaders.

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

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 ".<sha1>.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/

Here's the link.

If you don't understand, then just think of it as the solution of 99% stuck torrents and need to download part of other files' pieces to check if given file is valid.

These files are the cause of torrents that are stuck at 99%

Quote from your link: "If used incorrectly or maliciously symlinks and padding files can result in internally inconsistent torrents which cannot finish downloading because they contain conflicting hash information."

Exactly, that's why clients with BEP-47 support should:

Ensure that adding and deduplicating such a torrent does not lead to loss of already existing data.

I doubt that there are decent torrent clients implemented BEP-47 without this sanitization, if any.