this post was submitted on 21 Oct 2024
361 points (100.0% liked)

Open Source

30833 readers
374 users here now

All about open source! Feel free to ask questions, and share news, and interesting stuff!

Useful Links

Rules

Related Communities

Community icon from opensource.org, but we are not affiliated with them.

founded 5 years ago
MODERATORS
 

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.

Sad to see it go. There is a fork but seems not so great considering they are looking for active maintainer. Still better than nothing. Need to check it out as it has some enhancements.

Planning to close my Google Play Developer Account. Please say hi if you are interested in obtaining the latest gplay release files from me to help in publishing this app

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 13 points 1 day ago (2 children)

I was not even aware of this fork let alone a long timeline of existence. I am adding this onto my weekend project list. Thanks for the recommendation.

[–] [email protected] 10 points 1 day ago

I switched to the fork as soon as I read this news. It shouldn't take more than a few minutes:

  • Just install it in parallel with the mainline app,
  • export your existing configuration to the default storage location,
  • import it in syncthing-fork (it'll detect the export file automatically),
  • and you're done. Uninstall the official app so they don't compete for the daemon and port.
[–] [email protected] 2 points 1 day ago (2 children)

Sadly it's unusable on Android 15. All of the interactable functions are crammed up into the status bar and cannot be touched.

[–] [email protected] 1 points 1 day ago

Wdym cannot be touched?

[–] [email protected] 1 points 1 day ago (1 children)

Yeah I Have the same problem and wondered why no one switching to the fork mentions that :D But I guess android 15 is not very widespread jet.

[–] [email protected] 1 points 1 day ago (1 children)

Sounds like a bug and the dev hasn't caught up to the new version?

[–] [email protected] 1 points 1 day ago

Yes, there seems to be an open issue for this bug, but actually the developers response doesn't inflict confidence in the fork 😅 He seems to have updated the app to target Android 15 without testing in it in the emulator.