Does anyone know why syncthing-fork is no longer available on Github?

Hi all,

I digged a bit into what actually happened to the commit history. So for those who want to verify themselves what changed, here is some info.

TLDR: The commit of F-Droid’s 2.0.11.2 release is still in the new repo history.

I checked the lastet F-Droid (com.github.catfriend1.syncthingfork) builds before the downtime event, which should be 2.0.11 from Nov 10 and 2.0.11.2 from Nov 11 (correct me if I am wrong; I myself had 2.0.11.2 installed when I noticed the repo was gone and then this thread started Nov 13).

  • 2.0.11.1 (Nov 10 F-Droid release)
    • F-Droid’s build log* mentions revision b25c350849f3b7e7311eb9527e2f2a6b0a4ac37a
    • This revision can both be found in the new repo and in nel0x’s fork.
  • 2.0.11.2 (Nov 11 F-Droid release)
    • F-Droid’s build log mentions revision 34e85735c10d030ae0dd14526fe9db5523f8da91
    • This revision can be found in the new repo, but not in nel0x’s fork (because the fork basically stops there, with the last common commit being bd7802b5637758704aca58db586190b09bb5c9f5, followed by 2 commits regarding project migration)
  • 2.0.11.3 (Nov 22 F-Droid release)
    • F-Droid’s build log* mentions revision cf4714bc9d07d49b7956ad24cb2458aa6e188baa

*See link for 2.0.11.2 and change the last digit; it does not allow me to post more links.

New Github repo: researchxxl/syncthing-android
nel0x’s fork on Github: nel0x/syncthing-android

Therefore, if one wants to trust F-Droid releases up to 2.0.11.2, I would recommend reviewing changes since then for releases after this, and make sure that the versions you install correspond to the reviewed ones (e.g. by checking F-Droid’s build log, as above).

For example, comparing F-Droid releases 2.0.11.2 and 2.0.11.3: https://github.com/researchxxl/syncthing-android/compare/34e85735c10d030ae0dd14526fe9db5523f8da9…cf4714bc9d07d49b7956ad24cb2458aa6e188baa
As you can see, these changes only include:

  • Documentation
  • Repository setup including Github workflows, including changing the repository URL
  • The gradle build file, updating how to retrieve signing keys
  • Translations/Strings
  • Library updates

If anyone has any other trustworthy sources about what the latest commit SHAs for the releases before the incident were, please share!

Hope this helps.

8 Likes