Email or username:

Password:

Forgot your password?
Simon Tatham

The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED BUT REPULSIVE", "WRONG BUT WROMANTIC", "FREQUENTLY MISUNDERSTOOD", "NOBODY BOTHERS WITH THIS BIT", "SHOULDN'T REALLY BUT WE WON'T JUDGE", "REQUIRED IN ORDER TO WORK AROUND EVERYONE ELSE'S BUGS", "YOU DO YOU", and "OBVIOUSLY ABSURD BUT VERY COMMON FOR SOME REASON" in this document are to be interpreted as described in RFC 2119.

23 comments
Dan Sugalski

@simontatham Plus the ever popular "WE DON'T KNOW WHAT WE WERE THINKING, IT WAS 3AM WE WERE EXTREMELY DRUNK AND THERE WAS ALSO A DONKEY WHICH WE SHALL NEVER SPEAK OF AGAIN"

Simon Tatham

@wordshaper a certain piece of software I regularly use, which shall remain nameless unless anyone else in this thread recognises it, currently has the official version number "wtf 11pm pub"

PulkoMandy

@wordshaper @simontatham
Wasn't it a mouse?

"Mouse now present. 6.502 members represented.

[149-A94] Action Item for Landlord: Capture and exile the mouse that just fell out of the light fixture."

unicode.org/L2/L2016/16325.htm

Dan Sugalski

@pulkomandy @simontatham No, no, not the mouse. We still speak of the mouse. (I have heard the mouse is up for chairing the next round of the unicode committee but I dunno what its chances realistically are)

Jyrgen N

@simontatham Nice. But damn, it doesn't fit into four lines.

Saphire Lattice

@simontatham my first thought is about Mastodon and Matrix

julian

Re: The key words "MUST", "MUST NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED BUT REPULSIVE", "WRONG BUT WROMANTIC", "FREQUENTLY MISUNDERSTOOD", "NOBODY BOTHERS WITH THIS BIT", "SHOULDN'T REALLY BUT WE WON'T JUDGE", "REQUIRED IN ORDER TO WORK AROUND EVERYONE ...

@trwnh@mastodon.social :sob:

AntiComposite

@simontatham The key words "MUST (BUT WE KNOW YOU WON'T)", "SHOULD CONSIDER", "REALLY SHOULD NOT", "OUGHT TO", "WOULD PROBABLY", "MAY WISH TO", "COULD", "POSSIBLE", and "MIGHT" in this document are to be interpreted as described in RFC 6919.

datatracker.ietf.org/doc/html/

Pink

@anticomposite @simontatham tfw the IETF thought of your shitpost even before you did.

Simon Tatham

@can @anticomposite shitpost it may have been, but it's been a pretty popular one so far. Guess nobody else had seen RFC 6919 either!

Pink

@simontatham @anticomposite definitely funny! The fact that there's an actual RFC for it makes it even funnier imo

rfnix

But is it normative standard, non-normative standard, a request for comments or recommendation? 😅

Jack

@simontatham just now realising those instructions explain how to interpret "must", "should", etc but not "are to" :) :) :)

Simon Tatham

@jackv even the IETF is subject to Hume's law.

Tor Lillqvist

@simontatham Sir, I hereby declare you have been selected as the winner of the Internet today.

amyipdev

@simontatham@hachyderm.io the lack of these terms in RFC 2119 should be submitted as an erratum (to RFC 2119)

ciara
@simontatham a terry davis like temple os word/phrase generator list of words
Go Up