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:
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
for atproto devs and protocol watchers, I published an overview of the network moderation architecture.
it tries to cover all the mod actions possible for each service type. this design has been around a while, but not well documented.
this doc is not very polished, but could clarify some details
[AT Moderation Architecture | b...](
my positive vision for atproto is for people to have a greater degree of self-determination on the public social web.
baseline experience should be decent, but motivated folks should be able to organize and get more control over their online spaces and experience in line with their norms+values.
cooking on tooling for lexicon schemas: publishing, synchronizing, linting, checking evolution, etc.
still some rough edges, and need to show how codegen will hinge off this, but feedback welcome!
[tangled.org/@bnewbold.net/...](📃.md )
