Viewing profile — cjus

For just over a year now I've been contributing to an open source project called Moose. Moose is written in Rust and supports building applications in TypeScript and Python that le…

Hey everyone. This may be a bit out there. I'm a developer and certified instructor in Qigong - an ancient mind body practice. Some months ago I decided to apply AI to create modul…

Reading through the comments here I'm realizing that my single biggest error may have been the use of the word "Universal" :-D When you consider the spec as a "basis for agreement"…

The spec describes a message format and isn't intended to be a formal Internet RFC. As such, the thought was to leave definitions up to users rather than dictate things like priori…

Thanks for this. The need for canonical JSON is perhaps the best reason for dropping the signature field from future versions of the spec. However, because only the `to` `from` and…

+1 for mission statement, use case. The point about inconsistent formatting is that by aligning a team(s) on how a message is formatted groups can avoid the introduction of multipl…

In an earlier version of the docs I actually had the spec in the readme but felt the sheer size was enough to send folks running. Using the readme to describe the spec (which I rea…

I've always liked s-expressions, unfortunately, it hasn't caught on in the circles I travel.