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.
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.
Alternative if you can live with just the WebUI: SyncThing in Termux
TYSM for the link! I’ll probably switch to this.
Can i use my old exported synthing app config to this?
Given that they set up a new repo from scratch, this is a missed chance to just migrate to codeberg
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.
nel0x commented on that syncthing thread.
that’s what nel0x has said.
Ah, ok
Well, 🤬!
I use it without isuue
Maybe it is, but as with any question about something containing malware or being compromised or not is not about an individual using it without problems ;).
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.
