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.
Part 2 of our "Building Recurring Payments in Public" series where we give some context the behaviors, constraints, and definitions of recurring payments.
Part 1 of our "Building Recurring Payments in Public" series where we give some context about what we're trying to do and why it matters.
We're hosting our first community call to connect with everyone building on, using, or curious about ATProtoFans. This is a chance to share what we've learned, hear your feedback, and explore what's next together.
Ever wanted to add ATProtocol authentication to your website and check if visitors support their favorite creators? In this tutorial, we'll walk through building a minimal single-page application that authenticates users via ATProtocol OAuth and validates their supporter status using the ATProtoFans API.
ATProtoFans introduces a novel approach to creator support by leveraging ATProtocol's decentralized architecture and cryptographic attestations. This article explores the technical foundations of the system, focusing on the three-way relationship between supporter records, supporter proofs, and broker proofs, and how developers can integrate these records into their own applications.
We're excited to announce that ATProtoFans is now live and open for everyone to try.