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
video and image uploads might be borked for a bit ๐Ÿ˜ฅ
messing around with a lexicon web catalog: [lexidex.bsky.dev]( ) consumes from the firehose, or can load from local disk. not very hardened or complete yet
(a couple months from now) woke is back baby
turning a big dial taht says "Hitler" on it and constantly looking back at the audience for approval like a contestant on the price is right
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: View quoted note โ†’
take care of yourselves, and each other
please don't use the bsky "search" endpoints as a generic API or for automation. it is not designed for that, is an expensive waste/abuse of resources, and we will block by IP or user agent. searches should come from direct human queries in the moment
@Laurens has his work cut out this week!