Benjamin Saunders

Are we sure this is a good idea? Serialization can already be performed by manually traversing the world. Built-in serialization will be a subtle compatibility hazard when users attempt to...

> put them into another struct to keep things organised and then serialize that struct That's not necessary (though it may be relatively convenient); you can write serde (de)serialization code...

The [typetag](https://crates.io/crates/typetag) crate may be of interest for (de)serializing trait objects.

HDR metadata support would go nicely with this!

My interest is for using the `ravif` library to encode HDR data I generate myself; I don't know if it's relevant to transcoding from LDR using the command line tool,...

Is that something you consider in-scope, @kornelski?

HDR metadata is standardized and absolutely necessary, because it informs the ultimate display device of how to most effectively tonemap, avoiding unnecessary quality loss in common cases. I'm all in...

Is the somewhat dangerous `affected_users` field really necessary? It seems like the main objective here is to allow clients to flag messages that were not delivered by a bridge, and...

I agree that it's useful to be able to tell which users in a room are there via a bridge. It might make more sense for that to be handled...

> Just wanted to note that this is slightly ambiguous as there might be more than one IRC bridge in a room. A more formal/structured scheme for mapping users to...