Heath Stewart @heaths.dev · May 16

But there are no limits or obvious indications that someone edited their post via goat, pds.ls, etc. Not saying these aren’t good ideas, but about as secure as this gate. How would such a loophole be closed or, if useful functionality to retain, show indications of new CIDs in AppViews?

3 likes 2 replies

?

Replies

Trezy · May 16

Realistically, this is an AppView concern (based on the way atproto is designed today). I'm pretty confident this is just relevant to Bluesky as an AppView. Other AppViews have to make their own decisions on how to handle it.