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!

  • sugar_in_your_tea@sh.itjust.worksEnglish
    1·
    28 days ago

    That’s the second way it could go. But given their track record of being FOSS when everyone else was proprietary and keeping the source code available, I’m willing to give them the benefit of the doubt and see what they do. For now, “we’ll re-evaluate it again once it’s stable” tells me it’s still on the table.

    • ammonium@lemmy.worldEnglish
      1·
      28 days ago

      Stable bindings doesn’t mean open source, so I don’t see how that tells you it’s still on the table

      • sugar_in_your_tea@sh.itjust.worksEnglish
        1·
        28 days ago

        They’re moving a lot of code to this internal core, which means this core is unstable. It’s pretty common for projects to hold off on making code public until it’s reached a certain level of stability. I’m guessing they’re not interested in accepting patches, due to the high level of churn from the dev team. Once that churn dies down, there’s a chance they’ll reconsider and make it FOSS.

        I’ve seen this in a number of FOSS projects, and it’s also what I do on my own (I don’t want help until I’m happy with the base functionality).

        So that’s why I hold out hope. We’ll see once the churn on that internal SDK repo dies down.

        • ammonium@lemmy.worldEnglish
          2·
          28 days ago

          Why go through all the hoops if they are instead just could refuse patches? Open source doesn’t mean open to contributions, look at SQLite for example.

          If they had the idea to release this open source they would have said so in clear words by now. They didn’t so I don’t have much hope, unless maybe if they get enough negative publicity to change their mind.

          Why does VC need to ruin everything…