Pedro Casotti

Interesting thoughts, I really dislike the "fork and patch" approach, we currently have very little room for user customized code. I like the separate crates for LED and display, maybe...

> the `Controller` waits for a channel, say `CONTROL_EVENT_CHANNEL`, if there's `ControlEvent` coming, the all `Controller`s process it one by one until the event is consumed. Another approach is to...

> Hmmm, `watch` sounds a bit like the listener concept from Java and co, but maybe you meant that differently. RMK uses channels from `embassy`, which are implemented similar to...

> Maybe we should manage them in a single place to avoid runtime panic of `unwrap!(CONTROLLER_CHANNEL.publisher());`. You mean like a global publisher under a mutex? Seems good, but I don't...

I'm experimenting on this [branch](https://github.com/pcasotti/rmk/tree/feat/rpc), where I replicated a smaller version of `postcard-rpc` to experiment on. I'm using a proc macro instead of `define_dispatch!` to deal with the generics, the...

On the host side, looks like we cannot use the postcard `HostClient` if we're sending messages over HID. The only thing left to use from postcard_rpc is the unique key...

> yes, postcard uses USB bulk, and I think that's fine? USB HID is much slower. And WebUSB provides raw USB access which can be used to read/write data via...

Adding a note here. Before we add support for vial matrix tester we need to implement the vial security feature, otherwise a malicious program can use the vial protocol to...

It's technically possible to do on the user side using controllers. If we want to add it in the library we need to think how will the display options be...