Asking because of the latest issues with the maintainer.
Personally, it seems like it’s trustworthy again. The previous owner of the repo did eventually admit that they authorized the transfer, but, The entire transfer process was extremely sketchy and had no chain of custody or trust. It was just the repository got deleted, and then a few days later showed under a whole blank state again with a user with no profile, no contribution history, and it was just a trust me bro, I knew the original maintainer look I have the keys to prove it.
The maintainer of the Google Play build of it seems to trust them though, and they are established in the community, plus they archived their sync thing builds again in favor of just using one repo, so it’s likely fine.
For future people wondering about it as well, it doesn’t help that the new maintainer of the app has deleted every issue that had to do with the migration, so you no longer can research the issue for yourself. The only information you have available to you is the discussion chain listed on the community forums, But any type of issue that they link to were deleted.
Personally though, I plan on keeping my current version pinned to prior to the transfer until either I’m forced to update due to bugs or I feel comfortable with the current maintainer again. I’m not sure how long that will be.
For an app that contains very sensitive information, I was not impressed with how the transfer process underwent.
Verbose please? What happened?
E: thank you all. Especially lambdaRX’ hint to a summary (comment 234 by GrabbenD) helped me.
Years ago, official development of an android app of syncthing was abandoned by the official developers. Most android users migrated to an already existing fork by a github maintainer catfriend1.
Catfriend1 unceremoniously disappeared, with their github repositories being taken over by a new user researchxxl. This was entirely unannounced and wasn’t really discovered until people with automatic updates enabled on Unobtanium noticed it.
researchxxl is not a known community member, and is being very reclusive when interacting with the syncthing community. Their github account was made specifically for the repository transfer, and their method of handling existing credentials is suspicious; looking no different than a hostile take over.
At this point in time, they are collaborating with Nexon, a user who worked with catfriend to publish syncthing fork builds to Google Play. They are more well known and trusted. If you can trust Nexon, and trust that end users in general are putting more scrutiny on the github source code after this whole situation, you can probably trust the recent releases for now.
Sorry for any details I may have gotten wrong. AFAIK, no one has taken the time to document all the things that have gone down. I would have linked to such a document otherwise. A lot of the discussion on this is happening in separate discussion threads, one of them being researchxxl’s github issue page, which they are censoring/deleting discussions from with(till recently) no oversight.
*Edit: this is also a poor summary. There is a lot of additional context that I don’t feel comfortable trying to encompass. Like why the official syncthing developers stopped their official android app, or catfriend1’s forum account coming back for a short time to try to explain their side of the story. Frankly, for how many people are using syncthing, I don’t think this story is getting enough attention.
I don’t use syncthing (anymore) and didn’t know the story behind this, but one thing I know is, f-droid builds the apk from source and signs it with their keys, or if reproducible builds are available, it verifies the signed apk provided by the maintainer to match bit-for-bit with the source code, so at least even if one doesn’t trust the new maintainer, they should be able to trust f-droid that the apk matches the source, so e.g. no spyware or malware was added for example. Sure, someone still needs to review the source, of course.
Thats part of the problem though. Supposedly catfriend1 gave researchxxl their signing keys, and researchxxl used these on their new github account. No one was aware that catfriend1 was not maintaining the repo anymore until users saw unexpected/unannounced updates and looked into the matter. This sparked a short lived discussion on F-Droid forums about what should be done when maintainer transfers are handled poorly like this. F-Droid admins decided that it wasn’t that big of an issue, which is problematic… this supposedly happened between two people meeting each other online and discussing it with each other. But its possible that catfriend1 is being blackmailed or otherwise coerced into handing off this data. This type of credential attack could happen with a compromised machine, without the victim ever realizing it in time. The fact that F-Droid treats this so casually is upsetting. Signed developer certificates protect you from MITM attacks, it does not protect you from the sources themselves being compromised.
In addition to others’ replies there is also this thread, and the last post offers summary of the situation.
Excellent link, thanks
I understood the repo changed hands in a shady way, with bad communication. Might be fine or not. I would also like to know, I’m not a user but was going to be just when it happened, and I postponed it
Syncthing dropped the android version and someone forked it.
The handoff (if you can call it that) was extremely sketchy, including the “explanation” on the Syncthing forums. Made me switch to Nel0x’s fork of the app.
nel0x’s fork is now archived.
AFAIK nel0x and researchxxl work together on the reserchxxl repository now.
Do they? I don’t see any nel0x PRs. I moved away from it out of an abundance of caution.
Well, 🤬!
Maybe? But if you use termux you can install the official Linux package and avoid the fork drama.
Presumably that can’t handle things that the app adds like run conditions for wifi/mobile data though? I realise some may not care about that as much.
I migrated from the Syncthing Fork app to the official Syncthing package in Termux, and it was a breeze. Is there any reason for preferring the app, other than being afraid of CLI?
How does it handle the battery life? Is it run all the time or do you just start it to sync when you need it?
I just have it constantly running in the background at all times. Every time I restart my phone, I manually open Termux and run the command
syncthing. I haven’t noticed any difference in battery life compared to when I used Syncthing Fork. It may possibly be better or worse, but not noticeably so.Ok, thanks. It really sounds like a simple solution to the problem. I think even if it does drain battery for some reason (e.g. a repository with a huge number of files), this could be automated, like the on/off switch to run the app to sync and be done with it.
On iPhone, I use sushi train, and it does automated sync via Shortcuts (a built-in app for light automations), via timers or other events like charging. It works perfectly fine for my use case. It syncs my notes multiple times a night, plus during the day while on charge or when I join trusted WiFi networks. I expect the same can be achieved on an Android. So, really, the CLI version might do the job plenty good, I believe.
