DigiCert recently was forced to invalidate something like 50,000 of their DNS-challenge based certs because of a bug in their system, and they gave companies like mine only 24 hours to renew them before invalidating the old ones…

My employer had an EV cert for years on our primary domain. The C-suites, etc. thought it was important. Then one of our engineers who focuses on SEO demonstrated how the EV cert slowed down page loads enough that search engines like Google might take notice. Apparently EV certs trigger an additional lookup by the browser to confirm the extended validity.

Once the powers-that-be understood that the EV cert wasn’t offering any additional usefulness, and might be impacting our SEO performance (however small) they had us get rid of it and use a good old OV cert instead.

Back in the 90’s before the days of Windows 3.0 I had to debug a memory manager written by a brilliant but somewhat odd guy. Among other thing I stumbled across:

• A temporary variable called “handy” because it was useful in a number of situations.
• Another one called son_of_handy, used in conjunction with handy.
• Blocks of memory were referred to as cookies.
• Cookies had a flag called shit_cookie_corrupt that would get set if the block of memory was suspected of being corrupt.
• Each time a cookie was found to be corrupt then the function OhShit() was called.
• If too many cookies were corrupt then the function OhShitOhShitOhShit() was called, which would terminate everything.

If you have ssh open to the world then it’s better to disable root logins entirely and also disable passwords, relying on ssh keys instead.

Port 22 is the default SSH port and it receives a TON of malicious traffic any time it’s open to the whole internet. 20 years ago I saw a newly installed server with a weak root password get infected by an IP address in China less than an hour after being connected to the open internet.

With all the bots out there these days it would probably take a lot less time if we ran the same experiment again.

Back in the late 90’s I worked for an internet search company, long before Google was a thing. We would regularly physically drive a dozen SCSI drives from a RAID array between two datacenters about 20 miles apart.

I don’t understand why Cloudflare gets bashed so much over this… EVERY CDN out there does exactly the same thing. It’s how CDN’s work. Whether it’s Akamai, AWS, Google Cloud CDN, Fastly, Microsoft Azure CDN, or some other provider, they all do the same thing. In order to operate properly they need access to unencrypted content so that they can determine how to cache it properly and serve it from those caches instead of always going back to your origin server.

My employer uses both Akamai and AWS, and we’re well aware of this fact and what it means.

‘21 Model Y long range. Overall it drives well, and the supercharger network is really nice. We took it on a trip up & down a good portion of the east coast last year and never had any issues charging it. We have a couple 30 lb dogs that love going for rides, so things like dog mode are really nice as well.

Things I really do not like:

• The reliance on cameras for all sorts of features like auto high beams and auto wipers on top of traffic aware cruise control (aka autopilot) (and full self driving, if you have it). I regularly have the wipers go off on clear, sunny days. The auto high beams are so unreliable I don’t use them, and that means no autopilot at night. I have no faith in even trying out FSD because of how glitchy everything else is.
• The minimal use of physical controls. I have to take my eyes off the road just to switch wiper speed/mode.
• Software updates have, more than once, changed my settings for things like autopilot without warning, and I’ve only discovered it when driving and turning autopilot on.
• The maps have lots of routing issues. It shows roads in my neighborhood that don’t yet exist (new development under construction), regularly routes me wrong ways (there’s a left turn near my home that it thinks it can’t take so it tries to route me two sides if a triangle as a result), and on our road trip we found a stretch of highway that it thought it couldn’t drive on and kept trying to route us along side streets. And there’s no way I know to report these issues so they can be fixed. Apps like Waze make that trivial.

Pretty much all of these are reasons why I refuse to even try FSD and discourage others from using it. About the only way I’ll give it another chance is if a truly independent third party tests it and says all these issues have been resolved.

I admit I own a Tesla. Given all the recent erratic behavior:

• Not only will I not recommend Teslas to anybody who might ask about it, I will warn them to look at company & CEO behavior over the years, and actively discourage others from buying one.
• When the time comes, I will not be replacing my current car with another Tesla. I will still likely go with an EV, but by then there should be significantly more good (better) options available.

About the only way I’ll change either of these will be for Elon to step down and completely remove himself from any control over Tesla. But I don’t see that happening and I certainly won’t be holding my breath.