probably need to write tutorial on how to publish Lexicons with the new lex resolution stuff. here is the short version!
say you have new lexicon record type with NSID 'dev.example.drink.tea', and you control the 'example.dev' domain name
🛠️ atproto devs! 🛠️
got a new proposal out about Sync 1.1, aka inductive firehose, aka cheap validating relays.
it is a long, low-level doc. doesn't directly impact folks unless they emit a firehose (eg, PDS and other repo hosts), or are doing full validation as a consumer
[proposals/0006-sync-iteration ...](
have said it before and will say it again:
Bluesky Chat/DMs are not E2EE. don't put anything sensitive in there you wouldn't want rando law enforcement to pore over.
use it to exchange Signal contact info. consider "disappearing messages". do it by habit, get your friends+fam to also.
working on improvements to mod report routing: letting ozone instances declare types of reports they will review.
currently looking at having a more granular set of report types, but still a fixed/global set in the app. might allow custom report types in the future
really solid overview of atproto Lexicon system, and the soft-power dynamics around them. I will link folks to this!
a couple additional points in 🧵
RE:
