Announcement by the creator: https://forum.syncthing.net/t/discontinuing-syncthing-android/23002
Unfortunately I don’t have good news on the state of the android app: I am retiring it. The last release on Github and F-Droid will happen with the December 2024 Syncthing version.
Reason is a combination of Google making Play publishing something between hard and impossible and no active maintenance. The app saw no significant development for a long time and without Play releases I do no longer see enough benefit and/or have enough motivation to keep up the ongoing maintenance an app requires even without doing much, if any, changes.
Thanks a lot to everyone who ever contributed to this app!
Oh don’t worry to much, mine too: If there wasn’t an alternative for syncthing on android, I might have kept it on lifesupport :)
What is this alternative of which you speak?
Syncthing-fork. Both show if you search for Syncthing in fdroid. Since imsodin seems to be OP Dev maintainer for Syncthing, i think he is referring to the fork.
Ooh.
Thanks.
I’ve been running the fork for a long time but somehow figured it was a soft-fork and maybe not really viable without upstream development from syncthing.
Now @[email protected] 's comments are making a lot more sense.
This whole thing is more or less a non-issue then?
not quite
But that is the original Syncthing app @fine_sandy_bottom was talking about the fork that is available in F-Droid
Only one I can think of is Resilio, but it’s hard on RAM and battery for large folders.
It’s been forever since I looked at resilio so this may be an unfair appraisal but… I seem to remember it’s one of those OSS projects that feels a lot more like free tier commercial software. Do you think that’s the case or nah?
Honestly just a dumb rsync client would be enough for me.
And I don‘t know what‘s going on with them. There weren’t any updates for years, now there is a design overhaul, no new features and suddenly they want me to register. Duck
What’s the history behind this? Why could the changes be done upstream, necessitating a fork?
Sounds like the original maintainer is tired of maintaining it, and the amount of community support wasn’t enough to justify continuing to put in the effort. And then Google’s packaging process pushed it over the edge, hence retiring the project.
The fork is just another person deciding to take up maintenance of the project.
I know that part.
The other fork has existed for a long while.