You do not need any permissions to create HaikuPorts recipe poll request. Synergy fork is under GPL 2 license, see LICENSE file.
Is it possible to use Haiku version of Synergy with Barrier? Free version of Synergy is not available for Windows so Barrier should be used. I tried to adjust protocol signature to Barrier some time ago, but it doesnât help.
You could use an old version of synergy from before it went closed source. Haiku synergy is based on my original port of usynergy to the haiku input device API. usynergy was chosen because it was an independent client implementation of the protocol with cleaner source than the original. I donât know how clean the barrier source code is, but it might be easier to port barrier than to update the haiku usynergy port. There are no licensing problems, it only works now as it does because different people decided to help out, so please do whatever you want!
@kallisti5 seems to worked on that recently https://gitlab.com/kallisti5/barrier-haiku
I managed to run Haiku synergy (https://github.com/kallisti5/synergy-haiku, B_OK check in clipboard handling was changed to != NULL to fix build) with https://github.com/brahma-dev/synergy-stable-builds/releases (v1.8.8-stable). server_keymap need to changed to "AT". When attempting to copy text on Haiku, server reports error: ERROR: invalid message from client "haiku": DCLP. Copying text from windows is not working.
@kallisti5 did you manage to run it?
Synergy seems pretty dead. It hasnât been updated forever, so that proves the âpaidâ open source model sucks 
I recently took ~my~ the synergy-haiku codebase iâve been managing, and refactored it for Barrier under a new name (Barrier is new, again open-source version with some protocol changes). barrier-haiku is working ~80% for me. Just disable tls.
Barrier (and Synergy) has some issues with wayland desktops on Linux though⌠ymmv
1 Like
Aaahhh. Synergy blocked me from their github project after I mentioned that it looked pretty dead. (and deleted my github comment mentioning as much).
Iâm going to delete my synergy haiku repo in favor of the Barrier one. Go ahead and fork my Synergy repo if desired.
4 Likes
Hey,
Iâm a developer on the Synergy project. Iâm sorry to hear this. This breaks my heart a little. I donât think itâs right that saying something like that should get you blocked. Iâve been away from the project for a while and Iâm returning to see the community in a different place than where I left it, which is sad.
Iâm trying to rebuild some bridges, so let me know if youâre open to it, or if the damage is way past done.
Thanks,
Nick
5 Likes
I was probably too hard on Synergy (and Symless) in the past⌠I understand that you and Symless took over the very unmaintained original (really old⌠like IRIX old) open source Synergy with good intentions (There was a previous person who tried to maintain Synergy as an open source project before you that failed⌠I donât remember their name).
I do feel like priorities shifted too far towards making it a paid commercial product for end users with no real open source community engagement. Synergyâs biggest asset was always connecting the âweird systemsâ together. (FreeBSD to windows, Linux to Linux, Haiku to Linux, Haiku to Windows) I mean, the original IRIX port shows the core use case. (IRIX Workstations for 3D CAD to Windows workstations)
Synergy as an idea is simple, but historically it seemed to keep ending up getting âused a lot by engineers and developers, who donât contribute back enough to maintain itâ which stagnated development.
In the early 2010âs, I knew a bunch of random engineers at enterprise software companies using Synergy to connect their weird systems together. (This seemed like a great missed opportunity to capture funds for âenterprise licensesâ) Itâs why Docker Desktopâs license agreement says "if youâre working for a company with more than XXX employees, or making more that XXX dollars in profit, you must purchase an enterprise license⌠otherwise Docker Desktop is free to use.
Walking the line of paid open source is difficult, I donât think the difficulty you have had is unique to Synergy. I see these difficulties happen a lot. I can say that âbulldozing through open source communities to make something paidâ never works⌠it kills projects.
I think a common feeling that has developed is when youâre going after licenses for personal use cases, youâre pushing away potential users who may also want to use the product in their places of work (and have corporate funds available for enterprise licensing).
Keep personal licenses cheap, keep work/enterprise licenses reasonable to capture income.
5 Likes