Support for Terabox, Teldrive, Alldebrid and other remotes ready

Feature
1

Hello everyone,

I’ve been working on rclone-extra, a fork of rclone that adds support for several new backends: Terabox, Teldrive, Alldebrid, and Alist. You can find the fork here:

These backends were originally sourced from various community projects (mainly Bclone and official Teldrive forks) , but I’ve updated and improved them to align better with rclone’s architecture. Specifically, I have:

  • Integrated fs.ListPer support.

  • Added fs.Pacer for rate-limiting.

  • Implemented fs.Shutdowner for proper cleanup.

Before I proceed, I’d like to ask:

  • Is it possible (and acceptable) to submit a pull request to the official rclone repository with these additions?

  • Would it be preferable to submit them individually or as a single PR?

Thank you for your time and any advice you can provide!

2 Likes
2

Great work :slight_smile:

I'd probably prefer the backends one at a time in seperate PRs.

Just make sure that you've read the backend testing guide rclone/CONTRIBUTING.md at master · rclone/rclone · GitHub and post the results of the test_all test so I can see how you are doing.

Also we should try to retain the original contributors, maybe their commits or if that isn't possible with at least a Co-Authored-By attribution.

If the first one goes well maybe you'd consider joining the rclone team to help us maintain the backends?

1 Like
3

Like so many others, I’ve been looking for Terabox support for a loooooong time. Terabox is notoriously absent from almost everything I know, and since rclone is the Swiss Army Knife of all possible file transfer mechanisms out there, well, I’m actually positively surprised that, in the same day, I found not one, but two Terabox backends to play with!

Well, not quite. I’m actually talking about pull request #8508, submitted by x1arch some time ago. Your code is practically identical, although, after 130 comments on his PR, @x1arch seems to have developed it further.

Neither of you makes any attribution to the other, thus I was wondering which one I should test first! :laughing:

4

... oh, and neither has been incorporated in the upcoming new release... yet! But I'd say that @x1arch has a slight edge on you: he has, after all, already submitted his own PR, and has engaged with several users to fix several aspects of his code. Right now, it's only waiting for a maintainer to give the last thumbs up :+1: as his code passes all tests with flying colours...