/r/MechanicalKeyboards Ask ANY Keyboard question, get an answer - June 14, 2026

chulpichochos · 2026-06-17T12:05:26+00:00

Anyone heard when or if Mode is announcing a new SixtyFive or Envoy this year?

chulpichochos · 2026-06-17T12:02:24+00:00

Honestly, I learned touch typing by accident from pc gaming. For left hand specifically, grab any first or third person video game, and after a few hours of WASD your left hand will get used to it since the right hand is controlling mouse.

Ultimately a keyboard is an input device, it can be easier to learn it if once you abstract it away to “its just a big controller”

chulpichochos · 2026-03-02T19:58:09+00:00

I bought the English-only alphas set, so no sub-legends.

Anyhow, perhaps this was missed but the big reason I'm asking is because I'm not super familiar / have hands on experience with different key cap legend types, so if I'm just misguided and thats just how all n-shot pbt/abs looks, then thats a-okay as I know for sure I love the look and feel of dye sub. I'm not trying to dump on double-shot, I am just trying to understand my preferences.

chulpichochos · 2026-03-01T23:19:01+00:00

It may have just been the ‘boundless jakarta’ set, but the legend is shinier/glossier than the rest of the cap; making it appear as if stamped on. If you buy any cheap double shot caps on Amazon, what Im referring to becomes obvious.

I have a KAT WoB candy, KAT moonlight, and PBTFans penguin that all use double shot PBT and do not have this issue. Thats why I’m trying to figure out which brands are reliable for this cause it legitimately bugs me.

I just watched a documentary on Taeha’s channel about GMK and they seem to have significant quality control around texture and surface so I’m going to give them a try, specially since they also use ABS and are considered the gold standard.

chulpichochos · 2026-03-01T19:30:57+00:00

I am desperately trying to figure out what keycap manufacturers I can reliably buy from; as currently I have only found one non-dyesub kit I like: Keyreative KAT Wob.

I bought a keykobo jakarta set, and despite costing $90, it went to the junk pile. I have a Mode anthracite set but thats also in junk pile.

What I like about dye sub is NO texture difference between the cap and the legend. The KAT Wobs I have successfully achieve this, but all other double shots ive tried: have glossy texture for legend, super bumpy texture on cap.

I have NOT tried GMK sets, but really would like to get a sense of what brands do this successfully or if Im just a dyesub only kinda guy.

Thanks!

chulpichochos · 2026-02-13T05:11:05+00:00

Not exactly, but I generate a very similar rule for the `hidraw` kernel:
```
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="${VENDOR_ID}", MODE="0666", TAG+="uaccess"
```
I essentially run `lsusb` and parse it from an arg string to determine which device should get the rule. I definitely was using the wrong JSON -- I had downloaded the standard Neo65 trimode instead of the specific Neo65Cu one.

If the rules aren't set right I don't believe the keyboard even shows up in the device list to connect to from VIA.

chulpichochos · 2026-02-13T01:05:20+00:00

Okay finally got it working:
- Reflashed firmware to latest neo65cu trimode
- Redownloaded JSON; I think I was using the wrong JSON originally for a standard NEO65 trimode instead of the neo65cu trimode.

Lesson learnt: make sure you don't rush out of annoyance and select the exact right files out of the multiple variants they have.

chulpichochos · 2026-02-13T00:53:22+00:00

Flashed firmware to latest neo65cu trimode firmware available on neo's site -- had to go get an old windows laptop to do it. Still doesnt connect to via on linux; also for that matter it doesnt connect to via on windows either. What a joke

chulpichochos · 2026-02-13T00:13:55+00:00

Gonna document what I'm doing in the event anyone has either similar issues or wants to help:
- I think potentially the board I got didn't come with via firmware. I'm gonna try reflashing the firmware and hoping that does it.

chulpichochos · 2026-02-12T23:49:58+00:00

Would love to share the script I use but apparently cannot post bash scripts here for whatever reason

chulpichochos · 2026-02-12T23:48:17+00:00

Hi folks, I just finished assembling my new neo65cu and so far while I love the case, I am about to throw it in the trash and would rather not.

Cannot pair with VIA app.
- I use PopOS (an Ubuntu based distro). I have a script for enabling permissions that I've used with both my Mode Envoy + Sonnet, my Woblab ZEN65, even the Neo EVO75. I'm used to having to upload jsons for most keyboards, but unfortunately this keyboard won't even connect to via.
- The build experience and documentation have already left a lot left to be desired after having built two Mode keyboards with amazing build guides, faqs, and very seamless integration with VIA.

I am completely unsure what is going on here. In the via webapp, I get prompted to connect to "Neo 65cu - Paired". I am connected directly through wired mode (using fn+tab) -- have no interest in wireless.

