Need money to live, so get a job. Need to pee in cup to get job. Company pays for the test so they get the results. Company offsets cost of test by selling data to test labs. Test labs find cancer markers and make note in database. Insurance company buys database. Insurance company marks pre-existing condition found in test and raises insurance costs. Still not informed of test results. Life insurance companies buy database. Premiums raised to point of being infeasible. Still not informed of test results. A few years pass. Get sick. Eventually get doctors appointment. Bladder cancer detected, stage 4. Die.

What’s the problem here? You’re right, it’s how there’s an opportunity not being captured. Our company will keep and maintain the database, and instead of losing money by insuring sick people, your company for a nominal fee can have constant access to the data so any underpayment issues can be avoided before they start.

That’s my elevator pitch to a VC firm. The first paragraph is a storyboard for an ad we’re going to shoot. The other higher-up at the company is going to see if his girlfriend will be the person in the story.

I’ve been wondering ever since what can they do if they had it?

Ask for pictures of all his other paperwork so they can finish onboarding him at his new job.

When reached for comment the family said, “how could this happen to us? We’re not even trans?”

Have the day you voted for, know that you won’t be the last people in rural areas that this happens to, and that when the AI bubble pops you still won’t get the land back. It’s gone forever.

Ft. Knox

Did anyone ever go in there and show the gold? I thought someone campaigned with that as a promise.

abusive scraping

As opposed to the plain old scraping they do to train AI, and generate revenue by selling user comments for others to train AI.

I read a half-cocked internet theory that a certain someone might’ve purchased twitter just to gain access to an ex-gf’s personal tweets. I judged it as possible but unlikely, as that’s a lot of money to spend on such a thing.

Now, we’ve all heard stories about reddit blocking accounts for no published reason, and tracking folks down across accounts/IP addresses/etc. That code must be pretty expansive to do the things they’ve done. So one has the thought: if you’ve ever reached out to the reddit hive mind for some kind of support with a personal issue of any kind then that data about you is still floating around in their database and tied to whatever alternate accounts you have, even if it was the “good old days” when you did it.

Abusive scraping, my ass.

There are four version of x86_64: v1, v2, v3, and v4.

RHEL 9 dropped support for anything prior to v3. That means RockyLinux doesn’t cover it, either. AlmaLinux has support for v2 in version 10, but there’s no way of knowing how long that will last.

Some binary packages are starting to drop support for earlier version. The latest numpy out of pip will not work on a v1 machine. You can sometimes use the system package manager’s numpy to work around it, or constrain pip to use an older numpy. I don’t know what else is lurking out there.

If you’ve got visions of taking a really old computer that you happened to max out on RAM back in the day and bringing it back to life there are surprises waiting for you.