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
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
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.
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.
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.
Proposal for a staged RFC process · baby steps
This blog is where I post up various half-baked ideas that I have.
Inspired by @danielroe.dev I added comments functionality to my portfolio using barebones AT Protocol query. Definitely not necessary, but amazing that it's even possible 😅
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
P(aul) 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…
