Description

it is very strange to me that this tool for creating keyboard firmware has network dependencies that seem very hard to remove. i spent a few hours trying to get the whole stack running locally, but had very little success

i have some motivations for wanting to do this:

• i want to be able to edit my keyboard firmware when i don't have internet access
• i do not trust any of the services in that architecture diagram to be around forever
• i do not want to have my keyboard layouts stored on other people's computers

i feel like these are all reasonable desires, and kinda fundamental to tinkery open source stuff in general

my ideal version of this would be an entirely self-contained desktop app with a web view that exposes the existing configuration gui without hitting the network at all. after all, if being able to run this thing offline is a desirable thing, then it should be as accessible as possible

if it is already possible to run the stack locally, i would really like there to be documentation that covers how. i would be willing to write it myself, given guidance to understand what's necessary