Samuel
@samuel.fm
it’s not. can you guess the trick?
2 4Double 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.
1 2nope, it’s simpler than that
2 3I'm guessing some sort of edit? I just have no idea where the new post is
2 2seems like bluesky only shows the initial version in post form, but its search uses the latest version
1 5bingo!
2 5very funny that the other appviews allow edits yet don't show any UI to indicate it in their clients
2 3 6that 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
2 5So wait, when I edit a post on Mu does it still show the original text on bsky dot app?
1 1no. 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
1 4So far it only seems to exist inside the Bluesky AppView?
1 2looks like the other appviews are coded to use the latest version of a post, while Bluesky does not
1 3Okay. Then this is a showcase how the Bluesky AppView handles (or better ignores) changed content.
The Bluesky AppView is known to cache records and store the first version it sees, ignoring later versions/changes.
Other AppViews show the latest version from the network/PDS.
1 2yeah lol witchsky.app/profile/xan....
very funny that the other appviews allow edits yet don't show any UI to indicate it in their clients
idk, seems to be special only with bluesky's appview
1 2context hat for ppl not using threaded replies: witchsky.app/profile/xan....
very funny that the other appviews allow edits yet don't show any UI to indicate it in their clients