12 ms·
> Especially after SyncThing disappeared from Play Store (because it was basically a non-Android app behind a thin Android shell that couldn't easily be upgrad
by dns_snek 1y ago
> Especially after SyncThing disappeared from Play Store (because it was basically a non-Android app behind a thin Android shell that couldn't easily be upgraded to more modern native APIs), there's nothing super-obvious here.
That's not what happened, it was Google who started rejecting their updates on Play store. I believe the original Android app maintainer quit after that but there's a fork on on F-droid which works perfectly.
- graemep 1y agofork that will work perfectly until year after next.
- Zambyte 1y agoWhy?
- cyphar 1y agoPresumably they're referring to Google's plans to roll out developer signing requirements for all apps[1], which will affect F-Droid-installed apps. [1]: https://news.ycombinator.com/item?id=45017028 https://news.ycombinator.com/item?id=45017028
- Sanzig 1y agoAssuming that the developer of Syncthing-Fork doesn't mind providing ID to Google, they shouldn't have an issue getting a signing key (we will see how this works in practice). They aren't doing anything objectionable to Google. The bigger issue for third party apps will be things like Newpipe, where applying for a key will put the developers in danger of a lawsuit because it affects Google's business. (The APK signing requirement is a fiasco, I'm not defending Google. Just pointing out that this app will probably not be as seriously impacted as others).
- sunaookami 1y agoFWIW, adb install will continue to work: https://www.notebookcheck.net/Android-s-app-sideloading-block-has-a-potential-workaround.1107566.0.html https://www.notebookcheck.net/Android-s-app-sideloading-bloc...
- npoc 1y agoNot if you run the GrapheneOS variant of Android.