this post was submitted on 20 Oct 2024
776 points (99.4% liked)

Selfhosted

40296 readers
181 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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!

you are viewing a single comment's thread
view the rest of the comments
[–] Atemu@lemmy.ml 4 points 1 month ago (1 children)

What's the history behind this? Why could the changes be done upstream, necessitating a fork?

[–] sugar_in_your_tea@sh.itjust.works 3 points 1 month ago (1 children)

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.

[–] Atemu@lemmy.ml 1 points 1 month ago

I know that part.

The other fork has existed for a long while.