[GH-ISSUE #62] README should mention whether there are any attempt to maintain protocol interoperability with synergy 1.x #50

Closed
opened 2026-05-05 04:52:10 -06:00 by gitea-mirror · 1 comment
Owner

Originally created by @p12tic on GitHub (Jun 20, 2018).
Original GitHub issue: https://github.com/debauchee/barrier/issues/62

Thanks for the fork!

Are there any attempts to maintain protocol interoperability between synergy 1.x and barrier? I think the answer to this question should be mentioned in the README.

Originally created by @p12tic on GitHub (Jun 20, 2018). Original GitHub issue: https://github.com/debauchee/barrier/issues/62 Thanks for the fork! Are there any attempts to maintain protocol interoperability between synergy 1.x and barrier? I think the answer to this question should be mentioned in the README.
Author
Owner

@walker0643 commented on GitHub (Jun 30, 2018):

The short answer is "no". At the time Barrier was forked Synergy 1.x was legacy-ified and had more or less become abandonware. There was no reason to reason to invest in compatibility with a product that was dropped by its creators. Now that Symless has decided to return to 1.x as their stable branch I'm not sure how things will play out. I do like your suggestion that we cover this "officially" in the readme file, but let's wait to see what Symless does first.

Feel free to drop by the irc channel ( #barrier on freenode ) for things like this, @p12tic. We're nice people :D

<!-- gh-comment-id:401553685 --> @walker0643 commented on GitHub (Jun 30, 2018): The short answer is "no". At the time Barrier was forked Synergy 1.x was legacy-ified and had more or less become abandonware. There was no reason to reason to invest in compatibility with a product that was dropped by its creators. Now that Symless has decided to return to 1.x as their stable branch I'm not sure how things will play out. I do like your suggestion that we cover this "officially" in the readme file, but let's wait to see what Symless does first. Feel free to drop by the irc channel ( #barrier on freenode ) for things like this, @p12tic. We're nice people :D
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#50
No description provided.