Leaderboard

Warning: Beta versions are not the finished product, and are unstable. We also took some features out temporarily, which we're adding back in gradually. Please purchase only if you like trying out bleeding edge software that contains bugs. Do not use this in a production environment.

It looks like @kelvintechie beat me in answering @sinon6rn's question. Thanks so much for sharing the steps @kelvintechie. Keep rockin'!

This is the new config UI for Synergy 2, which is much simpler (we removed the need to use IPs and server/client modes). This is the legacy config UI for Synergy 1. It's only in the v2 branch because we haven't deleted it yet. The Synergy 1 UI is incompatible with the Synergy 2 UI, so that's why it's not working. We have a Fedora RPM build for Synergy 2... how come you're not using it? By the way, Synergy 2 is party closed source, so you won't be able to build the new UI from source.

Hey, for beta4 (due in 2-3 weeks) we'll be adding an error state for cloud config (but that could be pushed back to beta5). However, beta4 will definitely include daemon services for all platforms. SSL will come a little later (beta5 or beta6), and the hidden/advanced setting menu will follow sometime after that.

Hi @Erik.Z. I am happy to confirm that this feature is bound to be supported in v2.1.