Conversation

Notices

1. Embed this notice
   AntiComposite (anticomposite@wikis.world)'s status on Friday, 27-Dec-2024 12:44:25 JST AntiComposite

   • Simon Tatham

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

   https://datatracker.ietf.org/doc/html/rfc6919

   • clacke likes this.
   • Embed this notice
     Pink (can@haz.pink)'s status on Friday, 27-Dec-2024 12:44:53 JST Pink

     in reply to

     • Simon Tatham

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

     clacke likes this.
   • Embed this notice
     Wouter Verhelst (wouter@pleroma.debian.social)'s status on Friday, 27-Dec-2024 12:46:09 JST Wouter Verhelst

     in reply to

     • Pink
     • Simon Tatham
     @can
     What I've always liked about RFC6919 is that for *every* so called "key word" it "standardises" it provides an actual example from an actual non-humorous RFC which uses that exact phrase.
     
     Making fun of yourself the right way.
     @anticomposite @simontatham
     clacke likes this.
   • Embed this notice
     clacke (clacke@libranet.de)'s status on Friday, 27-Dec-2024 12:46:15 JST clacke

     in reply to

     • Wouter Verhelst
     • Pink
     • Simon Tatham

     @wouter I had only read the abstract, but thanks to your note I had to read the whole thing. It's brilliant.

     @anticomposite @simontatham @can

   • Embed this notice
     clacke (clacke@libranet.de)'s status on Friday, 27-Dec-2024 12:46:16 JST clacke

     in reply to

     • Wouter Verhelst
     • Pink
     • Simon Tatham

     My favorite reference:

     The phrase "MIGHT" conveys a requirement in an intentionally stealthy fashion, to facilitate product differentiation (cf. "COULD" above).

     For example: "In the case of audio and different "m" lines for different codecs, an implementation might decide to act as a mixer with the different incoming RTP sessions, which is the correct behavior."

     I just adore that passive aggressive "... which is the correct behavior" and would love to hear the anecdote for why the editor snuck that in there and how many chairs were thrown during the meeting.

     @anticomposite @wouter @can @simontatham

   • Embed this notice
     Wouter Verhelst (wouter@pleroma.debian.social)'s status on Saturday, 28-Dec-2024 21:37:32 JST Wouter Verhelst

     in reply to

     • clacke
     • Pink
     • Simon Tatham
     @clacke
     You're welcome 😉
     @simontatham @can @anticomposite
     clacke likes this.