lol nope, I named it as a string of random letters.

After downloading for a while, although B didn’t get anything from A, but some IPs from GE, FR, US, VN, and so on appeared in the peer list, and their client names are rather strange and usually not seen, e.g. the VN ip’s client name is “VN 3.xxx”, do you know what they are?

Not only is it still alive, but it even stands on the mountaintop looking down on BT

First exclude TGx, it sucks, don’t use it,

Instead of focusing on practicality, the folks on the admin team were heavy on the visuals, preferring to add a lot of fancy visual elements to the site, but not bothering with things that would actually improve the torrent download experience.

Add some public (BT) trackers to ur private torrent and share it to ur friends, you’ll get what you want.

Yup, they don’t have their own torrents, but when you uploading there, they have it ;-)

Found that The Pirate Bay supports uploading HYBRID torrents, not sure if DHT crawler is supported.

https://pirates-forum.org/Thread-Mysterious-pad-files-in-my-torrent-upload

https://thepiratebay.org/description.php?id=55917681

cool, a good beginning

yup, need uploaders and BT sites to take the initiative to do something

unexpected👏👏👏 Thank you, although I don’t know how to use it yet.

I am a uploader of a not famous website (although did not upload not too much), planned to upload hybrid or V2, but our webmaster wasn’t going to support it, searched for discussions on this matter on other similar sites and found that their ideas are basically the same, which gave me some ideas, so I posted this thread,

Judging by the number of the post likes, it seems that most of the downloaders in this forum who are passive recipients are not interested in this topic.

I sent u a PM :)

establish a hybrid & v2 torrent site first

Thanks I will try

thanks. I tried this method, but RARBG made modifications to the source file and the verification failed

thanks you all the same

Not same in 2 torrents, Putting one into the other and check it will only give me 0% of the results.

cuz before posting torrent, RARBG will make changes to the source files, such as filling in its site address in the video attributes, while the seed published by N1C is the source file of the publishing group, and was not modified.

rarbg.best

It is completely using the database of RARBG, and the release time is also based on the original time of RARBG.

No garbage content from other sites was added inside. Currently.

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

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’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/

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