# 02-liaizon

[//]: # (like-of: https://social.wake.st/@liaizon/116241670633671828)
[//]: # (reply-to: https://social.wake.st/@liaizon/116241670633671828)

Sorry for the spam from my clones 🙂

There were some inconsistencies between my cached AP state and that of the federated instances (and having likes with unique filenames also makes things a bit confusing actually).

But I honestly hoped that Mastodon was smart enough to aggregate reaction events coming from the same actor and targeting the same resource...

On the other hand however I also implemented my own versioning/conflict avoidance mechanism (which basically adds a `?v=<timestamp>` to a published URL if it matches the name of a file already indexed in the state, as a way to bypass Mastodon's tombstone logic if a file is deleted and then re-created with the same name). And I have a hunch that that may have messed up Mastodon's own object resolution logic.

I'm realizing that having files and filenames to associate to URLs adds another layer of complexity/impedance that has many corner cases to be handled.