Dude! Nothing frustrates me more than people mistaking server version with api version. It means I can’t update one piece of infrastructure at a time or you can never break api compact. Your server needs to support multiple api versions for rational progression of a distributed system.

Where i work we abuse semver but I hope in a good way. Major is wire api break. Minor is effectively YYYYMMWW (we ship weekly) and patch is number of commits off stable branch.

So not actually SemVer.

Please take this down. Load page with fresh cookies. It’s a scam.

I hadn't noticed the part at the very bottom the first time I'd read it. Idk I definitely wouldn't participate in whatever that's about.

If you know of a better source of information about McAfee's disappearance other than his official twitter, I'm all ears.

I agree, you would have to tie IPs->peer keys to make this work.

nacl says that for security each nonce/key pair must be unique for each message. If you send a "HELO" message, for example first, you've made it possible to build a pretty simple rainbow table if nonce just starts at 0 or 1. That said, it would seem that the first nonce being random and then incremented would likely work well.

A rainbow table? The key space is 2^256. If you're talking about building a table containing the ciphertext of "HELO" with all possible keys, that's totally infeasible. As you correctly state, NaCl requires each nonce/key pair to be unique. If you start the nonce at 0 for a given key and increment it for each message, as is commonly done, that satisfies the requirement and is secure.

But the NaCl key is randomly generated for each connection.

Your message length is sent in plain text and unauthenticated. Does this present a problem?

Probably not, because messages are authenticated cryptographically, and the lengths are validated before being passed to libsodium. You can't truncate an authenticated message.

mind = blown

I was a huge fan of this in '98. Was very sad to see it fail. I even wrote custom software for Litestep so you could see what beat time it was.

As an example:

I don't know where you are, you don't know where I am. I tell you I am available from @300-@800 if you want to Skype today. Let me know which time is good for you.

Which would be scenario A. You just did the lookup of finding that 0xEA's business hours are from @300 to @800.

Sure, you would have to know that. But you have to look up if the business you want to contact is open on Sunday anyway, even if they are local. Or what time they close today.

Or you have to try to figure out the whole no work on Friday thing in the middle east and Monday being part of the weekend. You always have to look it up.

What made this dream cool in the digital age is I could just have hours that I'm available and if I wanted to work late at night, I could. I considered myself a 'hardcore hacker' in '98 and what appealed was how well this lined up with my natural inclination to hack on code from 10pm to 5am every day, despite being in high school.

I didn't care or need to know where my IRC friends were. We could collaborate none the less.

WW2 had a ton of propaganda about distrusting people, yet according to this article that was a very trusting time.

>WW2 had a ton of propaganda about distrusting people

Yes, but that propaganda was nothing compared to the much more advanced and sophisticated level of indoctrination techniques we have in more modern history via mainstream television and radio.

And, don't forget WWII had wonderful internment camps and plenty of racism towards blacks in America. So it wasn't the most trusting place for everyone.

WWII propaganda was about Americans coming together to kick Japan and Germany's ass. Unless you were Japanese or German, most of the propaganda and the general sentiment around the war effort was about all Americans joining forces to win the war. There's even a part in one of Frank Capra's "Why We Fight" propaganda films calling on Americans of all ethnicities to set aside their differences and work together to win the war.