How to Make #Architecture Decisions: #RFCs, #ADRs, and Getting Everyone Aligned
How to Make #Architecture Decisions: #RFCs, #ADRs, and Getting Everyone Aligned
Think about it for a second: could the internet exist without standards and protocols? Of course not! Computers need shared rules and agreements to communicate with one another. Even human languages, like English, work much the same way. They function as a kind of communication protocol because we’ve all agreed on words and grammar that carry shared meaning. In both cases, whether among machines or people, communication depends on common understanding.
What Are RFCs? The Forgotten Blueprints of the Internet
https://ackreq.github.io/posts/what-are-rfcs/
#HackerNews #RFCs #Internet #History #TechDocumentation #OnlineStandards #WebDevelopment
Think about it for a second: could the internet exist without standards and protocols? Of course not! Computers need shared rules and agreements to communicate with one another. Even human languages, like English, work much the same way. They function as a kind of communication protocol because we’ve all agreed on words and grammar that carry shared meaning. In both cases, whether among machines or people, communication depends on common understanding.
Today I (re-)learned about the “418 I’m a Teapot” [1] error code, which was first codified in the April’s fools issue of Internet request for comments for 1998. RFC2324 [2] describes the Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0), and has 418 as that particular error code.
I think it might be useful, as part of the combined measures against unauthorized AI scraping, to start returning that HTTP 418 I’m a teapot error… or even mess with them with different ludicrous non-coffee things to be, such as a mate bowl, or I’m a spaceship…
After all, that’s what Internet of Things shitposting should be about, right?
/ht @osma
[1]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/418
[2]: https://www.rfc-editor.org/rfc/rfc2324
#TIL #TodayILearned #RFCs #AprilFools #AprilFoolsRFCs #HyperTextCoffeePotControlProtocol #HTCPCP

The HTTP 418 I'm a teapot status response code indicates that the server refuses to brew coffee because it is, permanently, a teapot. A combined coffee/tea pot that is temporarily out of coffee should instead return 503. This error is a reference to Hyper Text Coffee Pot Control Protocol defined in April Fools' jokes in 1998 and 2014.
This specification defines the Sunset HTTP response header field, which indicates that a URI is likely to become unresponsive at a specified point in the future. It also defines a sunset link relation type that allows linking to resources providing information about an upcoming resource or service sunset.