Pros:

• The clickety clack is creamy as hell
• The dial/knob is very useful already
• I really like the LED effects when I'm typing.
• The packaging was superb and it just generally looks amazing

Cons:

• Shipping (unrelated to keyboard):
  • it took 3 weeks to get here
• Keys / Spacebar
  • It's quite a high profile position and I find myself double-hitting the spacebar often which appears to have a hare-trigger
  • The spacebar is needlessly long, and my thumb can't quite reach the Alt or Win key without contorting my hand.
  • On my laptop, the spacebar begins at C and ends at M. Here it starts at X and ends at ,
• Customization
  • Modifying it in Linux is proving to be painful.
    • The qmk cli requires a full reflash, but no easy way to set macros
    • VIA has easy macros, but has no cli just a shitty Electron app that requires you to set your keyboard permissions to World Accessible for chrome to detect it (which is creepy).
• Gaming
  • I knew that some keyboards are better for typing and others for gaming, but I did not think the difference would be so big.
  • The arrow keys could be a lot more responsive
  • I've never noticed this issue with a normal keyboard.

I guess I love the look and feel of it, but it's incredibly frustrating to modify as a linux user and I'm making tons of mistakes with it whilst typing.

Is this all normal? Do I eventually get used to it? Or should I send it back and just use a normal $20 keyboard that I can just type and forget about.

I'm subscribed to a few communities which have posts that don't really reach my eyes, even in the "Subscribed" view, unless I manually click into the community to see what's happening.

Are there any plans or workarounds to make some communities more visible than others, just for a single user?

e.g. I want to see more what's happening in /c/Emacs than I do /c/AskLemmy, but AskLemmy posts always get more votes so the Emacs posts always seem to get buried.

I realize this might be a big ask. Cheers!

Duplicate days are allowed, but with just cause.

Edit: Y'all be strange.

I'm looking for a reliable way to log when my laptop is:

• powered down
• boots up
• goes to sleep
• wakes up

Currently I'm checking both the systemd-suspend and tlp systemctl services, but these don't really feel very robust, and I don't have TLP installed on all my machines.

Is there an easier way to do this, or a better systemctl unit that logs all the power states of my machine. Preferably laptop agnostic?

Laptop snippet so far:

journalctl --since -9days -u systemd-suspend -u tlp \
    | grep -P "Finish|Start|Stopped" | sed '/.*Finished TLP.*/d;
            s|Starting TLP.*|╭╴System Boot  |;
 s|Starting System Suspend.*|┤ · Sleep      |;
 s|Finished System Suspend.*|├ · Wake       |;
             s|Stopped TLP.*|╰╴Power Off    |;' \
    | sed -r 's|^(.*:[0-9]+)+:[0-9]+.*:(.*)|   \1 \2 |'

My work has given me a remote windows desktop to use, that I access using AWS.

Through this windows desktop (accessed via a chrome web-browser), I can SSH into a compute node to do work.

I dont actually need this virtual desktop, I'd rather just SSH from my local machine directly to the compute node, using the remote desktop's network without having to spawn the desktop itself.

Ive been reading up about SSM agents[0] as a solution, but am unsure if I have the priveledges to do this myself.

https://docs.aws.amazon.com/systems-manager/latest/userguide/session-manager-getting-started-enable-ssh-connections.html#ssh-connections-enable

Is this something I can easily do using the AWS credentials that I have?

https://www.viruscomix.com/page537.html