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.
A tip one contractor passed on to me when caulking: use pieces of toilet paper to smooth it out after applying. You won't get your fingers gunked up, and toilet paper's cheap enough that you can use a bit to smooth off a few inches of caulk and throw the paper away.
Think I got through half a roll when sealing up a window frame a couple years back, looks great.
According to the Tolkien Professor (during his YouTube streams on the History of Middle Earth series) there was always the intent to publish the Quenta Silmarillion (the central tale of the Silmarils) as a First-Age story of the Elves, but it kept getting revised and rewritten and never reached a publishable form.
Until Tolkien's son wanted to complete that piece of the legacy, and found multiple (sometimes contradictory) sets of notes and mostly-finished stories, and Editorial Decisions had to be made.
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.
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.
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.
The biggest problem IPv6 has is that IPv4 has been so hugely successful: gargantuan resources have been poured into getting the world connected on IPv4, and the routers/etc deployed in the field (especially in sub-Saharan Africa, south Asia, and other places which got the Internet late) are built around version 4: data paths 32 bits wide, ASICs and firmware developed with 4-byte offsets, and so on.
It's a big effort, and more importantly an expensive effort, to move all that infrastructure over for what the end user perceives as no benefit: their websites load just the same as before.
I don't think the extra address space of IPv6 is the problem holding back its adoption, so "IPv4 with another octet" would likely run into the same issues.
Not that it's a bad idea, it's just an idea that's unlikely to catch on.
As the saying goes, "for bandwidth, nothing beats a truck full of ~~tapes~~ 1TB MicroSDs hurtling down the highway".
A little lower down the stack, I always liked the Evil Bit in TCP, a standard which removes all need for firewalls heuristics by requiring malware or packets with evil intent to set the Evil Bit. The receiver can simply drop packets with the Evil Bit set, and thus be entirely safe forever from bad traffic.
At the physical interface layer where data meets real life, I especially enjoy IP over Avian Carrier; that link in particular is to the QoS definition which extends the original spec for carrying packets by carrier pigeon.
For real though, the shortest license is probably the WTFPL:
Might've used it a couple of times myself.