Aurelia Molzer

Sorry for not updating this explicitly, `async` is possible since `0.5.0` and there are [utility bindings](https://docs.rs/oxide-auth-async/0.1.0/oxide_auth_async/) based on `async-trait` for it as well.

Since JWT is suboptimal from many security standpoints, I might consider supporting [Paseto](https://github.com/instructure/paseto) instead. Other considerations involve [macaroons](http://theory.stanford.edu/~ataly/Papers/macaroons.pdf). Informal comment: Supporting a standard that does mac then encrypt while still...

You can do this with your own `Issuer` implementation but I probably won't support it in the main crate, and it isn't at the moment.

> EDIT: Or maybe just put the JWT token in its String representation in the token field? Precisely. It needs to be a string representation since that is what the...

There's a conceptual problem, I think: By design a library defines a single entry, which is a function that reveals its root module definition by _loading_ and _executing_ the libraries...

Of particular note might now be the [`generativity`](https://docs.rs/generativity/latest/generativity/) crate, which neatly abstracts creation of a brand into a _macro_ such that it no longer requires closures / scopes. Also it...

The offending chunk seems to be chunk 4 (rows 36-44). [chunk-4.tar.gz](https://github.com/image-rs/image-tiff/files/10057399/chunk-4.tar.gz). That seems to be invalid when running it though both `weezl` and `salzweg` using the tiff size switch and...

Sounds good with regards to maturity. There's some API details for implementation: * multithreading, we need to _not_ spawn threads on wasm targets for instance. Maybe switch to not-`zune-jpeg` on...

The concern isn't so much multiple images in a single reader, but that buffering all the available data beyond the image presents a change in semantics that has somewhat unknown...

Simple plan for `png`: A reader that _only_ checks the chunking until EOF to create an in-memory buffer of the whole file. Should be doable.