The idea of solving the problem by reclaiming IPv4 addresses was considered, but the math doesn't work:

Now, average daily assignment rates have been running at above 10 /8s per year, for 2010, and approached 15 /8s towards the end. This means any reclamation effort has to recover at least 15 /8s per year just to break even on 2010’s growth. That’s 5.9% of the total IPv4 address space, or 6.8% of the assignable address space.

Looking at the /8 blocks assigned to organizations other than regional NICs, there are 40 of them. So even if we could persuade all those organizations to give up their /8s, and even if we could organize it all quickly enough, the best we could do would be to put off the problem for 3 more years.

In addition, reclaiming IPv4 addresses is far more expensive than rolling out IPv6, and it's hard enough to persuade companies that they need to roll out IPv6.

And the calculation for class B allocations is even worse, because you have to deal with a lot more organizations; the cost is higher for far lower returns.

I currently have a web radio transceiver front panel application that works on Linux, Windows, MacOS, Android, Amazon Kindle Fire, under Chrome, Firefox, or Opera. No porting, no software installation. See blog.algoram.com for details of what I'm writing.

The one unsupported popular platform? iOS, because Safari doesn't have the function used to acquire the microphone in the web audio API (and perhaps doesn't have other parts of that API), and Apple insists on handicapping other browsers by forcing them to use Apple's rendering engine.

I don't have any answer other than "don't buy iOS until they fix it".

If you are working on an existing project that has already chosen to use jQuery, then you should learn it.

Otherwise, I wouldn't bother. Just learn Vanilla JS, and skip jQuery. Your pages will be faster and better.

jQuery was a useful thing a few years ago, but now that browser standards compliance is so much better it's a big chunk of unnecessary code.

Super Dracos are for escape in flight too, including in and past MaxQ. But they are on Crew Dragon, not Cargo Dragon. Cargo Dragon did not carry a crew and wasn't programmed to save itself.

Most of us do have a need to transmit messages privately. Do you not make any online purchases?

Yes, but those have to use public-key encryption. I am sure of my one-time-pad encryption because it's just exclusive-OR with the data, and I am sure that my diode noise is really random and there is no way for anyone else to predict or duplicate it. I can not extend the same degree of surety to public-key encryption. The software is complex, the math is hard to understand, and it all depends on the assumption that some algorithms are difficult to reverse - which might not be true.

"Now seriously..." doesn't stop a sexist joke from being sexist.

Indeed. And he was given the chance to put his side of the story on June 10th. Unfortunately for him, he made a non-apology apology, saying:

"I did mean the part about having trouble with girls. It is true that people - I have fallen in love with people in the lab and people in the lab have fallen in love with me and it's very disruptive to the science because it's terribly important that in a lab people are on a level playing field. I found that these emotional entanglements made life very difficult."

and

"It's terribly important that you can criticise people's ideas without criticising them and if they burst into tears, it means that you tend to hold back from getting at the absolute truth. Science is about nothing but getting at the truth and anything that gets in the way of that diminishes, in my experience, the science."

As for the idea that he was taken out of context, the linked article which is supposed to support that idea quotes him as saying:

"Let me tell you about my trouble with girls. Three things happen when they are in the lab: you fall in love with them, they fall in love with you, and when you criticise them they cry. Perhaps we should make separate labs for boys and girls?”

So yeah. He was sexist in context, he was given the chance to put his side of the story, he doubled down and said he stood by his comments and made more sexist remarks, and only then did he lose his job on June 11th.

Submitter should probably spend less time reading Brietbart.

Most algorithms to do this use the time between keypresses, measured to very high precision so that the lower bits are chaotic. So it doesn't really matter what keys you hit, and it doesn't matter how rythmic your typing is.

The problem with FM static is that you could start receiving a station, and if you don't happen to realize you are now getting low-entropy data, that's a problem.

There are many well-characterized forms of electronic noise: thermal noise, shot noise, avalanche noise, flicker noise, all of these are easy to produce with parts that cost a few dollars.

True randomness comes from quantum mechanical phenomena. Linux /dev/random is chaotic, yes, enough to seed a software "R"NG. But we can do better and devices to do so are cheap these days.

I wouldn't trust anything but diode noise for randomness. If I had a need to transmit messages privately, I'd only trust a one-time pad.

Communism has been tried on a large scale - see Mao's Great Leap Forward.

Nope. That was a totalitarian socialist program pushing a collectivism that didn't work. Communism is a post-scarcity society and obviously scarcity was the thing Mao produced best.

Whatever it has been used for subsequently, A113 is a classroom at Cal Arts.

I didn't actually work on GPUs very much at Pixar, the image computer I worked on was the grandfather of the SIMD image processing instructions on modern CPUs. What would become a GPU later on was a very expensive box from Silicon Graphics, I had one that cost at least a quarter Million dollars.

If they actually told us how to program their microengines, something good might come of it. But they'll probably just BSD-license a list of numbers, as others have.

I liked writing bit-slice microcode at Pixar. I really could get every last bit of power out of the hardware.