my consensus is that i will just follow whatever the reference lex-cli is doing when it generates a type interface

i wonder if going all in on zod-like validation would be good even if it results in a potentially awful typescript declarations

me typing twitter.com then immediately navigating to another website after a subsecond realization that i no longer have a twitter account

discord moment

JSON schema for AT Protocol lexicon documents [gist.github.com/mary-ext/6e428…](

Gist

JSON schema for AT Protocol lexicon documents

JSON schema for AT Protocol lexicon documents. GitHub Gist: instantly share code, notes, and snippets.

) [JSON schema for AT Protocol le...](

Gist

JSON schema for AT Protocol lexicon documents

JSON schema for AT Protocol lexicon documents. GitHub Gist: instantly share code, notes, and snippets.

)

there should be a way for js codegen to reorder my declarations so i dont have to

funny hackfix https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreidfml37ghwg7zvjhlmmj2gwf6bw63jtkwliqr64veswemx6of7vwq

more PDS coming online today https://porcini.us-east.host.bsky.network/xrpc/com.atproto.sync.getBlob?did=did:plc:ia76kvnndjutgedggx2ibrem&cid=bafkreiha2zl2g2x6huloywm3yeoikrgsrpl2p236hsydduajcixbn4eavy

i cba to dig up my past posts but i still think putting lexicon definitions into records is way too much effort for little benefit vs. just having a well-known/atproto-lexicon http route

youtube shorts not having the option to watch later makes it so you *have* to watch it else it gets swept away by recommendations