Proposal for a staged RFC process · baby steps

rfcs/atproto/001-private-content.md at main · knasher/rfcs

Technical RFCs and design proposals for protocols and systems - knasher/rfcs

We need to talk about RFCs

I think the Rust RFC process needs serious reform. In this blog post, I'll explain why I think that, by covering some of the problems with the current process. Before I get all negative, I think RFCs are amazing! They've been a crucial part of Rust's open design and community-focussed

RFCs on the Atmosphere

I was recently working on an RFC for some open source work and didn't have a good place to post it. Google Docs is annoying for anything technical and a git repo is heavy if you don't already have one set up and a process ready to go.

Refining Rust's RFCs · Aaron Turon

At the heart of Rust’s open development is the RFC process. Every major change to the language, compiler, core libraries, tooling, and policy go through an RFC writeup and consensus-building process. The process served us incredibly well in clarifying our technical direction on the road to 1.0, and has continued to be highly active since then, with on average about 2 RFCs merged every week.

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

How to Read an RFC

Requests for Comments (RFCs) are how we specify many protocols on the Internet. These documents are alternatively treated as holy texts by developers who parse them for hidden meanings, then shunned as irrelevant because they can’t be understood. This often leads to frustration and – more significantly – interoperability and security issues. However, with some insight into how they’re constructed and published, it’s a bit easier to understand what you’re looking at.

#protocolsforpublishers #atproto #mcp #webapplets | Chad Kohalyk

Web publishing is facing its next challenge: a new iteration of centralizing platforms. BUT there is also a new wave of open protocols and standards that can help us gain our independence. Next month in NYC we are gathering a group of frontier technologists and popular web publishers to discuss how we can sail into this next platform shift as captains. #ProtocolsForPublishers Learn more and sign up here: https://pfp.unternet.co We will be hosting talks on #atproto #mcp #webapplets and web payments, and give publishers the opportunity to interact directly with developers working on these frontier technologies. Thank you to Unternet, Graze Social, Free our Feeds, and betaworks for their support.

Payments on Protocol - Nick's Blog

atprotofans.com was a proof of concept for payments on ATProtocol built at Graze Social. This post is about what we built, why proof of payment on protocol matters, and what it makes possible.

Why a New Protocol? The History and Future of AT Protocol - AT Protocol

Bluesky CTO Paul Frazee and Head of Protocol Daniel Holmgren join for a wide-ranging conversation about what atproto is, why it exists, how it got built, and where it's going next. From a Twitter consultancy to an IETF working group, this is where to get started.