devs building on #atproto and working with lexicons! we have a new blog post up about interop and a recent accident with the 'pinnedPost' field being used by independent clients. also hints some tooling updates for the lexicon system overall - ThreadSky

bnewbold.net • 223 days ago

devs building on #atproto and working with lexicons!

we have a new blog post up about interop and a recent accident with the 'pinnedPost' field being used by independent clients.

also hints some tooling updates for the lexicon system overall

Comments

goeo.lol•223 days ago

soon every post will be 20 records?

maxouwell.bsky.social•223 days ago

All of them a variant of pinnedPost

natanael.bsky.social•223 days ago

Enough records to open a record shop

michelbestaat.thereforeiam.eu•223 days ago

Cool to see recommendations for extending the protocol. If there is a need to add a field to an existing record, I would make using NSID for the field name a strong recommendation to avoid name conflicts.

bnewbold.net•223 days ago

also mentions some of the cool collaborative app interop being done between @mimonelu.net, @tokimeki.blue, @hagoromo.relog.tech, @whtwnd.com, and @mkizka.dev

nyxxwolf.bsky.social•212 days ago

What about updates on how to implement private blocks?

https://github.com/bluesky-social/atproto/discussions/1131

It's been a while since any activity has showed up, has this been discussed recently?

serendipidude.bsky.social•223 days ago

I'd love to know why atproto needed its own lexicon to be invented.
Like, what was it with existing lexicons that didn't work well enough that a bespoke lexicon was created?

So far, all I can find is mansplaining of what a lexicon is.
(we used to call them data dictionaries, before they got cool)

timburga.com•223 days ago

serendipidude.bsky.social•223 days ago

This is the one I've read.
It mansplains lexicons but doesn't really go into why a bespoke one was thought necessary. Like specific use cases for its novel features.

Something I've done a lot of work with over the years. Really curious as to what the motivation was. It's the kind of thing I'd do.

timburga.com•223 days ago

Paul created it so only he can authoritatively answer, but speaking to your data dictionary comparison, lexicons define not just the data structure but also the operations you can request and actions you can take

bnewbold.net•223 days ago

I'm not sure I really understand the question, but JSON schema is the closest thing.

IIRC a key missing feature is "open unions" to allow for evolution and extension of schemas. these are basically "enums" allowing one of multiple types, but are forwards-compatible

bnewbold.net•223 days ago

protobuf (and thrift, avro, etc) are similar, and encode evolution/compatibility stuff more strongly than OpenAPI or JSON schema.

atproto includes binary content-addressable data records which can't be upgraded, so forwards/backwards compatibility and evolution are very important

Comments

Posting Rules

Reply