This post looks more closely at Brittany Ellich's work on representing groups in ATProtocol. It builds on earlier conversations and explores how these ideas might work in practice.
The hot topic of the moment is how to brand the neutral ATProto account in a way that it understandable for non-technical users. Stil another idea: the ".social account"
Part 4 of our "Building Recurring Payments in Public" series where we talk about being "locked open" and what it means to be a participant in the communities we support.
Part 3 of our "Building Recurring Payments in Public" series where we give describe real-world scenarios based on our behaviors, constraints, and definitions.
The Rules of Recurring Payments: Every Constraint Has a Story
Part 2 of our "Building Recurring Payments in Public" series where we give some context the behaviors, constraints, and definitions of recurring payments.