Beware the fork in the road

This is meant as a cautionary note regarding open source software forks. And by this I mean hard forks, namely that one project goes a different way than a previous version. Both are a bit different, but happened within six months of each other to important (to me) open source projects:

Syncthing-Fork fork

This is more of a rename/redirection of the repository to syncthing-android, the original name before syncthing-fork.

The background is somewhat murky, as follows:

  • Why syncthing-fork no longer available on github? - a long thread with a lot of info.
    • Fork in this sense is more of a redirection (to a differently-named repository, and new accounts to control them)
    • The keys were given, which prevents people from have to choose to install a new app, or not, as what they previously approved now points to other people and code.
    • Obtainium path for updates is vulnerable because bad things can be done to the code that is then auto-installed.
    • The new account running things is only days old, with no history to rely on regarding code quality and behavior.

TLDR;

In my estimation, not just with the glitches in handover, but the lack of attention and care to viable feedback and locking issues --> abandon syncthing-fork/syncthing-android. It can't be trusted, and it doesn't allow for much if any collaboration. There are three other options for running syncthing on Android.

Other syncthing on android options

  • syncthingtray - see esp. how to run the Android app, this has an experimental Android app, and also works well on Linux for managing syncthing. I don't need it as the basic start and web admins are sufficient for my use case.
  • BasicSync - by far the best replacement option, and the one I now use.
  • Syncthing on Termux on Android - but cannot access sdcards, so not usable for my use-case.

KeePassXC --> ChiPass

This fork is a hard fork based on a severe case of algorithm aversion with an overly healthy ego, and clearly too much time on their hands.

More to come on this...

We use cookies only for WordPress functionality, and do not use third-party analytics or tracking.
Accept