I'm pondering an interesting challenge with #ActivityPub. Most servers send Activity messages using actor as the originator and Note objects with attributedTo as the creator. Some use actor on Notes and some use attributedTo on Activities.

I configured deserialization aliases on my structs in #Rust to accommodate that. But now I see that a few servers (well, one so far) set both properties on Activities, which breaks the deserializer (since the unused one gets renamed to what I need and then I have a duplicate). So now I'm weighing whether to add both separately, to try writing a custom deserialization implementation, or to just write off federation with this server.

I'll probably try writing a custom implementation first.