mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1989] Is this project dead? #1457
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SiirRandall on GitHub (Nov 2, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1989
What happened?
I haven't seen any updates for two years. I love the hard work that went into this. I want to make sure this project isn't dead, and updates will be made if needed.
Version
v2.0.0-RC1
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
No response
What OSes are you seeing the problem on? (Check all that apply)
Linux, Windows, macOS
What OS versions are you using?
Fedora 40, macOS 14, WIndows 11 Pro
Relevant log output
No response
Any other information
No response
@m-graf commented on GitHub (Nov 3, 2023):
Open a PR, and contribute my friend. This project is not dead. :)
@stefnotch commented on GitHub (Nov 6, 2023):
This project has moved to https://github.com/input-leap/input-leap
However, as commented below
@m-graf commented on GitHub (Nov 7, 2023):
This is not entirely true. The two most active maintainers have forked this project, and have started the project in the link mentioned. I point the out because the discussion (https://github.com/input-leap/input-leap/issues/1414) was obviously heated, and was muted.
edit: just found the link to the open discussion: https://github.com/input-leap/input-leap/discussions/1427
neat :)
@stefnotch commented on GitHub (Nov 7, 2023):
Well yes, of course. The project has been forked, and the currently most promising looking fork is input-leap. And the owner of the barrier repository is at the moment not involved in input-leap.
Anyways, I chose to communicate it that way ("This project has moved to ..."), since I just wanted to give a simplified answer to anyone who's just looking for a solution.
The discussion thread is interesting. I'm glad to see that input-leap seems to be in good hands :)
@wccrawford commented on GitHub (Nov 20, 2023):
It's worth noting that while input-leap is more active, they have yet to release a build that they recommend using. They still recommend using Barrier 2.4.0 until they finally release something stable.
@sgon00 commented on GitHub (Jan 10, 2024):
Yeah, it's dead. Installation is broken (no openssl key created). No wayland support. Not usable at all.
@yllekz commented on GitHub (Jan 24, 2024):
This is the first time I'm hearing that the project has been forked. I think there should definitely be a much more forthcoming communication to users of this project...
@diegorodriguezv commented on GitHub (Feb 8, 2024):
There are a lot of PR's that are more than 3 years old. And almost a thousand open issues. I know that in the open source world instead of asking others to fix problems you should fix them yourself and contribute, but as a developer I don't want to waste my time creating a PR that won't get merged.
I would think twice before contributing here.
@myrandor commented on GitHub (Jul 10, 2024):
The last commit of this project is more than 2 years ago, and there's a lot of PR to be tested and approved.
Is @walker0643 or @p12tic still involve in this project? I'd love to contribute to help making it more stable and active! 😊
@stefnotch commented on GitHub (Jul 10, 2024):
@myrandor I would contact the developers of input leap https://github.com/input-leap/input-leap?tab=readme-ov-file#input-leap
@nbolton commented on GitHub (Jul 31, 2025):
Barrier postmortem: Why did Barrier fail?
@walker0643 commented on GitHub (Jul 31, 2025):
@myrandor It would be great to get the project caught up with the PRs. It's been quite a while since we've had an active developer, so there is definitely work to be done. Jump on the Discord server If you want to discuss: https://discord.gg/GbEud2RVV4 - Thanks!
@yllekz commented on GitHub (Jul 31, 2025):
If you want a 1:1 app replacement, I jumped to input-leap from this and things continued as normal. I think the two apps are even capable of talking to one another.
@nbolton commented on GitHub (Aug 1, 2025):
Please try Deskflow or Input Leap as Barrier is no longer in development.
https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap
The 'Insights' tab of each GitHub project may help you decide which one to use.
Both are compatible with Barrier client/server so you can try on one of your computers.
If this is still an issue in those projects, we would appreciate a cross-post of this issue.
@sithlord48 commented on GitHub (Aug 1, 2025):
@walker0643 Why not just work with us on Deskflow ? There is nothing here but tons of bugs and old code to update.. Most of that is now done in Deskflow. Instead of backporting and fixing here lets work together to make better software for everyone.