Not sure who to ask

[rccypher]

Trying to avoid stepping on toes here.

I ran across the project as I was setting up a new seedbox. It's great work but I discovered that the project was lacking several features that I wanted. As such I forked the project and began implementation of these features for my own use. I would like to contribute back, or if the current team isn't interested in ongoing work on this project I would like to publish the version that I've been working on for others to use.

Note, that the work I'm doing is all AI driven. I am not a software developer or coder. But from my testing the changes I'm making work (I won't say they are good quality, but they work).

Anyway, please let me know how I can contribute back. Or what path I should take.

Thanks

[SpaceAgeHero]

Hi,

thanks for your offer. I'm not a developer myself, so I won't complain about the vibe coding.
I'd like to know what you've got there.

A couple of thoughts

• a different name without a seedbox reference, as it might serve different use cases for people
  • lftp-webui?
  • MirrorBox? (with at least a nod to Seedbox)
• I'd like to run this "natively" in a Proxmox LXC without Docker (maybe even a Helper-Script?)
• move files (not just download / for hard links in a "complete" folder / without destroying active seeds)
• for a more general approach, an upload feature / even multiple ftp connections

[quadcom]

While I've had some chats with Ipsingh in the past, there hasn't been any response from them since, and it's been a few years now.

I've tried on a handful of occasions to bring some eyeballs to the project to see if someone could take it over or fork and build an updated version.

Up until recently, it's been pretty quiet around here. But just a few weeks ago, a handful of people jumped in doing exactly what you are considering.

The one build that I am following now is https://github.com/nitrobass24/seedsync.

They are refactoring and bringing things up to date, as well as creating a roadmap for features they would like to add.

They might be open to contributions or ideas, especially if you can build those out and contribute a working merge.

[rccypher]

A name change makes sense. I'll do that before I make the repo public.

So far I've added a file validation with chunking.
Support for mulitple directory support rather than just the single directory that it has now.
and Dark mode

I've also ensured that there are unit tests and an automated testing framework for everything to ensure that it is all working as expected during build.

For my use case the non-docker setup isn't really useful to me, but I don't see any reason it can't be built to operate without the container.

I like the idea of modernizing the code base and bringing it up to current standards for supportability. I'll look into that as part of the project.

[rccypher]

Here is the fork i'm working on. Lots to do still, but its a start.

https://github.com/rccypher/RapidCopy