GitHub - joho/7XX-rfc: An RFC for a new series of HTTP status codes covering developer fouls.

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

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

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.

ATProtocol Attestations: Cryptographic Signatures for the Decentralized Web - Nick's Blog

This post introduces the formal ATProtocol attestation specification, a framework for adding cryptographic signatures to ATProto records through two complementary patterns: inline attestations that embed signatures directly in records, and remote attestations that store proof in separate repository records. The specification prevents replay attacks through repository binding, uses CID-based content addressing for integrity, and provides the cryptographic foundation for verified credentials, trusted content, and authenticated interactions in the decentralized ATProtocol ecosystem.

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.

/beaver/patches/components/net/protocols/atproto at main · me.webbeef.org/beaver

Rewild Your Web

On forking the Web

This document contains a set of informal notes on how to build an alternative specification to the Web, in such a way that hopefully prevents many of its drawbacks while still preserves many of the good points. This document is not an specification, and is therefore subject to change over time.

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

RFC - Request for comments

#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.

Anubis: Web AI Firewall Utility | Anubis

Weigh the soul of incoming HTTP requests to protect your website!

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.

Introducing WEBCAT: Web-based Code Assurance and Transparency

In this post, we introduce Web-based Code Assurance and Transparency, a project that supports verifiable in-browser code for single-page browser applications. Along with this post, we are publishing the WEBCAT project repository; follow-up posts will provide more detailed information.