jwodder / demagnetize Goto Github PK

ws=<URL> parameters in magnet links should be converted into url-list entries (BEP 19) in the resulting .torrent file.

See BEP 5 et alii.

Use DHT if (and only if?) there are no trackers in a magnet URL.

It should be possible to specify the set of starting nodes for DHT in the configuration file (#1).

See BEP 9.

If a peer reports that the metadata info size exceeds, say, 20 MiB, abandon the connection.

• Make this value configurable via the configuration file (#1).

See BEP 34.

How can I ensure that the event loop waits "on drop" for these to complete? Would I have to pass the tracker a task group in which to run the "stop" announcements?

Hi @jwodder. Thanks for the wonderful implementation. I had an implementation to find the torrent information from magnet. i have used your library to implement that. It's working perfectly however for my custom requirement. I just only want to get the torrent information rather than creating torrent files. So I made custom changes to be able to work.

Implementation usage: https://github.com/mhdzumair/MediaFusion/blob/develop/utils/torrent.py#L92-L150

I would like to request for creating functions to use this as library which can be used for other project rather than only focusing cli usage.

demagnetize should be configurable via a TOML configuration file containing the following settings:

• local port or port range to report to trackers
• whether to actually listen on (and reject incoming connections to) the local port
• the numwant value to send to trackers
• local bind address
• whether to use IPv4
• whether to use IPv6
• maximum number of magnet links to process at once in batch mode
• maximum number of trackers to connect to at once per magnet link
• maximum number of peers to connect to at once per magnet link
• tracker timeouts
• general peer interaction timeout?
• maximum size of incoming packets to accept from peers?

The CLI should also have a dump-config subcommand for outputting the current configuration with explanatory comments above each field (good for creating a new config file).

The Rust version uses a limit of 30 trackers per magnet at once.

I would like to have a function to get seeders count for the magnet to be implemented on this library. More information mhdzumair/MediaFusion#86

Thanks.

See BEP 41.

See BEP 54.

See https://wiki.vuze.com/w/Message_Stream_Encryption (or my write-up at https://jwodder.github.io/kbits/posts/bt-encrypt/).

The configuration file (#1) should include a setting for encryption preference: always use encryption, prefer encryption, prefer no encryption, forbid encryption(?).

See BEP 29.

See BEP 40.

See BEP 52.

• Fetch data from a limited number of peers at once

  • Use asyncio.wait(..., return_when=FIRST_COMPLETED) to run up to <limit> peer tasks at once, adding a new peer whenever a previous one errors
    • Use a similar strategy to replace/rewrite acollect()
    • Would this implementation strategy have the same issues as those motivating jwodder/demagnetize-rs#65?

• Spawn tasks for independently sending "stopped" announcements to trackers

  • How can I ensure that the event loop waits "on drop" for these to complete? Would I have to pass the tracker a task group in which to run the "stop" announcements?

Obviously, this will mean dropping support for trio.

See the integration tests in the Rust version.