AT service operators and moderation thinkers: I put together an early proposal around infra abuse notices across organizational boundaries. really looking for feedback on this one, it is bait for counter-proposals and references to prior work! [github.com/bluesky-social...](📃.md )
check out [@stechlab-labels.bsky.social]( )
put out a new 'goat' release (v0.1.2) with basic support for PDS administration ('goat pds admin ...'). if you run it from a PDS instance it should find admin auth info automatically. hope to have this replace the 'pdsadmin' shell script over time
there is an AWS incident happening in us-east-1: [health.aws.amazon.com/health/status](https://health.aws.amazon.com/health/status ) Bluesky has been mostly unaffected so far, but automated emails may be impacted, including communication of moderation actions
CTO: So are we clean on OPSEC? Backend: Sure are boss, real fuckin sexy for #FCF, just like you asked. CTO: what
as a reminder: bluesky (the app) has a broad set of user interactions controls. beyond blocking and block lists, we have features to control who can reply, mention, and quote-post accounts RE: View quoted note →
wrote up a little thing [AT Namespaces for Community Sp...]( )
endorse! RE: View quoted note →
a great way to break up bsky appview implementation work would be implementing "Following" as a regular feedgen. one of the harder pieces in general high-req-rate full-network scale, but a bunch of ez optimizations: only recent posts, limit following count, only subset of network, etc
standards folks! if you are in to this sort of thing, we now have an IETF mailing list to discuss AT protocol bits. [mailman3.ietf.org/mailman3/lis...](https://mailman3.ietf.org/mailman3/lists/atp.ietf.org/ ) if you want to jump in, I recommend setting up an overall IETF datatracker account and reviewing IETF IP policies ("note well") first