Yeah. I’m surprised they took from MI. Management was just complaining last week about how hard it is to hire RTL people and trying to juggle us around to all the generations and variants that need to be staffed. And then this week it’s this. Maybe it is how they fire people; I haven’t heard of anyone else being fired besides this layoff in the ~4 years I’ve been there.

As someone who works at AMD not in AI, that’s how they explained it to us. Or I guess it was a bit more generic “highest growth areas” and “still hiring for positions aligned with our strategic priorities.” Which we generally took to mean AI based on the gestures broadly at the market.

If you want to work in AI, they’re hiring. The layoff was sold as a way to make room for more AI headcount.

What does the name being common in that case get you that individual doesn’t? The only thing I can think of is not having to take the trouble to name it yourself, which is such a minor thing.

Canadians as a dogwhistle for what, dare I ask? Or was that part of what you refused to ask?

That’s good. The article linked to by the graveyard made it seem like they didn’t.

Pixel Pass

Killed 8 months ago, Pixel Pass was a program that allowed users to pay a monthly charge for their Pixel phone and upgrade immediately after two years. It was almost 2 years old.

Well, that seems particularly scummy.

You don’t get it. Valve never has a business plan! It’s a hierarchyless place where everyone just moves their desk whenever and works on whatever they want. Plans? Who needs them!

I think that’s google opinion rewards. Or at least Google opinion rewards is the same thing.

The RSS feed points to the already hosted files. A lot of people host podcasts on services like libsyn or podbean. I don’t think you can really host podcasts on Google; maybe hacked together on drive or something.

It’s been super easy the two times I’ve done it.

Podcasts are (generally, Spotify excluded) on an open standard. They’re just RSS feeds. So, the content can be aggregated by anyone. So it’s primarily the UI that will be different between different podcast players.

Are you mixing it up with Google Forms? I think most people would never have used surveys, whereas forms is pretty popular. And they sound the same.

If you read the article it’s explained that some SSL implementations put random data in the time field (OpenSSL was given as an example). Microsoft knows about this and so needs a certain number of closely matching timestamps to be confident about the new time to change the system time. However, if you get particularly unlucky with a string of random timestamps that match, you end up with a random time.

You don’t need to, but it probably wouldn’t be a bad idea unless you were already using fairly complex passwords.

For a lot of them, you set up the service, then as you log into things, it asks if you’d like to save the login credentials you just used.