Just install @Catfriend1 fork from F-Droid:
1 Like
I heavily use LDAP integration and untrusted device encryption. I hope both of these features continue in any and all future versions.
Hi all, as the maintainer of official Syncthing for macOS wrapper I was wondering if there will be a roadmap towards 2.0, when will v1 for example be phased out and bugfixes not backported. In some communication I did read there are no big breaking changes (yet) the major one is on-disk database switch to Sqlite. But I did read there will be some API changes as well in the future, this can and will break the Syncthing for macOS integration. I will try to catch up with the changelogs so I can maintain also two versions. As long as syncthing v2 will be RC the macOS version will not auto upgrade from v1 to v2 via sparkle. Thanks all for the hard work and make this happening.
2 Likes
For your purposes, you probably just need to worry about command line flags: syncthing/relnotes/v2.0.md at main · syncthing/syncthing · GitHub
2.0 is “imminent” after which further 1.x releases will be “as required”…
3 Likes
Do we have any performance comparisons between v1 and v2 ? Will it be faster ? Need more or less cpu / ram / io / disk space ?
Almost certainly yes, or no, depending 
2 Likes
Wishlist: generally more user-friendly messages when the syncing is stopped or not starting. This may require passing messages forth and back between servers. It would cut down tremendously on the message traffic in this forum, too (“why does it not work?”)
(Reach goal: a way to see what’s on the other computer and/or ssh tunnel access to do it by hand. useful when one computer is behind a firewall.)
I would say it’s about the same but the database is triple the size with some of the db 2Gb - 3Gb. Not sure if that size will impact the overall speed, but if the dbs are on HDD, it’s going to be painful
Note, I am an extreme user with lots of devices and folders
2 Likes
Maybe, maybe not? I mean, that was pretty painful in v1 as well, and one reason for the larger database is there are more indexes resulting in (hopefully) more targeted reads instead of scans…
3 Likes
Honestly, I was incredibly surprised to see that Syncthing does not have gRPC nor OpenAPI/Swagger spec when I was writing a Ktor-powered Syncthing API client. The resulting code is incredibly messy to say the least. Glad to see gRPC coming!
It is, without any doubt.
They’ve proven themselves incredibly useful in translating from Java plus tight coupling to Android Framework to Kotlin and somewhat more platform-agnostic APIs. Maybe, your rewrite will also bring cross-platform support to iOS and iPadOS. Some things such as API client can easily be done in multiplatform way.
Looking good, thanks @calmh for pointing at this