Hello there 👋

Do you think you can add a hash field to the NormalizedTorrent type?

The problem I am having with Transmission is that restarting the service causes the torrent IDs to change.
The only unique data I have found is the hashString property.
It would be super cool to have it directly on the normalized data 🤌

Thanks !

All the Torrent Client packages have a public function addMagnet but this is not defined in the TorrentClient interface. Suggest that either:

1. It gets added to allow access from generically defined torrent client
2. The normalizedAddTorrent function checks if the URL is a magnet and calls it internally.

Suggested code for 2 is below:

if (url.startsWith("magnet:")) {
      const torrent = await client.addMagnet(url, {paused: !autoDownload});
      const hashString = torrent.arguments["torrent-added"].hashString;
      return this.client.getTorrent(hashString);
}

At first, thanks for your work.

I'm writing a transmission Web ui and looking for a client sdk. But got is for nodejs runtime, have you consider support this in Web runtime？

Hi,
I want to using @ctrl/transmission in a react project that based on typescript, but the browser always popup a transmission server login dialog, and this will displayed in a loop after each login. In final it will get 401 error.
But when I using in a javascript react project, it will login automation.

In typescript:

Thanks for your attention!

I think there is a mistake in this typing:

It should be:

files: Files[];

Hi,

Sorry to open an issue for this but I didn't find any info about adding torrent via Magnet. Is it possible ? If so, can you tell me how ?

Thanks a lot !

https://github.com/transmission/transmission/blob/master/extras/rpc-spec.txt#L404 defines:

   "filename"           | string      filename or URL of the .torrent file

It would be awesome if addTorrent method supported URL or another method was created for that.