The latest Mastodon quirk is the poll at the top of this thread. Mastodon polls aren't updating on our software any more. We rely on the 'updated' time to make sure we don't process two Update activities out of order. This is no longer updated. Instead the updated time is encoded as a Unix timestamp in a URL fragment of the activity id. Why would you do such a thing? We normally don't go parsing URLs to discover updated timestamps, and now we not only have to, we have to only do it for Mastodon polls. Apparently they've got some code that parses them and make sure that on Mastodon they always arrive in order. We have to create a whole new Mastodon specific function to make it work like before. And other projects will need to do the same if they don't want to have inaccurate poll results due to updates arriving out of order. Or you can say 'screw it' and check the updated timestamp like all good software should do, and have Mastodon polls that never update. And your users will blame you for not implementing ActivityPub correctly; and you actually did.
EEE means 'Embrace, Extend, Extinguish'.
