Lucid One

I'm not super picky on notation but one option might be something like `YYYY.0M.0D`. Either way I think calver could benefit from a more formal definition, as it will make...

I'm not sure it is aesthetically optimal, but I'm wondering if `` make sense because they are already considered reserved for version comparison and it wouldn't make sense to compare...

I think there is some ambiguity regarding `MICRO` I wonder if a `00MICRO` notation is worth specifying.

['On Debian and derivatives including Ubuntu this is "dialout"; on Gentoo/Fedora/openSuse it is "uucp".' ](http://catb.org/gpsd/installation.html) Please let me know if you have any questions as I am currently working on...

@OpusK did you have a chance to look at https://git.sr.ht/~lucidone/dmxl Thanks!

Our team is also interested in seeing improved sync read/write performance merged. [Semantic Versioning](https://semver.org/) the SDK would probably help.

Also worth considering. https://community.apigee.com/articles/21711/dsig-part-3-xml-dsig-vs-json-web-signature.html

Can you explain more? https://tools.ietf.org/html/rfc7159#section-8.1 Indicates that ``` Implementations MUST NOT add a byte order mark to the beginning of a JSON text. ``` Are you suggesting something like ```...

I'm eventually moving all of my efforts to https://sourcehut.org/

One thing to try is adding a sleep in the host app reply so this happens 100% of the time.