Ask HN: Who wants to collaborate?
Ad-hoc data formats like JSON and XML are too insecure for the modern world, so I&#x27;m developing a new format to remedy this [1].<p>It&#x27;s a twin format, one binary and one text, so that you can input &#x2F; edit the data in text, and then it passes from machine to machine in binary only (or convert back to text if a human needs to inspect it). The binary format is designed for simplicity and speed, and the text format is designed for human readability.<p>Both formats are designed for security and minimal attack surface, while providing the fundamental data types we use in our daily life (so you&#x27;re not stuck doing stringification and base64 fields and other such hacks).<p>I&#x27;ve pretty much completed the base format [2], and am 90% done with the golang reference implementation [3] plus some standard compliance tests, but I could use a lot of help:<p>- Reviewing the specifications and pointing out issues or anything weird or things that seem wrong or don&#x27;t make sense.<p>- Implementations in other languages.<p>- Ideas for a schema.<p>- Public outreach, championing online.<p>[1] <a href="https:&#x2F;&#x2F;concise-encoding.org&#x2F;" rel="nofollow">https:&#x2F;&#x2F;concise-encoding.org&#x2F;</a><p>[2] <a href="https:&#x2F;&#x2F;github.com&#x2F;kstenerud&#x2F;concise-encoding" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kstenerud&#x2F;concise-encoding</a><p>[3] <a href="https:&#x2F;&#x2F;github.com&#x2F;kstenerud&#x2F;go-concise-encoding" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;kstenerud&#x2F;go-concise-encoding</a>