key-ripper VS qutebrowser

Nice - a friend and I worked on my keyboard's debouncer and call it "eager debouncing", not sure if there's an official term for it. I agree that it's much better for latency.

Awhile ago I made an remote infrared sending tool so a raspberry pi can control my A/C unit

https://blog.bschwind.com/2016/05/29/sending-infrared-comman...

Since then I made a much slimmer, cheaper, more efficient version based on the ESP32 but I haven't written up much about that.

I also created my own keyboard with firmware in Rust

https://github.com/bschwind/key-ripper

I've done a bunch of other small one-off projects too.

Good luck! I have an open source keyboard project in KiCad as well, feel free to reference or use anything from it.

Not sure if the author of the post is around, but I guess this is a question for anyone who has designed keyboards: have you ever tried using shift registers for reading all the keyswitch inputs, and is it worth it? Does it mean you don't have to use a diode per switch?

I've designed my own as well but just went with the traditional key matrix with a diode per switch. Works well enough for the current size.

https://github.com/bschwind/key-ripper

All the source files can be found here

I made my own keyboard layout just the way I want so I would put these caps on that, or replace the stock caps that came with my Filco board.

Twist looks awesome, I'd put it on my key-ripper

You can absolutely run Rust on the pico - I designed a keyboard with Rust firmware which runs on an RP2040. That being said, wireless functionality might not be existent yet in the Rust world for the Pico W, but I'm sure it won't take long to get added.

I looked at the schematic and it seems reasonable. I just completed an RP2040 project with USB C and it works correctly. You can see the project files here

I don'r know if this counts but there is also https://www.qutebrowser.org/ which uses qt webkit IIUC

I searched this issue and saw there were already open issues on github, and it is an upstream issue with QtWebEngine.

You can add [aria-haspopup] to your hints.selectors setting (from a config.py, see the configuration docs) to get the same effect.

There is a small how-to here: Switching to Qt 6 by default · Issue #7202 · qutebrowser/qutebrowser

There is a Qutebrowser user script for 1password: https://github.com/qutebrowser/qutebrowser/blob/master/misc/userscripts/qute-1pass. Disclaimer: I am the original author (it’s been refactored a lot by mkonig since I originally wrote it). My original version is here https://github.com/tomoakley/dotfiles/blob/master/qutebrowser/userscripts/1password

Glad to hear! You'd either add it to the userscripts folder in the repo, or add a link to the README about it and host it elsewhere.

It seems to work fine with Qt 6, so I guess this is just some missing feature on Qt 5. Maybe something changed on Wikipedia's side.

Show PID in :process error message · qutebrowser/qutebrowser@c41f152