Asklemmy

Excellent. I'm on Stage 4 on the Thursday afternoon: "Brewing Tea Over The Internet".

Should be fun times, see you there.

Wasn't there a new HTTP action recently proposed for "This is a JSON RPC request that we've convinced ourselves is actually REST and we've been using POST and someone finally pointed out that that was stupid"?

Not a new status code but still vaguely amusing.

I quite like the idea of HTTP 256 Binary Data Follows, which is just 200 OK but you asked for a non-text content type file.

That's a tough one: most standards are codified as such because they're already seeing wide use. The major example of one that's been worked the other way around is IPv6: it's been a standard for a very long time, and still doesn't seem to be seeing adoption.

Of course, I wouldn't say I was bullish on IPv6. 32 bits is enough for anyone, right.

I enjoy that the original draft for the Referer header spelled it wrong, and now we're all stuck with the typo forever...

For "real" RFCs that aren't Apr 1st jokes, there's an independent submissions track for the public to write Internet-Drafts and then submit them into the review process.

With the joke RFCs, they get emailed straight to the editor at least two weeks beforehand. I'm not privy to the selection meeting, but I expect it's fun.

I never understood the beef people had with that. The Internet is a series of tubes, of various widths and sizes, with inputs at random points in the stream.

Plumbing analogies are apt.

Yes, unless Jen needs to borrow it for a presentation.

I need one too and I'm a stupid Gen Y