jesec
commented
4 years ago Related issue: https://github.com/Flood-UI/flood/issues/332
Fantastic idea. I think it is important to make it easier for uploaders to create torrents.
Technically it would be relatively straightforward to implement. However I would prefer a pure JS implementation like create-torrent for easier deployment, better maintainability and cross platform support. Piece size algorithm won’t be technically challenging in my opinion.
The most challenging part would be handling of long torrent creation time and as a result potential API (HTTP) request timeout imposed by the browser or other middleware (eg. nginx or express). UX-wise, users probably want to see a progress bar or see the process happens in background instead of waiting with a spinning icon.
I also found it challenging to find a perfect place in the frontend for this feature. The best solution I can think of currently is to add a “Create” tab to “Add Torrents” panel. I am concerned about the potential confusion, though. Do you have some better ideas?
mirolm
Type: Feature Request
Summary
Flood currently lacks a way to create a torrent. I think it was requested before but it was never implemented.
Idea of implementation
Torrent can be created relatively easy using the console utility mktorrent. If flood implements the frontend and then call mktorrent to do the actual work it can happen. After that the resulting torrent needs to be handled to rtorrent for the initial seeding.
Example of creating a torrent with mktorrent can be seen below:
mktorrent -a http://nyaa.tracker.wf:7777/announce -a udp://open.stealth.si:80/announce -a udp://tracker.opentrackr.org:1337/announce -a udp://tracker.coppersurfer.tk:6969/announce -a udp://exodus.desync.com:6969/announce -l 22 -o Sora_yori_mo_Tooi_Basho.torrent -n Sora\ yori\ mo\ Tooi\ Basho /media/lv2/download/rtorrent/Sora\ yori\ mo\ Tooi\ Basho/ -s https://horriblesubs.info
The only thing that is little trickly is the piece size - torrent should have between 1500 and 2500 pieces.
2^18 = 262 144 = 256 KiB for filesizes between 256 MB - 512 MB 2^19 = 524 288 = 512 KiB for filesizes between 512 MB - 1 GB 2^20 = 1 048 576 = 1024 KiB for filesizes between 1 GB - 2 GB 2^21 = 2 097 152 = 2048 KiB for filesizes between 2 GB - 4 GB 2^22 = 4 194 304 = 4096 KiB for filesizes between 4 GB - 8 GB 2^23 = 8 388 608 = 8192 KiB for filesizes between 8 GB - 16 GB 2^24 = 16 777 216 = 16384 KiB for filesizes between 16 GB - 512 GB
If there is an algoritm to automatically calculate the best piece size it will be great.