Double post, no delete?
Different records served to different relays/appviews? (only the bluesky appview shows the emoji that I can see)
Some of the likes on your post have different CIDs too.
that relies on a dumb text-only addition to posts. posts made anywhere else will not show that an edit occurred because the app server does not surface such info
no. mu is actually deleting the original post and creating a new one with the same TID, but it breaks metrics and a majority of users are left confused
So when the Bluesky appview sees the new post with the same TID it replaces the old one?
Since it has the same TID, how does it break the metrics – is that an appview implementation detail? Presumably the "like" etc records still exist on the liker's PDS referencing that TID?
they still reference the same post/its TID, but since the CID (hash) of the updated post differs, Bluesky's appview doesn't trust it anymore, and the app will only show things like reply counts of posts that mention the new post CID
I opted to include a different but also hacky solution in my client witchsky.app, where people can redraft posts (where the old one gets deleted like on mastodon), mainly meant for immediately after creating the post. that uses a fully different TID so no issues occur, but it's connections are gone
ok one (1) issue can occur. in threads where Bluesky would normally show a thread indicator count, a redrafted post will lose its counter. this may be because the post is replaced very quickly? I'm unsure