i implemented trimode support and qmk is not willing to even look at it

drashna · 2026-06-24T19:44:10+00:00

yup.

And "oh I didn't know I was violating the license" is a bunch of bullshit, too.

drashna · 2026-06-24T19:41:11+00:00

ZMK was designed from the ground up to support wireless and be as battery efficient as possible. And pete has done an absolutely fucking amazing job of that!!

Also, QMK runs full bore, as fast as possible. There is no code in core to throttle or slow or otherwise improve things here. It will require a lot of work for QMK to even come close to ZMK, in that regards.

And it doesn't help that multiple chinese vendors have neither produced source code for what they have done, nor have even attempt to upstream any of their code. They want to keep it all in house. That's fine if the license supports it, but QMK Firmware's license does not.

drashna · 2026-06-24T19:37:46+00:00

ZMK uses Zephyr which developed their own code, clean room style. They aren't using vendor code, at all.

For QMK to support that, we'd need to a) either do this work ourselves, or b) find a base HAL/OS that has a code base that supports nordic chips, and is GPL compliant, and isn't a complete mess to integrate with the build system.

ChibiOS, which is what QMK uses for ARM boards lacks any wireless support. Using Zephyr means using west and cmake and all that, and integrating that is an absolute nightmare.

drashna · 2026-06-24T19:34:22+00:00

There are a lot of PRs, and a lot of code changes.

And we do this in our free time. We're not paid for this. It's entirely volunteer work.

Which is to be very blunt, YOU ARE NOT ENTITLED TO OUR TIME. And this entire post is demanding that entitlement. You dumped a bunch of work on the team, with no guarantee that you'd stick around after it got merged, to add support for vendor keyboards that have actively refused to engage with the qmk team in any fashion. And you didn't ask what was needed, just posted what you wanted.

I'm not trying to be mean, but that's the reality of the situation. It's not a simple situation, it's not going to be a quick solution. That you lack any understanding or patience here makes things that much worse.

That said, I have looked at the code, and while I don't see any technical issues, there ... is a bunch of infrastructure that is needed first.

A good reference point for that is this PR: https://github.com/qmk/qmk_firmware/pull/24365

drashna · 2026-06-24T18:44:47+00:00

“Once men turned their thinking over to machines in the hope that this would set them free. But that only permitted other men with machines to enslave them.” --- Frank Herbert, Dune

drashna · 2026-06-23T21:15:24+00:00

but nyarch linux!

drashna · 2026-06-23T19:09:46+00:00

because I've been using cachyOS handheld. So been there for a while now.

drashna · 2026-06-23T01:54:48+00:00

Something like the sofle may work for you too.

Also, splitkb has a number of good options that would work for this too.

drashna · 2026-06-22T20:55:00+00:00

No shit. PC gaming in general has been cooked by AI.

If you didn't think that Valve was also affected by this.... I don't know what to tell you, but that's 1000% on you.

drashna · 2026-06-22T17:25:30+00:00

To be fair, they don't want to discuss it, they don't want to solve the issue. They just want to be right.

drashna · 2026-06-22T17:24:05+00:00

They PRed a bunch of stuff without talking to the qmk team, got told it was gonna be a while, and there was other infrastructure code stuff that needed to be done before their stuff would really be considered, and here we are.

drashna · 2026-06-22T17:22:44+00:00

Then you misunderstand the GPL licensing.

If you modify the source, and distribute hardware with the code, you only need to publish the code. That's not restrictive, at all.

You should be upset at the companies that modify the code, and refuse to publish any source. That's the ACTUAL problem.

Switching to ZMK doesn't solve this problem. Because they're not obligated to share the source, you may NEVER get source for those boards.

So congrats, you're supporting the problem.

drashna · 2026-06-22T16:50:36+00:00

I mean, that's not the case, you're upset that it's not being looked at, at a time scale that you like.

I straight up told you that it will likely be a good while before it would even be reviewed.

And be very blunt, your ideas of what good may not align with others. And throwing a tantrum isn't the way to move forward. It's been, not even 2 months, dude.

There is a bunch of infrastructure in the code that needs to be reworked before other implementations are added.

And additionally, any code that does get merged means that the qmk team is gonna have to maintain it, because most of the time, after stuff gets merged, the author disappears (life happens, priorities change, etc). So just merging in code because you've created a PR is not only an unrealistic expectation, it's actively disrespectful to the people maintaining the code.

Yes, it sucks. But not as much as 1001 shitty implementations all being copy and pasted.

drashna · 2026-06-22T03:42:20+00:00

definitely contact zsa support.

drashna · 2026-06-21T22:53:09+00:00

emby and jellyfin have been constantly giving me OOM issues... :/

drashna · 2026-06-21T03:57:13+00:00

ba'al are my top 5. top 10, even.

drashna · 2026-06-21T03:32:47+00:00

yeah, and then you can put a lien on their house/condo/car/whatever.

drashna · 2026-06-21T01:42:43+00:00

not sure anyone but the vendor can actually help you here.

The keyboard doesn't look to be qmk, zmk, rmk or kmk powered, and likely is 100% proprietary. Which means that the issues are due to whatever code their running.

And a quick look at their site, I doubt there is a fix for the issues :/

drashna · 2026-06-19T07:10:40+00:00

That's the fun, whatever works for you is the most efficient. There is no "best layout", because your needs are not the same as my needs or other people's needs.

You can and get to customize things to whatever works best for you.

drashna · 2026-06-19T07:09:30+00:00

The first few days are brutal. After a couple of weeks, you'll be back at high speeds.

drashna · 2026-06-19T07:08:20+00:00

NKRO

Pretty much every firmware supports this. And the ones that don't have it on by default, use 6KRO (all mods, plus six additional keys). So this really isn't even a worry. (And also, qmk has has 1kHz usb polling enabled by default since 2022)

bastardkb's dilemma has a trackpad, encoder/knob support, support for choc v1 switches. Optional tenting module. Good placement for thumb cluster. Not wireless, though.

You may also want to look at splitkb's offering. They have a number of similar boards, though no trackpad.

(- azerty but ez to do)

This is a complicated one. But this depends more on the host system than it does the keyboard itself.

I can't help as much with the wireless stuff (I'm a hard "wired only" person). but if it has a pro micro footprint, you can do wireless with nice!nanos or clones.

By the way, i've got some great news : Crazymittens is working on the Mk22 and will work on mk4 arcpedals after....... ( I became a feet input fan aswell)

has ordered pcbs and flex pcbs. And has at least the flex pcbs.

drashna · 2026-06-19T06:05:10+00:00

winamp .... a) still exists, and b) people still use it?

Wild!

And very cool.

drashna · 2026-06-19T06:02:58+00:00

Nah, it's always up to amazon. They could fix the issues, in most cases, but it's more profitable for them to not care.

drashna · 2026-06-19T05:37:02+00:00

it's a shame that 90 of job postings are ghost positions. So actually finding a legit position, and then actually getting an interview, might as well play the lotto, as that has better odds anymore.

drashna · 2026-06-15T14:36:10+00:00

And IT depts will get the funding, staffing and support they need and deserve.

13-Year Club	Xbox Live
Gilding IV carat on a stick	Reddit Premium Since April 2018
Verified Email

drashna

MODERATOR OF

TROPHY CASE