And of course, the moment Bluesky decides to change their API a little this integration will break.
So what was the point? If you are not going to have stuff as stable and stupidly hard to change as web api, then why pretend you have interop?
Discussion
You can't make breaking changes to an ATproto lexicon, that requires a new lexicon. The point about it being a lexicon is that it's not actually a javascript embed (ok calling it an embed type before is the wrong word). You're writing the comment to the PDS in a way that means the comment will be picked up in the additional site(s) where you want it to be picked up, and there's benefit there (versus something like Facebook comments)
Lol... i literally saw Bluesky making breaking changes to their API before... not sure what magic do you think Json schemas have to prevent breaking updates.
Man, people really buy these claims!
Give me one recent example of BlueSky making a breaking change to:
app.bsky.feed.post
app.bsky.actor.profile
or any other core lexicon (before the very early days way back).
If you can post the before and after, and it's not two different lexicons, then I'll owe a nice dinner next time you come to Vietnam.
The reason they can't is the domain is just used for publishing at first and for publishing non-breaking changes, after that it propagates. I think maybe you're mixing up the API and the lexicon system.
Wow... not sure what to tell you man. OK, I believe you, Bluesky now are physically incapable of updating the schemas they use because the older one propagated.
Honestly, I don't hate that people trust each other that much, good for everyone.
Of course they can publish whatever update they want, but if it's a breaking change nobody adheres to it. Even if it's a non-breaking change nobody has to adhere to it. What they publish after the fact is not some kind of new source of truth. Apps adhere to what they have *in hand* from whatever point in time. I think you're seeing it like it's some kind of pub/sub deal, but that's not how it works.