Anyway, the part here that really amuses me is that RFCs generally list the authors' employers... and so...
This is the first RFC that includes the words "DNA Lounge". Hah!
Anyway, the part here that really amuses me is that RFCs generally list the authors' employers... and so...
This is the first RFC that includes the words "DNA Lounge". Hah!
Grats! DNA mentioned in RFC!
I have to also assume that you are the first barkeeper listed in any RFC.
peace
I would fade that action, but have no proof.
...we just need a spec that specifies the captcha to solve before the server will return the email address.
But standardizing anything about captchas just makes them easier to break, oops.
recaptcha "337 jarnistan" - I'm starting to wonder what source material they're weaving these from.
I've been working on a utility called 2ping, which uses a UDP client and listener. This week (after about a month delay and some back-and-forth, not exactly unexpected), the IANA assigned 2ping a registered port in the master services list. So, I'm on a boat^H^H^H^H^H^H^H^H^H in an IANA document.
The protocol I wrote for 2ping is well defined and documented, though I doubt I'd get it to the RFC stage. Though if I did, I'd probably want to be listed as "Ryan Finnie, Human, 0.08% ABV".
Nice work! I particularly like the examples. The RFC2324 reference was also great.
I'm just glad the gorby%kremvax example is still in there.
Yeah, it's always nice to see the classics.
And I see that my former coworker from Jabber, Peter Saint-Andre (aka "St. Peter, the Patron Saint of Jabber^H^H^H^H^H^HXMPP") got a nice shout-out in the acknowledgements, too. Awesome!
Congratulations to DNA.
Excellent. I guess now we'll have to call it a Request For Clubbing.