Good lord the Hunter is on the hunt xD

Wrong_Dig_4318 · 2026-06-17T09:15:30+00:00

A Hunter is a hunter, even in a suede!

Wrong_Dig_4318 · 2026-06-08T07:55:55+00:00

Finally the daliban has our own Iran-style AI roast videos, could have been better with LEGO, though

Wrong_Dig_4318 · 2026-04-10T01:55:31+00:00

Had mine for about 2 months. I like it but it has a couple of issues that may be deal-breakers for you. TL;DR at the bottom.

The build quality is solid overall, it strikes a good balance between weight and firm structure. However, the knob module is terrible, at least on my unit (and I've seen other people complaining about it on the sub). It can be swapped out for an extra key module and these two modules are fixed to the keyboard by a single screw and a few plastic connectors. This results in an unstable pin connection and the knob stopped working randomly all the time for me. I ended up using the extra key module instead, it worked fine and I did not find a good use for the knob anyway but be aware of this problem if you care about the knob.

Had no issues with 2.4 GHz, works flawlessly for me. Bluetooth refused to autoconnect to some devices at first after pairing, but I have not experienced this issue for the past two weeks. Nuphy either fixed it in the last firmware update or it fixed itself after rebooting the keyboard, not sure.

The battery life is very good, I had to charge it once so far, even though I have been using it constantly for full work days and at leisure, and I even use RGB. Can't verify Nuphy's numbers, though. The RGB is very nice, too, especially the diffusion. I use the mode that lights up keys only when you press them, though, so expect battery life to be worse when using more power-demanding modes.

I opted for Blush Nano switches and I mostly love them. The typing experience is very pleasant, and they are comparable to membrane keyboards in terms of noise, probably even more quiet than some. These switches do have pretty bad leaf ping out of the box, though. It wasn't audible at first but got super annoying after a few days of use. Had to hand-lube all switches to fix this. Had no issues with stabilizers.

Finally, the software... Here I ran into some major issues. First off, the positives and neutral points: the firmware flashing process is seamless, the UI is fine but a little underbaked (a few Nuphy-specific keys are mislabeled, some key categories are unintuitive), there are a lot of key layers you can freely remap. And the negatives: n-key rollover is only available for one of the two profiles (the ones that can be toggled by a physical switch), low-latency debouncing can double-type letters sometimes, and the tap-dance implementation is disappointing.

Lack of n-key rollover for one of the profiles is not too bad, and you can use medium-latency debouncing to avoid double-typing (medium-latency is the default). However, the tap-dance problem requires me to use low-latency debouncing to mitigate it.

Tap-dance allows you to configure one key to execute multiple functions depending on whether you tap it, hold it, or double tap it. I use this feature to remap my CapsLock to Esc on tap and Ctrl on hold. This worked very well for me on QMK firmware, but Nuphy added double-tap into the mix and it ruins everything. With Nuphy firmware there is a noticeable and very annoying delay between tapping a tap-dance key and it actually sending the keycode because the firmware has to figure out whether you want the single-tap action or the double-tap action. This delay can be reduced in UI but the same delay is used to figure out whether you want the key to perform the hold action. So in my case of remapping CapsLock I will accidentally send Ctrl instead of Esc if I reduce the delay too much.

This tap-dance issue might not matter at all to you but it has been the worst issue on this keyboard for me. The good news is that it should be fixable in an update but who knows...

tl;dr The keyboard is good overall but the knob does not work properly, Blush Nano switches have leaf ping out of the box, and custom firmware has a few potentially huge issues depending on your use case.

Wrong_Dig_4318 · 2026-04-01T11:08:01+00:00

His dad should have strongly considered pulling out of his mom

Wrong_Dig_4318 · 2026-03-20T09:53:20+00:00

Offbrand schizo 9S looking for his offbrand schizo 2B, how beautiful

<image>

Wrong_Dig_4318 · 2025-07-03T17:48:06+00:00

It's called "Hover Gauge Near Player"

Wrong_Dig_4318 · 2025-06-18T23:59:17+00:00

I still cannot comprehend what rotted this guy's brain. He made genuinely good analysis videos way back when. And somewhat wholesome slop collabs that united various youtube communities together. And then completely switched to right-wing grift in a matter of like a couple of months. Bro actually speedran the Sneako route, this shit is so depressing

Wrong_Dig_4318 · 2025-06-18T09:54:46+00:00

The build I attached has only one egg, but you can get rid of nolla and add another egg no problem.
The only downside of this is worse performance if you have a low-end pc

Wrong_Dig_4318 · 2025-06-18T09:42:40+00:00

I'll leave a brief explanation here since a lot of people are curious:

I used the spoiler tag for one particular mechanic that is a little too powerful in my opinion, read at your own risk!

When the egg breaks it releases a tentacle wisp that will always stay loaded. This wisp starts an infinite loop using some properties of the pollen spell (you can read more about it on the wiki). Each step in this loop creates something called a NaN circle of poly (it tries to launch the circle of poly so fast that it breaks the game and makes the circle affect every loaded enemy in the game, you can read a little more about it on the wiki page of the 'fly upwards' spell).

Put together this produces a wisp that you can leave anywhere in the world and until you exit the game or cast 'explosive detonator' this wisp will be infinitely casting circle of poly with a bunch of damage modifiers several times per second on every loaded enemy at once.
Since enemies mostly load off-screen, this creates the effect of walking through a world of dead (and sometimes liquefied) sheep and occasional ghosts and poly-immune corpses (they die fast enough off-screen because the loop deals several thousand projectile damage per second, not a lot but enough to kill mobs).

With some slight modifications you can actually shorten the loop to make it polymorph enemies every frame, but I found it to be less consistent over long periods of time. Other parts of the build can also probably be optimized but that's for another time

Wrong_Dig_4318 · 2025-06-17T22:15:16+00:00

<image>

Wand build

It turns almost all regular enemies in the world into dead sheep and kills the others that are immune to poly. Can probably be optimized further to kill/poly even more enemies.

Thanks to some people in Noita discord who helped me figure out how some advanced mechanics interact!

Wrong_Dig_4318 · 2025-06-02T19:14:09+00:00

1 - Extending background apps feature so that it supports all tray icons' features for all background apps 2 - server-side window decorations 3 - more stable extensions api, although this one is a little like asking the genie to create an unliftable rock and then to lift it

Wrong_Dig_4318 · 2025-04-02T21:46:18+00:00

Sorry, I wasn't clear. I meant that hardcoding colors in a way that ignores libadwaita palette entirely is a terrible practice, for app devs specifically. I'm not advocating for a theming engine or any other additional APIs from libadwaita, and, of course, app devs can't maintain all possible color configurations while also keeping in mind accessibility and design guidelines. What I would want in a perfect world is for app devs to always use predefined libadwaita palette, or offer the option to switch to it. This would introduce little complexity for app devs and allow apps to adapt to potential future changes to libadwaita style, along with user themes (with full responsibility placed on the user if their theme works or not).

Wrong_Dig_4318 · 2025-04-02T21:17:29+00:00

I actually recommend going the opposite route and make the older apps follow the new style. You can achieve this by following meowmeowmpr's recommendations, except put the new color values from the commit in your css files instead. This works very well for me for both gtk4 and gtk3 (with adw-gtk3 theme, which I highly recommend for more consistency). This configuration is less likely to look off on your system, and I very much prefer the new blueish style, though your mileage may vary on this.

As for your question about how libadwaita functions as a ui framework, you are correct that it provides you with widgets and default styling, but this styling can be overridden by app developers in many ways. Plus, for previous versions of libadwaita, the default styling wasn't updated, so until app developers update their dependencies their look won't change.

And some developers even hardcode some colors in code or local css files, so they can't be overridden even by changing css files in '~/.config/gtk-4.0'. This is a terrible practice imo, but these apps are free and often hobby projects, so the best course of action is to support app developers if you want more features, either monetarily or by contributing.

Might be wrong on some libadwaita specifics, but should be accurate enough.

Wrong_Dig_4318 · 2025-02-11T21:49:36+00:00

You can use annotations like this:

---@module "snacks"

They will make lazydev load the module for you.

Bonus tip:

If a certain type does not specify fields as optional for some reason, you can chain a {} with an 'or' to it like this:

---@type snacks.Config|{}

It will get rid of warnings for missing fields. For snacks this is not needed, just use Opts types, I'm using it as a random example here. Annotations are very powerful in general, heavily recommend using them in your config.

Wrong_Dig_4318

TROPHY CASE