Building for Organizers - The People Layer

"the most enduring social networks ... [are] the ones that empower organizers... coaches, teachers, volunteer coordinators, union stewards, event planners, health workers, running club hosts, activist organizers, and owners of community-based businesses ... making decisions on behalf of a group ... turn a collection of individuals into a functioning community" - online community managers, in other words.

Author examines two examples:

• Google Forms "gives organizers exactly what they need... designed for asymmetric complexity, making it dead simple to contribute, but giving organizers the tools to orchestrate"
• Facebook Groups "offer something crucial: tools that work for both organizers and members. Organizers get privacy settings and moderation controls. Members get a space to share content, ask questions, comment on each other's posts, and build conversations over time in a familiar interface"

So "organizers are pivot points for software adoption at scale" - they make choices for many more people - "Yet most social networks optimize their onboarding, features, and support for individual users".

Most people arent performing on social media, but they are using "social software: the person who hasn't tweeted in months is sending twenty messages a day in their youth soccer league chat coordinating game schedules... essential infrastructure, not optional entertainment".

So how could ATproto satisfy "the need to connect and coordinate without broadcasting to the entire internet"?

Bryan Newbold's "Community Spaces on AT Protocol," shows how DIDs and lists provide "a way to define a group and have those permissions travel across applications... a calendar app for workshop schedules, a messaging app for pitch collaboration, and a file-sharing tool for contract templates and rate sheets. Update the list once, permissions propagate everywhere".

This needs "Granular permissions... Private data... Interconnected apps" - and it needs builders to build for organisers.