Hacker News Reader

I was struck by the reference to RFC 2119

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

http://tools.ietf.org/html/rfc2119

I guess there really does need to be a standards specification for everything

Of course. Standards, of all things, should be written in a standard way.

And the standard way in which they're written should also be expressed in a standard way.

A way to get conversations out of service "silos". Excellent.

Cue 50 comments on how this is an evil attempt by Google to make money and monopolize everything.

Ah, I thought it was like the Pigeon Protocol, or IPoAC.

Draft: The Salmon Protocol