Discontinuing syncthing-android
forum.syncthing.net
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 ...

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!

  • imsodin@infosec.pubEnglish
    1·
    1 month ago

    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 :)

      • iturnedintoanewt@lemm.eeEnglish
        4·
        1 month ago

        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.

        • fine_sandy_bottom@lemmy.federate.ccEnglish
          1·
          1 month ago

          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 @imsodin@infosec.pub 's comments are making a lot more sense.

          This whole thing is more or less a non-issue then?

    • Atemu@lemmy.mlEnglish
      0·
      1 month ago

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

      • sugar_in_your_tea@sh.itjust.worksEnglish
        2·
        1 month ago

        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.