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

Selfhosted

39964 readers
342 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
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
HybridSarcasm@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
784
Syncthing Android app discontinued (forum.syncthing.net)
submitted 2 weeks ago by chaospatterns@lemmy.world to c/selfhosted@lemmy.world
208 comments fedilink hide all child comments
 

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
[–] sugar_in_your_tea@sh.itjust.works 1 points 2 weeks ago (1 children)

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.world 2 points 2 weeks 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...