1025: The Open Web's second chance (w/ Dan Abramov)

The AT Protocol (ATProto) is a decentralized data layer for the web that enables user-owned data storage and control, addressing issues like data loss, walled gardens, and lack of interoperability in centralized platforms. Users store their data in personal folders - essentially repositories for JSON records - hosted either by themselves or third-party providers, with apps acting as consumers and creators of this data rather than its owners. This architecture allows users to switch apps or hosting providers without losing content, ensuring continuity and portability across services.

The protocol supports a wide range of applications beyond social media, including blogging, forums, code hosting, and music tracking (e.g., Teal FM), all built on a shared, open infrastructure. It uses flexible schema definitions called lexicons, which allow developers to define custom data types while enabling interoperability when desired. Data is publicly accessible by default, with event streaming via WebSockets allowing apps to sync and display content. The system draws comparisons to RSS and Git, emphasizing decentralized ownership, algorithmic flexibility, and community-driven standardization, while avoiding the rigidity of fully centralized platforms or blockchain-based systems.

• What if you built a decentralized blogging platform using AT Protocol as a solo developer?

  • Move: Use the AT Protocol's lexicon system to define a standardized blog post schema (title, content, tags, timestamp) and publish it on GitHub. Build a minimal Next.js app that reads and writes to user repositories via the AT Protocol API, enabling users to own their content.
  • Why Now?: With growing interest in user-owned data and tools like Hubble enabling public data access, now is the time to capture early adopters disillusioned with platform lock-in (e.g., Medium, Substack).
  • Expected Upside: Position yourself as a foundational player in a decentralized content ecosystem - monetize via premium hosting referrals or Pro features (analytics, custom domains), while benefiting from network effects as other apps adopt your lexicon.

• What if you created a niche analytics tool for trending AT Protocol data types?

  • Move: Build a real-time dashboard (using Vercel + Next.js) that scrapes public AT Protocol events via WebSocket streams, identifies emerging lexicons (e.g., "Anisota Progress", "Puzzmo Streak"), and surfaces usage trends - similar to UFOs but focused on developer adoption.
  • Why Now?: The ecosystem lacks accessible tooling for tracking grassroots standardization; with Dan Abramov and Vercel involved, developer attention is increasing.
  • Expected Upside: Attract indie hackers and early-stage builders looking for the next big use case - monetize through sponsorships, API access tiers, or integration partnerships with app developers.

• What if you launched a cross-app social reader for Standard Site-compatible blogs?

  • Move: Develop a feed aggregator that ingests blog posts from AT Protocol users publishing in the Standard Site format (used by Leaflet, Offprint). Add algorithmic ranking ("For You" feed), search, and offline sync using client-side caching, all powered by public data from personal data servers.
  • Why Now?: Apps like Standard Reader are emerging but remain sparse - there's an opening for a polished, AI-enhanced experience that leverages the protocol's public-by-default data model.
  • Expected Upside: Capture a loyal audience of knowledge workers and creators seeking an RSS successor with modern UX - differentiate via personalization and network effects, then offer paid sync or AI summarization features.

• Set up a personal data repository using AT Protocol to own and control your application data, enabling portability and interoperability across apps.
• Design your app as a consumer of user-owned data by building against standardized JSON schemas (lexicons), allowing seamless integration with decentralized user repositories.
• Implement event streaming via WebSockets to ingest and react to real-time data changes from user hosts, reducing reliance on centralized APIs.
• Adopt or contribute to shared lexicons for common data types (e.g., blog posts, follows) to enable cross-app compatibility and grow ecosystem adoption around your tooling.
• Generate type-safe frontend and backend code automatically from lexicon definitions using JSON-based schema tooling to improve development speed and reduce errors.