Sebastian Messmer

Nvm, my mistake. I built the channel based on some type `T` while the signal expected `Option`. That broke it. Wondering if there's any type checking the library could do...

It seems `ServerSentEvents::new` only takes one event name and `Sse::new` only takes one `ServerSentEvents`. Is it even possible to create a stream sending multiple events? You mentioned it's inefficient but...

Leases are an option but would be pretty slow and would require a constant network connection to the master. I have been hoping to instead use a concurrency solution where...

What's the state on this? Has there been progress since it was put on hold half a year ago?

Or actually, `Base64UrlSafeData` might not even be the right type here. Concretely, it is currently used to store key data in COSEKey. Base64 is necessary for sending data to/from the...

Ok it's not only in the key, but also in the credential id object. I get that credential id sometimes needs to be encoded as base64 (e.g. when sent to...

Yes, I agree that when sending things to the client, serializing as json and wrapping things in base64 makes sense. It does introduce a lot of overhead though if you...

We're using `danger-credential-internals` already for what I mentioned above, but it only gives access to the passkey internals, not to the internals of PasskeyAuthentication or PasskeyRegistration. Let me check what...

> `Base64UrlSafeData` is essentially a _serialiser annotation_, and does not accurately describe its in-memory data format. It's still essentially a `Vec`, and you're not wasting much (or possibly any) memory...

Hm another potential approach could be [this](https://github.com/serde-rs/serde/issues/790). We could use `Serializer::is_human_readable` so that it serializes using base64 to json but binary to bincode.