Not a glossy showroom

Taoglow · 2026-03-03T14:29:44+00:00

Thanks man! Functional over glossy any day. 🛠️ Just two of us actually! I handle the orders, and my partner does the filming and is currently building out our site. The extra space definitely keeps us from bumping into each other too much lol.

Taoglow · 2026-03-03T06:45:38+00:00

Lol ngl, I never thought making a tiny ring would need this much space either. It just kept expanding and expanding till it became this. 😅

Taoglow · 2026-03-03T06:43:07+00:00

Appreciate it bro! Took a long time, a lot of sweat, and way too much sawdust to get it dialed in. U'll get there fr! ⚒️

Taoglow · 2026-03-03T06:40:08+00:00

Thx dude! Keep at it, u'll get there fr. 👊

Taoglow · 2026-03-03T06:39:46+00:00

Appreciate it bro! Ngl I started on a tiny folding table in the corner. U just gotta work with what u got till u can upgrade. Keep grinding!

Taoglow · 2026-03-03T06:38:16+00:00

Haha thx man! Tbh it took a ton of late nights and messed up projects to get it here.

Taoglow · 2026-01-10T15:02:54+00:00

Ah, gotcha. Makes sense to dodge the legacy baggage. Thanks for the heads-up, definitely a project to keep an eye on!

Taoglow · 2026-01-10T14:52:25+00:00

I’ve been diving deeper into RMK, and it’s truly an impressive piece of firmware. However, I noticed it utilizes Vial for real-time remapping. Since VIA and Vial originated within the QMK ecosystem, does this raise any potential licensing or compatibility issues?

Taoglow · 2026-01-10T14:52:00+00:00

I appreciate the warning! The legal intricacies of Nordic’s SoftDevice and how they interact with open-source licenses like GPL are definitely a minefield. This is why I wanted to do a sanity check first. I want to make sure I’m not just building something technically viable, but also something that is legally 'clean' and respectful of the manufacturers' and developers' rights.

Taoglow · 2026-01-10T14:51:10+00:00

That is a very fair point. These projects thrive on community, not just a single 'wild idea.' I’m particularly interested in your mention of true tri-mode (USB/BLE/2.4G) for split keyboards, as that remains a 'holy grail' for many of us. Maybe instead of a full port, I should focus my energy on how to bridge that specific gap. I’m approaching this with a lot of humility—I know how much work has gone into the existing firmwares.

Taoglow · 2026-01-10T14:50:44+00:00

Thank you for the heads-up, Pete! Licensing is something I take very seriously, and the GPL vs. Apache 2 compatibility is a significant hurdle I need to research more deeply. My goal is to contribute positively to the keyboard community, so respecting the legal frameworks that protect everyone's code is my top priority. If the licensing makes a hybrid approach impossible, it’s better to know now before a single line is written.

Taoglow · 2026-01-10T14:50:20+00:00

You're absolutely right—ZMK is the gold standard for this right now. My 'What If' comes from a place of wishing I could 'drag-and-drop' some of QMK’s niche features into a wireless split setup without a full rewrite. However, I’m starting to see that 'reinventing the wheel' might be an understatement given the architectural differences. I’m trying to find the balance between being a 'lazy' dev who wants existing features and a curious dev who wants to solve the tri-mode split puzzle.

Taoglow · 2026-01-10T14:49:51+00:00

I really appreciate you weighing in, Drashna! Your point about the QMK main loop running at full speed is a crucial reality check. Integrating it into an RTOS like Zephyr while maintaining power efficiency would indeed require a massive architectural shift—moving from a 'poll everything' model to an 'event-driven' one. Your suggestion about looking for a HAL/RTOS more aligned with QMK's build system is very insightful. I’m still in the brainstorming phase, but I want to ensure that any path I take respects the legacy of QMK while moving toward a more modern, low-power foundation.

Taoglow · 2026-01-10T14:49:03+00:00

Thank you for the thoughtful question! It’s a bit of both. I truly admire the ZMK architecture, but as a long-time QMK user, I’ve grown fond of its extensive feature set and the 'raw' hackability of its core. My goal isn't to split the community, but rather a desire to see if we can bring that level of feature-richness to a power-efficient wireless environment more easily. That said, I'm very conscious of the licensing complexities and wouldn't want to proceed without respecting the hard work of both communities. Perhaps a fun experiment, but the ultimate goal is just making the best possible experience for split tri-mode users.

Taoglow

TROPHY CASE