blinry
blinryCan't say that I'm not enjoying the reviews that the niche perfume community is writing! :D
blinryThat blog post seems to have kicked off a new special interest for me! :D
I'm bringing some perfume samples, to #why2025 hit me up if you wanna try some; I'd be happy to recommend you something!
Also, if there's anyone into perfumes (or perfume-making?), I'd love to chat!
blinryThis feels like a blog post from a parallel universe, discussing a topic I never knew existed: Artsy, experimental perfumes!
Perfumes that smell like new cars. Like a distant Tuscan town in winter. Abstract scents. Like ink & old books. Or like Room 237 from "The Shining". :'D
https://gwern.net/blog/2025/perfume
blinryCan't say that I'm not enjoying the reviews that the niche perfume community is writing! :D
blinryThis feels like a blog post from a parallel universe, discussing a topic I never knew existed: Artsy, experimental perfumes!
Perfumes that smell like new cars. Like a distant Tuscan town in winter. Abstract scents. Like ink & old books. Or like Room 237 from "The Shining". :'D
https://gwern.net/blog/2025/perfume
blinryThis was a fun afternoon! Thanks for following along.
Let me know which other programs I should try with multiple mice! :D
blinryLooks like SDL (the multimedia library) very recently merged support for multi-seat input! https://www.phoronix.com/news/SDL-Merges-Wayland-Multi-Seat
So… many-mouse games should be possible on Wayland? :3
blinryYou could try this script (requires zenity & possibly more tools? Please read before running!) https://github.com/n3rdopolis/rebeccablackos/blob/master/rebeccablackos_files/usr/bin/configureseats
(Doesn't work on #NixOS, where /etc/udev is read-only. 💀
)
I'd love to have a little command line helper tool to help set this up, for an arbitrary number of mice! :D
blinryThis was a fun afternoon! Thanks for following along.
Let me know which other programs I should try with multiple mice! :D
blinry1. Use sudo libinput list-devices to find the device file (like "/dev/input/event12")
2. Use udevadm info -a /dev/input/event12 to find the parent device with a catchy ATTRS{name}.
3. Create a file /run/udev/rules.d/00-multiseat.rules like this:
ATTRS{name}=="Name of your mouse" ENV{WL_SEAT}="second"
(Note: This is a single line)
4. Run sudo udevadm trigger to apply the new rules.
You can check again with sudo libinput list-devices. The device's "Seat" should now say "seat0, second"!
blinryYou could try this script (requires zenity & possibly more tools? Please read before running!) https://github.com/n3rdopolis/rebeccablackos/blob/master/rebeccablackos_files/usr/bin/configureseats
(Doesn't work on #NixOS, where /etc/udev is read-only. 💀)
I'd love to have a little command line helper tool to help set this up, for an arbitrary number of mice! :D
blinryOkay, here's how to set this up!
You need to create a udev rule for the "second" input device that sets ENV{WL_SEAT} to a string other than "default", and then start Weston from a virtual console. (At least, starting it from another Wayland session didn't work for me.) That's it!
The WL_SEAT property is what Wayland refers to as a "logical seat". Assign the same seat name to a mouse and a keyboard to make them work together! The default seat is "default".
Detailed steps:
blinry1. Use sudo libinput list-devices to find the device file (like "/dev/input/event12")
2. Use udevadm info -a /dev/input/event12 to find the parent device with a catchy ATTRS{name}.
3. Create a file /run/udev/rules.d/00-multiseat.rules like this:
ATTRS{name}=="Name of your mouse" ENV{WL_SEAT}="second"
(Note: This is a single line)
4. Run sudo udevadm trigger to apply the new rules.
You can check again with sudo libinput list-devices. The device's "Seat" should now say "seat0, second"!
blinryVery useful when your very long line of code doesn't fit on your screen, for example! :P
(Shout-out to @xssfox@cloudisland.nz, who first did this on X.org! https://sprocketfox.io/xssfox/2021/12/02/xrandr/)
blinryOkay, here's how to set this up!
You need to create a udev rule for the "second" input device that sets ENV{WL_SEAT} to a string other than "default", and then start Weston from a virtual console. (At least, starting it from another Wayland session didn't work for me.) That's it!
The WL_SEAT property is what Wayland refers to as a "logical seat". Assign the same seat name to a mouse and a keyboard to make them work together! The default seat is "default".
Detailed steps:
blinrySide note: I think more window managers should support this feature!
blinryVery useful when your very long line of code doesn't fit on your screen, for example! :P
(Shout-out to @xssfox@cloudisland.nz, who first did this on X.org! https://sprocketfox.io/xssfox/2021/12/02/xrandr/)
blinryTried it again, and the independent clipboards still seem a bit glitchy after all… :(
An issue asking for proper support in GTK was closed five years ago, for example… https://gitlab.gnome.org/GNOME/gtk/-/issues/1574
blinrySide note: I think more window managers should support this feature!