./configure.py complains about missing Python library and asks to do python3 -m pip install --user docopt ninja-syntax. Yes it does work. But README.md doesn't mention this.

It doesn't mention need for a ninja either.

The methods do not support the "object_hook" keyword argument. There also does not seem some other way to achieve the same result.

This seriously limits its usefulness. Are there any plans to implement object_hooks?

There is an issue with the reference to the HTML spec in README.md in the following part:

This function takes a string of HTML and decodes any named and numerical character references in it using the algorithm described in section 12.2.4.69 of the HTML spec.

This link I assumed would take me to section 12

I am trying to evaluate adapting ArduinoMenu to run under Mongoose OS, and am looking at a two stage implementation plan:

1. get it running on Linux (with a very generic serial input and output device, similar to the Blink or Button examples). I want to do this so I can quickly get the menus going, and make sure I really understand what's going on.

2. move it to Mongoose OS (with an ILI9341

To support the use case of generating videos from still images, the -loop flag should be added -loop 1 per ffmpeg docs.

Currently, this flag is not exposed in EncodingAttributes.

Sanity checks:
This flag should co-occur with a durationAttribute or the encoding will loop forever.

Given that PASETO is designed for "Resistance to Implementation Error / Misuse", I'm surprised the examples don't cover calling JSONToken.Validate, nor does JSONToken.UnmarshalJSON do this on it's own.

The documentation does indicate that the standard claims are optional, which would mean that calling the default set of validation functions during JSONToken.Unmarshal might break the curre

The documentation is not clear about the order in which the entries of a JSON object will be iterated through the JsonValue::entries method. Is it a lexicographic order? Order of definition in the original string?

Issue #68 is letting me think there was some kind of defined order between keys in an older version of the crate, but is now the order of definition.

XMLCoder should have publicly visible docs for its API. First option to consider for auto-generated docs is Jazzy. Generated docs could be published with GitHub Pages.

I think the woff prefix should be this, not sure if it makes any difference:
data:application/x-font-woff;charset=utf-8;base64,

Thanks for this project, it's my new favourite website :)