enctool VS Shynet

https://concise-encoding.org/ is looking for help!

I'm planning to release v1 later this year, and there are still a number of things to finish:

- Finish upgrading the portable testing rig (whereby the tests are defined in CTE format so that they can be run against any implementation).

- Bring the Antlr grammar files up to date and make sure they're as easy as possible to build CTE parsers from.

- Add schema validation support to https://github.com/kstenerud/enctool for Concise Encoding documents (using https://cuelang.org/)

- Critiques on the format itself (passages that are unclear or don't make sense, features that shouldn't be there or need more work, etc)

- Implementations in other languages & platforms (CBE is more important to start because one can always use enctool to convert between CBE and CTE).

It's still in the prerelease stage, but v1 will be released later this year. I'm mostly getting hits from China since they tend to be a lot more worried about security. I expect the rest of the world to catch on to the gaping security holes of JSON and friends in the next few years as the more sophisticated actors start taking advantage of them. For example https://github.com/kstenerud/concise-encoding/blob/master/ce...

There are still a few things to do:

- Update enctool (https://github.com/kstenerud/enctool) to integrate https://cuelang.org so that there's at least a command line schema validator for CE.

- Update the grammar file (https://github.com/kstenerud/concise-encoding/tree/master/an...) because it's a bit out of date.

- Revamp the compliance tests to be themselves written in Concise Encoding (for example https://github.com/kstenerud/go-concise-encoding/blob/master... but I'll be simplifying the format some more). That way, we can run the same tests on all CE implementations instead of everyone coming up with their own. I'll move the test definitions to their own repo when they're done and then you can just submodule it.

I'm thinking that they should look more like:

    c1

Yes, that is exactly the aim of the binary format. It has a few basic concepts like being byte-oriented, 1-byte headers for most things, ULEB128 encoding for large values, same chunking mechanism for all arrays and string-likes, same "open/close" mechanism for all container types, etc.

The binary codec is VERY simple, and can be trivially implemented for an async-safe or otherwise constrained environment. In fact, I expect that many implementations will only build the binary codec, since you could just pass any recorded binary data through enctool [1] or whatever to see or manipulate its contents as a human. An embedded system would have no need to process the text format.

[1]https://github.com/kstenerud/enctool

+1 on shynet! I use it for my personal website and my blog, and it's been working great.

I got it up and running with Podman, so no need to install and run the Docker daemon. I also fixed SQLite support [1], so no need for an additional DB server.

I analyzed available open-source web analytics tools [2] and AFAIK there is simpler solution for web analytics that doesn't involve a third party.

[1] https://github.com/milesmcc/shynet/issues/208

[2] https://blog.fidelramos.net/software/privacy-respecting-self...

I like shynet

I am using shynet for a while now. Really all I need to know :)

https://github.com/milesmcc/shynet

There's also Shynet.

Oh that is actually shynet self hosted analytics which is privacy friendly. https://github.com/milesmcc/shynet

But I think I'll just remove it for now.

Shynet: https://github.com/milesmcc/shynet

The goal is to provide, privacy-friendly, and detailed web analytics that works without cookies or JS. And it's completely open source.

Full disclosure: I am the primary maintainer.