Thank you for balancing the parentheses. Cosmic order has been restored.

The answer is that this is somewhat misleading; there are plenty of Z80 compatible chips still being manufactured. The TI-84 uses the eZ80, which is four times faster and will still be around. There are also many (many) clones that are closer to cycle-exact.

The agony, of course, is that Dieter Rams was all about function, which informed his designs. If Apple had hired him (he's still alive, incredibly) instead of just imitating him, he'd probably have taken a significantly different direction that actually respected the complexity of the underlying hardware instead of trying to butcher it. And the logos would have been smaller!

The only questions I have are:

1. Google is still in the search business? I thought they went to sales only.
2. People still use Google Search? Isn't that like opening a coupon book when you want a dictionary?
3. If they charge for it, will they stop throwing out good search results and still give you only the poisoned SEO results for things that have zero to do with what you were searching for? I searched for (as an example, not real) "No dust or scent Cat Litter" and got four pages of ads for everything but cat litter. (as an example, not real)
4. Don't ask me what I use to search, aside from Reddit, I've not found anything like Google before they crapped out.

Since many cannot comment with real world experience at scale deployments, Hypothetically, fault probes are generally path aware when the path itself is not redundant. Hypothetically, a three letter data center would have multiple data lines that enter the building from hypothetically different directions with hypothetically independent routing into the area of the building, though, sometimes Telco will hypothetically lie to you about route paths. Which is why, hypothetically, an alarm would also be fault path aware.

Hypothetically.

Using that sort of logic, Chevy can't be held libel for modifying a '57 pickup.
Guess what? They already can't. Just as Boeing can't be held libel when an air line screws up maintenance procedures. Don't look now, but a combine doesn't fly at 500 MPH at 40,000 feet with 250 people on board.

Or more directly, Numbers 5 (all of it is an abortion recipe) or Psalm 137:8-9.
Or, if you want verifiable archeological facts, the smashed skulls of infants at the back of Roman baths, and oddly, nothing was ever said about that in the new testament.

Barely pessimistic. I was trying to think of anything absolutely new, without prior lineage, in electronics for the past 50 years and come up blank. Which is not to say there are not any, simply nothing that comes to my mind that I would consider as new in every way. I mean, REALLY new things, not like a blue LED (we've had LEDs since 1962), not MOSFETs (1959), I mean really new. Not chips either, as it is not a break through, simply a refinement of application of single transistors. Even Maggies aren't that new (1940). nor CCD arrays (1969).

PS: Yes, I did need to look up when each was invented - so maybe the Internet could be seen as "newish" - derived from ARPAnet (1969 - ish?)

My (possibly flawed) recollection is that the Eastern District of Texas is concerned, as far as taking patent cases, was legislated/regulated (I forget which) out of the patent troll business. The judge tried to circumvent it, and got nailed for it. Well, nailed as hard as they ever nail a judge - batted with big fluffy pillows and a stern finger wag with a very cross look. And Horror of Horrors, a whispered "NO!".

So the FBI and SS get a heads up, but not the general public. Which, I would argue, should be required withing 60 days unless given authorization by both the FBI and SS to maintain a moratorium. Further, it should apply to anyone at all that has PII on others beside themselves, their family, or their legal wards below ten in number. Any more than ten, they need to report. (I'm thinking states maintain a large number of wards, orphans and the insane for example. They need to be accoutable)

Are there others that occurred that we don't know about? I couldn't say. How many cases of fraud and loss have people suffered because they were victims, but that the banks or institutions involved were allowed or required to keep silent?

snark - The average American city seems to present insurmountable barriers to trouble free operation. - /snark

Expensive rides with people that are usually pretty nice folks.

It was the constant waking me up in the middle of sleeping (I've no set schedule and it is not usually "business" hours) really got my ire up. Add in that the settings seem to go back to "annoy the shit out of our customers" whenever there was a (frequent) silent update. I assume that's what was going on anyway. I spent 45 minutes with Google, the phone, and the App to turn off notifications, only to have it wake me up less than 5 hours later. I don't want to have to spend time to tell a company not to annoy me when I give them money.

As to using them to pick up food, for the most part it more than doubles the cost, usually gets the order incorrect, arrives cold with side orders "missing".
For me, the only valid use case for Ride Share/Food Delivery rather than owning my own vehicle is convenience. And I don't find it convenient to be woken up while asleep, or get the wrong, cold food order.

Personally I found this really eye-opening, so...

TC doesn't require patching which to my mind is more elegant and sustainable across servers. (TARPIT last I looked required patches)
Granted I don't use it in production but my mindset is by default set for "at scale" and I didn't remove my lazy thinking. Those that "just want results" would likely be happier with your choice than mine.

I'll block at the drop of a hat on personal systems - though I can't on production things.
But really, wouldn't it be more apropos to cause them pain, suffering, and woe?

A few dittys with tc does the trick to slow down their network traffic down to one packet every 30 seconds.
Haven't thought about it too much, but some off the cuff build out mile stones:
Ensure that the setup (adding the qdisk, class) is only done once, then the cascade of tc filter add dev blah blah blah.

quick ditty (alias or /usr/local/bin) to add IP space as it is noticed.
quick ditty to drop all the rules.
quick ditty to put them back.

Since pfSense 2.7 was released, my setup has been unstable. Even a reboot twice a day and it still locks up. Nothing in the logs at all.
Complete top to bottom hardware swap (same models of everything, different hardware) and still locks up two and three times every two days.
Moving to opnsense.