Zach White

> Yes, I apologize. > > It wasn't meant to be condescending. It was a remark about the stale nature of the upstream. I apologize. Apologies accepted. > Right, but...

> The current project have been forked and moved around. I'm not sure if when `hidapi` was uploaded to pypi is a indicator of when people started using that project,...

> In a normal situation we would just downstream patch this and you would never hear from us again, but the awkward project structure (as mentioned and explained) makes this...

> That would solve my issues by patching inn the vendored library. I won't promise it'll make it into this cycle (which closes to new PRs in 10 days) but...

I have a [branch I've been working on](https://github.com/qmk/qmk_firmware/tree/info_json_config) that adds this (as well as a lot more.) I'm targeting the first develop merge in 2021.

@codebymiles The overall [QMK roadmap is kept here](https://hackmd.io/fpPylbKgQROie6ndKHimfA), and basically what we lack here is a design. Someone needs to do the work to define how custom keycodes work, get...

> I'm thinking Configurator needs another endpoint to tell the compiler to include the `keymap_steno.h` before this will work. Someone needs to extend the keymap.json format to support steno, then...

> No, I wouldn't change the code like that, I would make it a setting in the data model. I assume this refers to the metadata hostname? I'm not tied...

Getting back to this, I think I can create the workflow to upload to S3. I'll get started on that. That still leaves an open question around implementation for specifying...

The status is I still need to figure out where to host the files. Digital Ocean has an App platform we might be able to use that's CDN fronted, but...