Only recently has it been anything other than relative ranking.

What questions that they asked, for which he said the answers were on the web site, can he not legally answer?

He clearly had an axe to grind with CNBC, given his multiple passive-aggressive mentions of how they predicted his downfall.

The one interviewer appeared to strike a body blow when she asked if his motivations were tied to a performance-based compensation package. All of GameStop's flailing malarky makes sense through that lens: the CEO was trying a hail mary, 'cause otherwise he gets didly-squat. Part of that malarky is claiming to own 5% of eBay when, as the main interviewer pointed out, most of that so-called ownership was through derivatives. This guy's a fraud. Time to short GameStop.

The interview shows the CEO is kind of a jerk. He probably shouldn't be put in situations where communication is a requirement, like public interviews that are intended to help achieve an aggressive goal.

It's like he didn't understand he was on air during the conversation, despite the host clearly calling out that there was an audience listening.

The stark response from eBay is certainly understandable, having seen the interview.

Agreed that the Mach-E is a terrible name. But how did they screw up such a guaranteed out-of-the-park home run with an electric Mustang? I mean the whole image of the Mustang is a sporty performance vehicle for the young and stupidly lead-footed. Mustangs are classically known for acceleration and EVs are wickedly good at that. I mean, if Ford were to create a 1965-styled electric Mustang, I shudder to think how many boomers would buy them. They were the dream car of an entire generation.

Ford, are you listening?

What if you write a bunch of random noise of the same file size to weights.bin ... what happens then?

That sounds great. However, anything that causes anatomical brain chages that persist after a month, with a single dose, would be, by me, considered unacceptably risky. I'm not saying that it's by default considered bad, both you and the paper are talking about positive changes, and that's good. I'm saying, "risky," as in, I don't know what negative effects haven't been identified and I'd need a much more complete understanding before I'd be willing to try it.

Most of the positive effects are in reported well-being, but I really want to see more cognitive tests. The tests on cognitive flexibility is a great start, but we really need a barrage of tests here: mathematical ability? Short-term *and* long-term memory? Spatial thinking? Are there *any* cognitive functions that are negatively affected here? It's important to understand this with anything that has this type of long-lasting effect.

If it's as effective against stovetop fires as the KMPH video indicates, some kitchen manufacturer should license this tech and build it into their vent hoods. Some sizable percentage of house fire start on stovetops, so killing them off early would be a good thing.

This will wreck some customers. Expats overseas without vpn access. Anyone working or living in a remote location without internet access. Military around the world, both on land and on sea. Maritime workers on ships.

Basically take a bunch of people who rely on gaming devices for their entertainment because of the remote nature of their job or home, and cut off access to stuff they already paid for. Well thought out plan, if the plan is to get people to switch to a different company's products.

As a friend of mine in an uncharacteristic fit of insight once said, as long as there is a decision point that can be discovered, yes and the code goes this way, no and the code goes that way, it is in principle possible to write a patch to circumvent any DRM.

Here, there is a timeout test.

Need I say more?

To me the hoops that smoothbrains will jump through to avoid IPv6 and stay on legacy IPv4, especially when hosting, is pathetic. NAT, port forwarding, tunnels, blah blah blah blah.

I have something like ~1.2 trillion times the number of routable addresses that the entire IPv4 space has. Not all are reachable, of course, just the services that need incoming access and they're each on their own isolated DMZ.

Forgot to add: if you enable IPv6, be sure to use the browser extension IPvFoo. It shows a small 4 or 6 in your URI bar to let you know what protocol you're connecting to. Once enabled, you'll see just how much stuff out there actually is IPv6.

Started the move about 18 months ago when I decided to get off my lazy ass. My ISP gives out a /56 prefix, so that lets me run 256 /64 subnets/VLANs in the house, currently there are ~10 in use. Everything get a GUA through SLAAC and I use RAs (Router Advertisements) to give ULAs to everything. Any external facing services get their own VLAN and /64 for the system(s) as needed. Firewall blocks all incoming as they usually do by default and I punch a hole for the external-facing systems. They can't reach back into the network, they only answer the phone. All the systems update DNS dynamically if the prefix or full address ever change.

I have an SSH bastion set up. In all this time there has not been a single SSH attempt from the internet. On IPv4 it was constant background noice.
For those legacy IPv4-only systems on the internet, I set up NAT64. I have an IoT VLAN and IoT 2.4 GHz wireless network that are only IPv4 because a lot of IoT network stacks are junk.

I'm still farting around with it, but man oh man, there's no way I'd go back to IPv4. It was one of the best moves I've done in ages.

The classic counter-example is Cheap Trick's Live at Budokan album which for many, myself included, had the definitive versions of many of their songs. If memory serves, they spliced a couple of different shows together for the release, but it was done pretty seamlessly.

Apparently the rain doesn't reach the surface. But it is still only slightly less hellish on the surface for the lack of droplets of concentrated sulfuric acid pelting down.

Or iPhones?