we are finally going to fully nuke the `#handle', '#tombstone', and '#migrate' events from the firehose.
these have been deprecated in favor of '#identity' and '#account' for a long time now
๐ท๏ธ devs and mod service operators! ๐ท๏ธ
got a proposal up about moderation report routing.
this is basically a small update to let moderation services ("labelers") declare what kind of reports they are willing to receive.
implementation on this is under way and we hope to ship it soon
[proposals/0007-mod-report-rout...](
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