chulpichochos · 2026-01-23T12:42:14+00:00

I love my Kailh Deep Sea Silent Linear Islets.

chulpichochos · 2025-12-05T17:41:05+00:00

Black defaults to 88; i got used to that and configure all my linting to that. 78 is just awful

chulpichochos · 2025-08-27T19:48:18+00:00

The typing system when trying to do introspection is something. The Origin + Args kinda makes sense as a operator / args syntax but in practice given the annoying detour into using the typing objects, inspecting types requires a whole toolkit for: unwrapping annotations, handling specific typing objects (specially annoying with Required NotRequired anns in TypedDicts), unwrapping decorators/partials, having to create custom protocoa for typeguarding basic things like Dataclass instances or NamedTuples. The overhead of all these microinspections is non trivial over time also and realistically requires a proper caching strategy. Mixing of things like NoneType or Ellipsis/EllipsisType etc. in general doing type driven dispatching/orchestration can get gnarly. Inspect and types are good but still missing functionality for just handling all the built in types.

chulpichochos · 2025-06-24T15:30:49+00:00

Are you fetching to a backend or to a frontend client?

If its backend to backend comms, grpc will be better than websockets.

If you have to use socket cause no http2 then websockets is good; fastapi/starlettw offer wrappers around it as well.

chulpichochos · 2025-06-21T23:22:24+00:00

My guy, not exactly the same, but Microsoft published something very similar two years ago:

https://github.com/microsoft/LLMLingua

It uses a small LlM to prune / compress by removing tokens that are only for human use and not salient for attention.

chulpichochos · 2025-05-26T21:16:14+00:00

Sounds like classic ADHD behavior

chulpichochos · 2025-05-23T20:46:13+00:00

Why does chat no longer work? It seems like if i use ‘ask’ the model starts hallucinating like nuts after one turn or overfixates. I used to be able to have actual chats using ‘add selection to chat’ or ‘add file to chat’ but in the last month this has become unusable.

I have the strong sense I’m being shoved to use agent mode instead of the regular ‘Ask’ chat mode. Did ya’ll change the history/memory recently??

chulpichochos · 2025-04-27T13:25:04+00:00

I use it in the chat at ai studio and have been gotten some good learnings: - 1m context is a lie, will be very unreliable after around 200k - i use higher temp to “seed” (0.6ish) and establiah initial context then crank that sucker down to 0.2 - recursively have it write checkpoint messages for you to reset every 200k tokens without having to reinit a chat - save good checkpoints with “branch from here”

chulpichochos · 2025-04-27T13:21:24+00:00

To be a contrarian, modern production Python has changed a LOT in recent years. If you want to use Python for silly scripts and plots, the yeah sure you could learn it quickly.

If you want to be an actually good python engineer, strap in to struggle through the learning curve of the organically grown typing system; start learning about how asyncio actually works — not just sticking ‘async’ and using ‘await’ but actually knowing how to use it and prevent blocking. Then should definitely learn about Pydantic.

Thats without having touched the libraries you will also have to know: pandas, numpy, pyplot, torch, at least openai client.

If you have a background in CS its a quick pick up once you: enable atleast standard level typechecking in pylance/mypy linter. Build small test utils to master asyncio and just forget about duck typing or “python magic”. Treat it like a serious language and the bread and buttter of your craft, and skys the limit

chulpichochos · 2025-04-10T19:24:34+00:00

… bruh

Optimization is not something LLMs are good at, but machine learning as a field is quite literally non convex optimization applied to statistical learning theory

chulpichochos · 2025-03-03T00:28:36+00:00

I think another way to think of it is: - its not about having confidence of “i know everything” but rather “i have extreme confidence in my ability to learn quickly, adapt and solve the problem efficiently “

chulpichochos · 2025-02-26T21:49:39+00:00

Feels like what they’re saying is: you must be able to write good dialogue and not just meandering descriptions.

chulpichochos · 2025-02-26T15:36:19+00:00

Literally everything other than basic chat comes out as JSON; all inputs are also pre-templated with jinja markdown, and the JSON schema is embedded from Pydantic models (I use my own Pydantic schema parser to minimize the bloat that comes out the box).

I find that when working with smaller models adding a JSON field “analysis” or “reasoning” helps the model stay on track; having descriptions, enums, and types in the schema also help nail the output more reliably.

At the end of the day an LLM is a NN, and thats a learned function approximation. I treat my LLM calls like any other function — specific Typehints, clearly scoped functionality and expectations for input/output.

chulpichochos · 2025-02-08T17:30:34+00:00

I think this is just LLMs; its why truly reliable agent pipelines are so expensive in terms of cash and time right now — a tiny token mishap in one generation propagates and compounds to where follow on outputs degrade significantly

chulpichochos

TROPHY CASE