Hi again! Thanks for your intro - I wish Slack could somehow encourage more people to do the same 🙂 I have been spiking a JSON<->Crux translation for the HTTP interface recently. I think the main constraints are that all attributes become strings and IDs would have to become nested maps, e.g. something like `{"crux.db/id": {"crux.db/json-id": true, "some-key": "some-identifier"}, "color": "red"} -- you would also have to sacrifice the ability to use Crux with edn at the same time, otherwise you will probably run into compatibility issues (p.s. I will respond on the email thread as soon as I can)