> Sure, you could use some kind of external service that parses the underlying data, but what user is going to use that? I already do this for Twitter, given i

> Sure, you could use some kind of external service that parses the underlying data, but what user is going to use that? I already do this for Twitter, given it fucks up Discord embedding, and also use a similar tool for Bluesky, called psky. All you have to do is turn the "b" in "bsky" upside down, and change it to "psky". Not hard to use. I've heard some Bluesky clients also give out "share" URLs that are world-readable. That said I agree that posts should just be public (and my understanding is that the current state is temporary).