Essentially. If the end user is being asked to make a financial outlay to get to the same things they did before, it’s unlikely that will go down well.

It should, certainly. But the original draft introducing the header had a typo, and now we’re all stuck with it.

Coffee may be an offence worthy of the Tower, but I hope my Services To Tea offer mitigating circumstances when my case is brought before the King Prince.

RST

My following list; of note is Lisa Melton, whose bio says “Follow me and I’ll fill your timeline with boosts”. She ain’t lying.

Looks like some of the talks from last year were released on the conference’s YouTube, so: hard to say if the recording will be available. I’ll (see if I can) remember to ask on the day.

I’m not the type to go hunting for the Best Bean, self-grinding to a particular size, pour-over…

The basic swill is plenty for me; my current choice is Kenco Instant.

Excellent. I’m on Stage 4 on the Thursday afternoon: “Brewing Tea Over The Internet”.

Should be fun times, see you there.

I haven’t been exploring in the depths of EFnet in …many years. I’m confined to the programming-related channels I found in the Way Back When, nowadays: at the moment, #c is probably the most active and it’s almost all old-timers.

As it turns out, no: HTCPCP isn’t a complete definition, so it never resulted in physical hardware. Except, of course, for the various teapots with chips inside that respond “418” but don’t actually do any brewing.

Did the predilection for tea give me away?

This is kinda the problem with widely deployed standards like TCP/IPv4: if you have even one device out there that’s on the “old” standard, it won’t be able to talk under a hypothetical new standard like IPv6 or TCP-with-huge-packets. And there are a lot more than one device out there that would be cut off.

As I understand it, the big pipes have very large MTUs now, and the edge routers cut up the packets for further transport. That’s probably the only way we can realistically go forward.

If anything, we’re into the “bust” part of the bubble: layoffs have been coming in waves all year, and are continuing. There were a whole bunch of posts over on Mastodon just a couple of weeks ago, at end of quarter, where people were laid off and looking for work.

Well, they could. They could also set up listening posts on every transcontinental pipe as they reach land.

What’s that, they did?

As it turns out, I drink black coffee nowadays.

I did go to a conference once where they were handing out laptop stickers, and in the pack was a 418 teapot.

Of course, a week after I stuck that to my machine, it died. Telling the laptop it was a teapot didn’t agree with it, I guess.

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.

So replicators are kind of a special case: they can make anything already fully prepared, without the need for a brewing command to be sent. It’s possible that by the 24th century, there’s a compatibility layer between Replicator Intermediate Language and HTCPCP, but I’ll leave that to future generations to establish.

Out.

Can’t stand pineapple at the best of times, on pizza is another level of wrong.

The RFC Editor’s site states that there’s an independent submissions track for “real” RFCs, whereby lay members of the public can write Internet-Drafts and then submit them into the review process.

Looks like there’s a good resource on how to write Internet-Drafts over at the IETF Authors site which may be worth perusing.