Issac Kelly

I'd like for this to be an option for config.

I was wrong. I can use `#[schema(as=Foo)]` and then use `Foo` in my request_body and response(body) declarations, and then point to `FooUtoipa` in my `#[openapi(components())` declaration. So this lets me...

Very neat. I was unaware that somebody had reversed groups. I'll take a look at it next time I get a chance.

Unauthorized user is interesting. I haven't seen that before. Potentially newer firmware is more strict on possible usernames. I made that up before there was an official API. The newest...

Yeah. Username is a misnomer, it's more like a unique User Agent, or a client name. This is why in my original version i based it on the fqdn.

This will definitely need to be changed, yes. I don't really do much active maintenance, since up until this newest release things worked pretty well for me. Thanks for checking...

That's exactly how we (I work with OP) use `-E` We are back to touching this part of our code so I was looking at this recently. If I get...

Occasionally, if i make a few dozen changes to my document... this branch is called: https://github.com/automerge/spanreed/commit/84ad6cf54c667f17d976c837f95e22fb98d3986b#diff-05a5db13701065ba8c66d1545cd83b1ba2b610cd217f6ecf94b6fda757864f28R183-R186 I haven't yet identified why.

In repo.rs compaction is an optional step that occurs _at time of save_. and in fs_store.rs compaction is a step that happens _independent of what is going on_. I think...

This one doesn't address #52 in any meaningful way, we should extract that out of the issackelly:compaction branch. The character length issue is something like ::str::hex::str::hex::random_128_uint which is getting expected...