Perl is the only language that looks just as incomprehensible before and aa rot13 transformation.

Lol. You’re not wrong.

I’m kinda jealous. I don’t miss maintaining production Perl code, but Perl was more fun to code in.

Lisp is the more logical choice.

Relevant XKCD. Python has replaced Perl, but things have otherwise changed quite little.

The only way to know if you are competent coder is for other coders to tell you. If none are telling you, your imposter syndrome isn’t.

Or, considering that they’re mostly introverts, if they look approvingly in the general direction of your shoes…

Yeah. An elephant won’t stay crisp in the egg compartment.

Gee. The police are still protecting us by smashing fun things

Edit: Since I don’t in any way routinely buy from these guys, there’s no way I can possibly let y’all know later, when the supply is in no noticable way diminished by this.

The exciting thing about this is just being able to reuse more USB controllers that happen to be lying around available.

The vast majority of the Evercade catalog has no particular use for Analog controls, but it’ll be nice to be able to plug in and use a controller that happens to have analog sticks.

It’s also worth noting that none of the games that do support Analog actually expected the player to have analog sticks. I’ve played most of those either on PS1 or Evercade, and they’re winnable without analog sticks.

Analog sticks for PS1 were available, but most folks didn’t have them.

I’m predicting that the “hidden secret” for those “on the ball” is a bonus Piko game when Piko Collection 3 and 4 are inserted. Since Piko 4 features Glover, and bonus games for cartridge pairs have been a tradition for awhile.

Ever since they added DRM Anti-cheat to Capcom Arcade 1 and 2, I satisfy my nostalgia for old Capcom games… Other ways.

There’s this guy who stands in an alley near my house who sells a USB stick with everything Capcom ever made before 2004.

I’m sure he’s officially licensed. He’s my preferred Capcom vendor, because that USB stick was DRM free.

You’re not wrong to give the benefit out the doubt and believe their PR person isn’t lying.

But I’m not inclined to give that benefit of the doubt. I don’t trust these folks farther than I can throw them. I don’t, myself, need proof, to believe they would try this crap.

And this is definitely evidence.

But without hard evidence I don’t believe random apps are just recording clandestinely in the background.

I certainly do. Malware attempts to record you is old news.

We have always assumed voice was off the table for practical reasons - voice recordings are expensive to decode and correlated usefully.

Cox has particularly deep pockets, which makes this interesting.

I do actually agree, this really could just have been a vendor bullshitting. Normally I would say Occam’s razor points there. But Occam’s razor points the other way, to me, when I consider that basically everyone I know has experienced a voice targeted ad.

The big ugly question is which apps are recording voices?

It might just be name squatting spyware. I haven’t seen confirmation that any do this, and I always assumed it was too expensive. Maybe it still is, but my guess is Cox isn’t the only ones who got that sale offer.

The creepy part is, if you’re not inclined to take Google, Amazon, and Meta at their word, then one wonders what other apps are recording voices…

Here’s the conspiracy part:

• Apps by Meta famously ask for more permissions than they should reasonably need.
• Both Google and Amazon publish operating systems that promise us they are enforcing our permission preferences, while definitely collecting more behavior data than most people would feel comfortable with, if they were aware.
• We know that all three companies thrive on tracking our behavior, and selling what they learn.
• One of the three had to change it’s corporate slogan away from “don’t be evil”.

The conspiracy emerges when we look at these data points and squint a little.

Security researchers would’ve noticed this.

They did notice. Malicious apps that use everything they can to spy on you are old news.

To your point - this isn’t confirmation that any of the big players are listening directly. That would probably have been caught by security researchers, although it would be really difficult in Google’s or Amazon’s case, as they run proprietary software at a very low level.

The news here is two fold;

1. Cox got caught buying that data, and when confronted about it, Google, Amazon, and Meta all failed to deny that they also buy that data from those malicious app makers.

2. This is strong evidence that someone is routinely collecting that data. That’s news. We’ve suspected for awhile that, at minimum, the malware apps do. Occam’s razor says at minimum, we should now assume many malware apps are using microphone to collect speech and submit it elsewhere for analysis.

The unprovable part of this that smells much worse is: a kid in a basement writing malware does not have the computing power to turn tons of raw voice recordings into useful correlated data.

That kid needs an ally with a lot of computing power. Google, Meta, and Amazon all have a motive here and have the necessary computing power.

And all three worded their denials pretty carefully, I noticed.

In summary: Google, Amazon and Meta all deny that they directly access your microphone, and all three failed to actually deny purchasing voice data from third party apps that definitely do use your microphone and pair that with your ad targeting profile.

This is getting more attention because an internal slide deck from Cox Media Group was leaked. Based on rthe nature of leaks, it’s safe to assume that Cox isn’t the only organization up to this, they were just thee least careful.

So yeah, they’re listening to anyone who isn’t incredibly careful what apps they install and what permissions they give those apps.

Exactly as we all have suspected for years, while they gaslight us promising that they definitely don’t.

Notice that they’re still denying it, and trust that as you will.

I think they forgot to pay themselves to use their product.

You are supposed to be tracking when they expire and then renew/replace them before they expire.

I’ve been told that, as well, but I’m not sure I see it… Seems like a lot of effort… (This is sarcasm. Or is it just too much honesty?)

Yeah. The idea of an automated C to Rust replacement of the Linux kernel is fascinating. As you say, there’s probably stuff in the Kernel that Rust’s compiler won’t allow.

I imagine it wouldn’t work at all, out of the box, but it might reduce the cost curve enough to make a dedicated team of very clever engineers able to cross the last mile, given time.

As cynical as I am of both Rust and AI generated code, it honestly feels like trying an automated conversion might be less of a long shot than expecting the existing Linux kernel developers to switch to Rust.

And I’m sure a few would kick in some thought cycles if a promising Kernel clone could be generated. These are certainly interesting times.

Lol. If Rust fans want a Rust kernel, no one is stopping them from building one.

This is a good list. Another, often overlooked is:

Sometimes we just get incredibly unlucky and interview at the same time as someone wildly unusually more qualified.