Arghblarg

No comment other than the phrase in title is prominent on the hats intentionally shown behind the young man being interviewed here. I'll let everyone reading this decide for themselves whether this is a problem or not.

EDIT: For the record, perhaps my original commentary on this post was attempting to be too 'clever'. I was most definitely * not * trying to promote these chuckleheads. It was posted in order to ensure people know the enemy -- there are some scary forces working in Canada to instill the horrors we are seeing down south, right here, right now.

As most have predicted and feared, the US Administration appears to now be testing if they can push one step further towards enforcing an authoritarian ethno-state: threatening a full-on US citizen by-birth with detainment and deportation (to where, exactly, if they are a born US citizen?). Someone who, "coincidentally", is an immigration lawyer, someone who might defend other targets of their deportation agenda.

First they came for ...

EDIT: a thread indicating this has been a mass email to others https://bsky.app/profile/reichlinmelnick.bsky.social/post/3lmljpkrdj22h

In response to suggestions by a lunatic in the US Oval Office, Green Party Canada's leader Elizabeth May suggested Canada should invite western states Washington, Oregon and California join B.C and split from Canada to form the 'Cascadia' eco-state.

(Note this article is from Jan 8, 2025 and Elizabeth May has since become co-leader of the party alongside Jonathan Pedneault).

EDIT see my comment below which uses a much cleaner method that avoids the noisy multple udev events and doesn't require udev/eudev at all

This activates/de-activates the secondary display underneath the removeable keyboard properly. Note though that the keyboard is a composite unit and causes a whole train of udev events, rather than a single one, which means the desktop will flicker multiple times on each re-attachment of the keyboard :(. If anyone knows how to just run the scripts on the 'last' udev event, it would make for a cleaner experience. (XFCE sometimes crashes out on me due to the rapid xrandr reconfigs but it's mostly usable).

[/usr/local/bin/usb-0b05_1b2c-in]

#!/bin/bash

if [ "$(xrandr --listmonitors | wc -l)" -gt "2" ]; then

#logger -p user.info "=== KEYBOARD REPLACED ==="

xrandr --output eDP-2 --off

fi

[/usr/local/bin/usb-0b05_1b2c-in_udev]

#!/bin/bash

export PATH=/bin:/sbin:/usr/bin:/usr/sbin

/usr/local/bin/usb-0b05_1b2c-in &

[/usr/local/bin/usb-0b05_1b2c-out]

#!/bin/bash

if [ "$(xrandr --listmonitors | wc -l)" -lt "3" ]; then

#logger -p user.info "=== KEYBOARD REMOVED ==="

xrandr --auto && xrandr --output eDP-2 --below eDP-1

fi

[/usr/local/bin/usb-0b05_1b2c-out_udev]

#!/bin/bash

export PATH=/bin:/sbin:/usr/bin:/usr/sbin

/usr/local/bin/usb-0b05_1b2c-out &

[/etc/udev/rules.d/99-zbduo2024-kbd.rules]

ACTION=="add", ATTRS{idVendor}=="0b05", ATTRS{idProduct}=="1b2c", ENV{XAUTHORITY}="/home/username/.Xauthority", ENV{DISPLAY}=":0", OWNER="username", RUN+="/usr/local/bin/usb-0b05_1b2c-in_udev"

ACTION=="remove", ENV{ID_MODEL}="ASUS_Zenbook_Duo_Keyboard", RUN+="/usr/local/bin/usb-0b05_1b2c-out_udev"

Now, to get your laptop keyboard working when removed, in bluetooth mode, one must

1. Ensure bluetooth-ctl is running and initiate 'pair' in Bluetooth by clicking 'Create pairing with this device' (key icon in the 'Blueman-Manager' window)
2. Turn on bluetooth (switch on the left of the keyboard)
3. Remove the keyboard
4. Hold F10 for 4-5 seconds until its blue LED starts blinking rapidly (kbd in pairing mode)
5. Watch your desktop notifications for the connection message with the BT challenge pin code (6 digits)
6. type the challenge PIN code on the keyboard
7. Now the keyboard should be paired.

... now if only I could get the sound device (Intel HD Audio) and brightness control working for both screens!

If you haven't heard of it, this island has a population that the world has collectively decided to leave alone, mostly because they have proven, on multiple occasions, that they absolutely do not want visitors. Like, arrow-to-death anyone attempting to land or even visit near their shores.

This probably cannot go on forever... but maybe, it could. Essentially, we are already implementing a 'Prime Directive' of sorts here. Would the 23rd, 24th, ... centuries in Star Trek canon still have this little island on Earth, isolated from not just from Earth's own unified Federation society, but from the greater Federation races? What steps would the Federation and Earth take to maintain their isolation and the ecosystem on which they depend?

Would make for an interesting episode, or at least a cool side-note reference in one :)