The associated forum post URL fromhttps://forum.rclone.org

N/A

What is your current rclone version (output fromrclone version)?

v1.72.0

What problem are you are trying to solve?

I would like a backend somewhat similar to thearchive backend, but with support for torrents.

When searching for something along those lines I came across this previous pull request (#8240) and took a stab at reviving it and extending it a bit to suit my needs.

I have an initial implementation availablehere implemented as an out-of-tree backend.

I'm aware the current implementation isn't ready to be merged as is. I'm really just looking to see if there's interest in me working on getting this into shape for merging as well as any input on implementation if merging is desirable.

Particularly, if merging this backend is desirable, it seems like a good first step would be deciding if it makes sense to add to the archive backend or not. Conceptually, they seem quite similar so I'm inclined to do so if it makes sense, but I haven't gone down that path so far mainly because it didn't feel like adding the various config options that seemed necessary/useful for the torrent backend really made sense to add to the archive backend.

Regarding the current implementation, I'm aware it doesn't really follow the coding standards/best practices laid outhere and that's one of the first things I would work on if we decide to try to merge it. This is also my first real foray into writing go, so I'm sure there is probably a fair amount of room for improvement in general and things that aren't really done very idiomatically.

There are a fair number of things I'd like to improve with the current implementation, but it's currently in a state where it's working well enough that others can easily play around with it and getting feedback on whether this is something that makes sense to merge into rclone or not (and in what form) will probably significantly influence what I work on next with it.

How to use GitHub

• Please use the 👍reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.