Our great sponsors
sway | barrier | |
---|---|---|
613 | 616 | |
13,672 | 25,896 | |
2.3% | 1.8% | |
9.2 | 0.0 | |
3 days ago | 11 months ago | |
C | C | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
sway
-
"We understand" ;)
This is partially why i use tools like i3 (/ sway). i like the tool; it works extremely well for me; the design has stayed the same for 20 years; there's no profit motive to come along and fuck everything up. it just works. it is boring in the best way possible.
-
Firefox on the Brink?
I also have crashes on sway, but there’s a rough workaround now which prevents the issue totally.
I believe there’s a design issue with Firefox and GTK handling input events; some Wayland compositors have workarounds but others do not.
https://github.com/swaywm/sway/issues/7645
https://bugzilla.mozilla.org/show_bug.cgi?id=1743144
Firefox is my preferred browser and I hope we can keep its engine alive in this era of Chrome dominance.
- Framework 13 with AMD Ryzen 7040 Series Makes for a Great Linux Laptop
-
On Desktop GUI Minimalism
Sway is fast, minimal, and flexible. Their recommended tools/addons are worth a look: https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway
From that list I use greetd + tuigreet as my login manager, sway-launcher-desktop for FZF-powered app launching, and wob for lightweight brightness and volume display (send '50' to the wob socket and it'll show 50%; it doesn't get simpler).
-
The technical merits of Wayland are mostly irrelevant
Sensitive features like screenshots, input methods, screen locking and whatnot are behind extensions (or portals). I'm not familiar with the state of GNOME/KDE/Flatpak, but at least on the wlroots side of things it is true that currently these extensions are enabled and accessible by any process that can talk to the Wayland socket (breaking those security benefits, as you say). This is changing with protocols such as security-context that allow a sandbox engine like Flatpak (or your custom scripts) to restrict what features apps can use. (so your browser can't register an input method, or some random app can't lock the screen)
https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m...
-
Rethinking Window Management in Gnome
sway does all those things very well: https://swaywm.org/
-
Using nwg-wrapper for a HUD of help for sway modes
I've added it to https://github.com/swaywm/sway/wiki/Useful-add-ons-for-sway
- What is a good windows tiling manager for beginners?
-
Wayland Is Pretty Good
https://github.com/swaywm/sway/issues/4763
sad to see another linux api design failure
- A linux newbie has installed and configured Arch. Minimalist graphical capabilities?
barrier
-
Show HN: Multi-monitor KVM using just a USB switch
For software KVM you can use https://github.com/debauchee/barrier
I use it between a Windows PC & a Macbookpro (Linux version available but I don't have Linux)
- Barrier: Open-Source KVM Software
-
Hrvach/Deskhop: Fast Desktop Switching Device
Barrier is a Cross-Plattform, open source Synergy fork that works quite well without any additional HW too [0]
Prior to Synergy going to closed source, it was forked into Barrier[0], which then was forked into input-leap[1]. Both open source.
Synergy is open core, these portions are licensed as GPL: https://github.com/symless/synergy-core/#License-1-ov-file
There is an open source fork that branches off version 1.9: https://github.com/debauchee/barrier#what-is-it
-
Wayland vs. X – Overview
libei looks useful. But IDK why libei is necessary to run Barrier with Wayland?
For client systems, couldn't there just be a virtual /dev/inputXYZ that Barrier forwards events through
And for host systems, it looks like xev only logs input events when the window is focused.
Is xeyes still broken on Wayland, and how to fix it so that it would work with Barrier?
With Barrier, when the mouse cursor reaches a screen boundary, the keyboard and mouse input are then passed to a different X session on another box until the cursor again crosses a screen boundary rule.
Barrier is a fork of Synergy's open core: https://github.com/debauchee/barrier
libei:
-
Alternative solution to expensive KVM - Auto Monitor Input Switcher
Barrier appears to handle PC switching only for the keyboard and mouse.
- Linux VNC viewer not displaying MacOS with multiple desktops (single monitor)
What are some alternatives?
Hyprland - Hyprland is a highly customizable dynamic tiling Wayland compositor that doesn't sacrifice on its looks.
i3 - A tiling window manager for X11
wayfire - A modular and extensible wayland compositor
river - [mirror] A dynamic tiling Wayland compositor
synergy-core - Open source core of Synergy, the cross-platform keyboard and mouse sharing tool (Windows, macOS, Linux)
awesome-wayland - A curated list of Wayland code and resources.
input-leap - Open-source KVM software
bspwm - A tiling window manager based on binary space partitioning
qtile - :cookie: A full-featured, hackable tiling window manager written and configured in Python (X11 + Wayland)
wslg - Enabling the Windows Subsystem for Linux to include support for Wayland and X server related scenarios
Waybar - Highly customizable Wayland bar for Sway and Wlroots based compositors. :v: :tada:
hidusbf - USB Mice Overclocking Software (for Windows)