Post

lexicon: { *: any }

Only if it's in a way that doesn't break the expectation of some other party, i.e. a new previously unknown field is fine, but "all profiles previously had a display name but now you can get accounts without a display name" can break some apps

Thank you!

Basically you can't change it in a way that either an old app version will be rejecting something that new version makes, or the other way around. (It's somewhat analogous to the soft fork / hard fork problem in crypto ;) except you can't really force either side to the other direction here)

maybe you could briefly mention something about (or link to) how the bluesky code "runs" lexicon schemas. As I understand it they are compiled into a large bunch of functions that run on both the server and client ends.

Could someone please explain this one: “It's a good idea to use open unions instead of refs. This enables extension or replacement in the future.”

🙌

Great stuff!

I think we'd need a book, online one works too, to make the concepts clear. 😉*nod, nod* 👤↕️

📌

clearly the schema doesnt control that

📌

i love nearly all of this but even the mention of optional separate social graphs makes my head hurt a little i just finished telling 200 people “and the coolest thing is that your friends list keeps working between apps”, imo it’s the atproto killer feature