←back to thread

410 points morsch | 5 comments | | HN request time: 0.437s | source
Show context
thombles ◴[] No.43983191[source]
This is also why the official SyncThing Android app stopped being distributed. There is a fork but it's not available on the Play Store.
replies(2): >>43983226 #>>43983745 #
1. fsh ◴[] No.43983745[source]
The fork is in the play store and works fine for me on Android 15: https://play.google.com/store/apps/details?id=com.github.cat...

I was a bit surprised that the official client suddenly disappeared though.

replies(3): >>43983958 #>>43985792 #>>43991945 #
2. deng ◴[] No.43983958[source]
From a very cursory look it seems like syncthing-fork uses ContentResolver and other stuff from SAF, so it seems they made it work.

The official maintainer of syncthing-fork indeed stopped publishing to Google Play, but it seems some other guy is doing that now for him.

3. JeremyNT ◴[] No.43985792[source]
> I was a bit surprised that the official client suddenly disappeared though.

Here is when syncthing dropped the official Android client [0] so you can read through their rationale and the HN response at the time.

I am not an Android developer but I do follow this space; I had the impression at the time that it really was mostly about the dev cycles that would have been required and nobody willing to do the work.

I do wonder why they don't just make the fork an official Syncthing project, it seems like the obvious solution would be to officially bless it. I can only guess the maintainer likes their independence.

[0] https://news.ycombinator.com/item?id=41895718

replies(1): >>43986694 #
4. kortilla ◴[] No.43986694[source]
Well they also probably don’t want the reputation hit if the fork ends up doing some kind of rug pull.
5. BitPirate ◴[] No.43991945[source]
The play store version isn't updated anymore. You should switch to F-Droid.