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.

atproto-comments

Renders an AT Protocol (Bluesky) thread as a comment section. Supports SSR, sign-in, replies, and live updates.

rfc/content/RFC0005/index.md at 7a977ec6723ffe8cf10add493279b75fa62a5701 · oxa-dev/rfc

Request for Comments for the Open Exchange Architecture (OXA) project. - oxa-dev/rfc

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

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

ATF public comments analysis 2026-08

Comments are a basic web feature. So why aren’t they solved on ATProto yet?

Comments are about as old and basic as the social web gets, so I assumed ATProto would have them figured out. It doesn’t, not yet. Here is my take on why standard.site deferred comments on pu…

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.

Using Bluesky posts as blog comments

As a fast-follow to the blog post from earlier today on the benefits of an open network, here's a concrete example. Your blog's comment section can be pulled directly from Bluesky.