by Darius Kazemi, April 3 2019
The technical content
This RFC points out an ambiguity in RFC-66 and RFC-80. There is a control message sent during the initial connection “defined as 'exactly an even 32 bit number'”. It's unclear what the message type code for this message is supposed to be. This is kind of amusing because there is only one message type code currently defined (code zero), but they want things to be as clear as possible in case further message type codes are defined in the future. They suggest amending the intitial connection protocol to specify that it is, indeed, code zero.
How to follow this blog
You can subscribe to this blog's RSS feed or if you're on a federated ActivityPub social network like Mastodon or Pleroma you can search for the user “@email@example.com” and follow it there.