Stephan Auerhahn

> One possible reason to create separate HID interfaces is that various USB APIs may prevent concurrent usage of the same HID interface by different apps, therefore running an app...

To follow up with and summarize some thoughts on future direction: - [Aurora](https://github.com/antonpup/Aurora) has integration code for various RGBLED SDKs/protocols that we'd probably all do well to study in depth...

> @palp Are you aware of OpenRGB? It is based around reverse engineering the protocols sent by the SDK's to the hardware directly and documents the packet structure in the...

Yeah, I think even just the language is significant, as it'll make it more clear that functionality can be added to the QMK protocol that isn't tied to OpenRGB or...

> How are you planning to use this worker? What's sitting on the other end of the connection, making the requests? Do you have queueing logic on that side at...

I think maybe the right term for what both of them do (different from the HTTP API) is "subscription" or something along those lines, versus "queue"?

Though just temporary logic, this bit of code is where I actually assign jobs to workers; the idea is if a worker has a running job it's not considered a...

I've refactored the name and fixed some bugs, while switching to the asyncio-based websockets library. I plan to adjust the parameters with the idea of allowing it to act as...