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.
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
RFC - Request for comments
rfcs/atproto/001-private-content.md at main · knasher/rfcs
Technical RFCs and design proposals for protocols and systems - knasher/rfcs
rfc/content/RFC0005/index.md at 7a977ec6723ffe8cf10add493279b75fa62a5701 · oxa-dev/rfc
Request for Comments for the Open Exchange Architecture (OXA) project. - oxa-dev/rfc
atproto-comments
Renders an AT Protocol (Bluesky) thread as a comment section. Supports SSR, sign-in, replies, and live updates.
Protocol Reader - Summer of Protocols
The Protocol Reader The Protocol Reader is an 358-page book (currently only available as an epub) comprising 26 foundational essays by 31 authors from the Summer of Protocols program, carefully edited and sequenced to introduce you to the fascinating new discipline of Protocol Studies. It can serve as
HTTP Semantics
The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypertext information systems. This document describes the overall architecture of HTTP, establishes common terminology, and defines aspects of the protocol that are shared by all versions. In this definition are core protocol elements, extensibility mechanisms, and the "http" and "https" Uniform Resource Identifier (URI) schemes. This document updates RFC 3864 and obsoletes RFCs 2818, 7231, 7232, 7233, 7235, 7538, 7615, 7694, and portions of 7230.
CBOR — Concise Binary Object Representation | Specification
CBOR is specified in an Internet Standard RFC. RFCs that serve as Internet Standards are generated by the IETF based on an extensive technical review and quality control process. These are meant to last.
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.
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…
Understanding AT Protocol
I’ve been playing around with AT Protocol. The posts on this site are now published to standard.site, and I’ve written a (very basic) WordPress plugin to display posts from my PDS on the Now page of this site.
Protocol Buffers
Protocol Buffers are language-neutral, platform-neutral extensible mechanisms for serializing structured data.
Paul's article prompted a long one from me: What is the purpose of protocols? connectedplaces.online/the-purpose-of-protocols/
The Purpose of Protocols
connectedplaces.online
Paul Frazee
New blogpost about atproto It's not federation, it's not a p2p mesh. It's a secret third thing: practical. pfrazee.com/blog/practical-decentralizati…
