As I understand it, the prophecy is that when the state of Israel is fully unified once more, and the temple of Solomon is rebuilt, Jesus will return and the second battle of Armageddon will commence.
End of the world, rapture of the believers into Heaven, the whole bit.
Being realistic, it's not something I see gaining adoption, mostly because HTCPCP is a joke protocol and isn't a complete spec. Any internet-connected coffee machine nowadays would probably go through a ZigBee proxy or similar, and talk some proprietary format.
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.
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.
Did the predilection for tea give me away?
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.
For real though, the shortest license is probably the WTFPL:
Might've used it a couple of times myself.