Keychron would be my choice because they have open source QMK/ZMK firmware, a decent web-based configuration tool (Keychron Launcher) that is built around an open protocol (VIA) with their own open extensions. The build quality is good and they are customizable (hot swappable switches, standard layout so keycaps are available). They have a bunch of models so you can find some cheaper options and some more expensive premium options. I am quite fond of the Q series which have a solid aluminum body but these are the expensive ones, the K series tend to still be great keyboards but with a more affordable plastic or plastic/aluminum hybrid design.
As the OpenRGB creator, if you care about RGB, especially if you want to sync with other devices, stay away from the no-name boards with closed source firmware. Might have good build quality, but their firmware situation is awful and you likely won't be able to control it from anything other than the official app, RGB sync is out the door on many of them as they don't have an RGB streaming mode.
I thought the X was in reference to the roman numeral for 10. Mac OS X == Mac OS 10. They sat on version 10 for a long time and then moved on so it's no longer X.
The DRAM that came in it was SK Hynix 5600, but having mixed sticks has not been a problem for me. I've used it quite a bit on all 3 operating systems with no memory concerns.
The SSD was just whatever was available on eBay for a decent price, any NVMe will work. If you get a normal size 2280 drive you need to relocate the standoff because the included drive is a small 2230 drive (same size as the Steam Deck uses). Moving the standoff is pretty easy so you can accommodate either size NVMe SSD.
There is winget, which is built into newer Windows. You can install a decent amount of stuff using it. I have a setup script for setting up my OpenRGB development environment that uses winget to pull down MSVC build tools and libraries, 7-zip, and more.
I use git all the time at work from CLI. Windows Terminal is something I would highly recommend if you're going to heavily use CLI on Windows. Set up profiles for CMD, PowerShell, and if you have it, git bash. I don't use WSL (don't use Linux at work and use actual Linux at home) but git bash provides Windows equivalents of commonly used Linux/Unix commands.
Steam Machine is awesome, got my 512GB + Controller last week. Upgraded SSD to 2TB and added an extra 16GB stick of RAM. Triple booted SteamOS/Arch/Windows. Great little gaming box that also doubles as a travel PC.
Anubis seems to do a good job, most of the GitLab instances I've seen outside of gitlab.com use it and I've never had any problems with it even on lower end/mobile devices. Hopefully it cuts down on the bot issues, I love using old.lemmy.today.
Keychron is my current preference. Open source firmware (QMK/ZMK), excellent build quality, highly customizable, and their stock QMK/ZMK firmware works with their web-based Keychron Launcher in any Chromium-based browser or you can use any other app that supports the VIA protocol. Keychron also has their own per-key RGB extension to the VIA protocol and I've recently added support for it in OpenRGB, so my Keychron keyboards sync with all my other lights. The only problem is their firmware has a limitation on the lighting configuration where each key has to be the same brightness in per-key RGB mode. I've opened a PR on their GitHub to fix it and flashed custom builds to my Keychron Q2 (QMK) and Keychron Q6 Ultra 8K (ZMK).
Mission Center is my favorite task manager app on Linux. It does copy the Windows design somewhat, but Windows' task manager is one of the better designed things in Windows.
When I originally joined Lemmy I joined .ml because it seemed like the default instance. It's hosted by the devs! It seemed like a good choice. But as this platform has grown and especially during the lead up to the 2024 election the awful side of that instance really started to show and I decided to leave. I'm glad I did. It sucks that the dev-hosted instance is such a cesspit as that is where I would expect new users to end up.
Thanks to both of you for keeping mlmym alive. It's the best way to use Lemmy and I moved to lemmy.today primarily because they have it as an available interface.
Update! It looks like it won't be too difficult to implement on Windows either! I did some poking around with RWEverything and the LED controller memory space is right there ready to be poked starting at address 0x0DE8 (IO port space). I manually poked the enable, LED color, and mode registers and could change the LEDs accordingly. This is easily achievable with a PawnIO module that mimics the sysfs entries from the Linux driver and I already have one partially written. I tested that PawnIO was able to enable/disable the LEDs and it could, but more complex interactions will require defining some ioctls and writing an OpenRGB implementation that mirrors the Linux one. Currently setting up my Windows build environment on the Steam Machine.
At least using AI but proofreading and fixing AI's mistakes uses your human brain to some degree. If they must use AI I'd rather they be smart enough to comprehend what it puts out and do at least some critical thinking of their own.
Only as useless as you want it to be, you could, for instance, use it with the hardware sync plugin to display CPU or GPU usage. I should mark it as manually configurable for segments so you can divide it up and use it for both CPU and GPU actually.
Mainly for development purposes. I plan to use the Steam Machine as my new travel PC and for my work on OpenRGB I want both Linux and Windows for testing. I use Windows to reverse engineer the official software and protocols for devices so I can reimplement them in a cross platform way to work across all OSes. Also maybe for Fortnite, the only game I still need Windows for, though my friend group hasn't been playing lately, I know how to fix the bootloader, spent time getting a customized rEFInd config going.
While I'm generally pretty anti-AI especially in OpenRGB itself, I did try slop coding a Decky plugin with free AIs for selecting OpenRGB profiles and colors just as an experiment. It didn't go well though and I'm not familiar enough wih Decky or the languages it uses to really do it justice. I'd love to see such a thing from someone who knows what they're doing.
The OpenRGB Effects Plugin has some audio visualizer effects including a port of my old Keyboard Visualizer. You can also use the Python SDK to integrate OpenRGB lighting into third party software.
It does not, but Steam isn't constantly writing to the LEDs. The Customization tab in game mode just lets you pick from the built in hardware effects so it's not continuously writing. That means it generally is not fighting OpenRGB. The only time it does seem to write to the LEDs repeatedly is during downloads when it uses the LEDs as a progress bar. Also, in desktop mode (on SteamOS or on other distros) it does not seem that Steam touches LEDs at all.
Keychron would be my choice because they have open source QMK/ZMK firmware, a decent web-based configuration tool (Keychron Launcher) that is built around an open protocol (VIA) with their own open extensions. The build quality is good and they are customizable (hot swappable switches, standard layout so keycaps are available). They have a bunch of models so you can find some cheaper options and some more expensive premium options. I am quite fond of the Q series which have a solid aluminum body but these are the expensive ones, the K series tend to still be great keyboards but with a more affordable plastic or plastic/aluminum hybrid design.
As the OpenRGB creator, if you care about RGB, especially if you want to sync with other devices, stay away from the no-name boards with closed source firmware. Might have good build quality, but their firmware situation is awful and you likely won't be able to control it from anything other than the official app, RGB sync is out the door on many of them as they don't have an RGB streaming mode.
I thought the X was in reference to the roman numeral for 10. Mac OS X == Mac OS 10. They sat on version 10 for a long time and then moved on so it's no longer X.
Crucial 16GB 1x16GB DDR5 5600 CL46 SODIMM Laptop Memory PC5-44800
SanDisk Optimus 5100 2TB M.2 2280 NVMe PCIe 4.0 x4
The DRAM that came in it was SK Hynix 5600, but having mixed sticks has not been a problem for me. I've used it quite a bit on all 3 operating systems with no memory concerns.
The SSD was just whatever was available on eBay for a decent price, any NVMe will work. If you get a normal size 2280 drive you need to relocate the standoff because the included drive is a small 2230 drive (same size as the Steam Deck uses). Moving the standoff is pretty easy so you can accommodate either size NVMe SSD.
There is winget, which is built into newer Windows. You can install a decent amount of stuff using it. I have a setup script for setting up my OpenRGB development environment that uses winget to pull down MSVC build tools and libraries, 7-zip, and more.
I use git all the time at work from CLI. Windows Terminal is something I would highly recommend if you're going to heavily use CLI on Windows. Set up profiles for CMD, PowerShell, and if you have it, git bash. I don't use WSL (don't use Linux at work and use actual Linux at home) but git bash provides Windows equivalents of commonly used Linux/Unix commands.
Steam Machine is awesome, got my 512GB + Controller last week. Upgraded SSD to 2TB and added an extra 16GB stick of RAM. Triple booted SteamOS/Arch/Windows. Great little gaming box that also doubles as a travel PC.
Anubis seems to do a good job, most of the GitLab instances I've seen outside of gitlab.com use it and I've never had any problems with it even on lower end/mobile devices. Hopefully it cuts down on the bot issues, I love using old.lemmy.today.
I'm pretty sure all of the HE boards use QMK. If you can use per-key RGB in Keychron Launcher you can use it in OpenRGB.
Keychron support made it into OpenRGB 1.0rc3, so just grab the 1.0rc3 version from https://openrgb.org/. To patch your firmware to fix the color issue, see this PR: https://github.com/Keychron/qmk_firmware/pull/492.
Keychron is my current preference. Open source firmware (QMK/ZMK), excellent build quality, highly customizable, and their stock QMK/ZMK firmware works with their web-based Keychron Launcher in any Chromium-based browser or you can use any other app that supports the VIA protocol. Keychron also has their own per-key RGB extension to the VIA protocol and I've recently added support for it in OpenRGB, so my Keychron keyboards sync with all my other lights. The only problem is their firmware has a limitation on the lighting configuration where each key has to be the same brightness in per-key RGB mode. I've opened a PR on their GitHub to fix it and flashed custom builds to my Keychron Q2 (QMK) and Keychron Q6 Ultra 8K (ZMK).
Mission Center is my favorite task manager app on Linux. It does copy the Windows design somewhat, but Windows' task manager is one of the better designed things in Windows.
When I originally joined Lemmy I joined .ml because it seemed like the default instance. It's hosted by the devs! It seemed like a good choice. But as this platform has grown and especially during the lead up to the 2024 election the awful side of that instance really started to show and I decided to leave. I'm glad I did. It sucks that the dev-hosted instance is such a cesspit as that is where I would expect new users to end up.
Thanks to both of you for keeping mlmym alive. It's the best way to use Lemmy and I moved to lemmy.today primarily because they have it as an available interface.
Update! It looks like it won't be too difficult to implement on Windows either! I did some poking around with RWEverything and the LED controller memory space is right there ready to be poked starting at address 0x0DE8 (IO port space). I manually poked the enable, LED color, and mode registers and could change the LEDs accordingly. This is easily achievable with a PawnIO module that mimics the sysfs entries from the Linux driver and I already have one partially written. I tested that PawnIO was able to enable/disable the LEDs and it could, but more complex interactions will require defining some ioctls and writing an OpenRGB implementation that mirrors the Linux one. Currently setting up my Windows build environment on the Steam Machine.
At least using AI but proofreading and fixing AI's mistakes uses your human brain to some degree. If they must use AI I'd rather they be smart enough to comprehend what it puts out and do at least some critical thinking of their own.
Only as useless as you want it to be, you could, for instance, use it with the hardware sync plugin to display CPU or GPU usage. I should mark it as manually configurable for segments so you can divide it up and use it for both CPU and GPU actually.
Mainly for development purposes. I plan to use the Steam Machine as my new travel PC and for my work on OpenRGB I want both Linux and Windows for testing. I use Windows to reverse engineer the official software and protocols for devices so I can reimplement them in a cross platform way to work across all OSes. Also maybe for Fortnite, the only game I still need Windows for, though my friend group hasn't been playing lately, I know how to fix the bootloader, spent time getting a customized rEFInd config going.
While I'm generally pretty anti-AI especially in OpenRGB itself, I did try slop coding a Decky plugin with free AIs for selecting OpenRGB profiles and colors just as an experiment. It didn't go well though and I'm not familiar enough wih Decky or the languages it uses to really do it justice. I'd love to see such a thing from someone who knows what they're doing.
The OpenRGB Effects Plugin has some audio visualizer effects including a port of my old Keyboard Visualizer. You can also use the Python SDK to integrate OpenRGB lighting into third party software.
It does not, but Steam isn't constantly writing to the LEDs. The Customization tab in game mode just lets you pick from the built in hardware effects so it's not continuously writing. That means it generally is not fighting OpenRGB. The only time it does seem to write to the LEDs repeatedly is during downloads when it uses the LEDs as a progress bar. Also, in desktop mode (on SteamOS or on other distros) it does not seem that Steam touches LEDs at all.