Basically just 2048. I have actually had a single 7x7 game going for literally months.

They are just RFID and can be read with consumer devices

https://docs.flipper.net/rfid/animal-microchips

There are definitely visual similarities, especially if you are watching the episode in 1960’s quality. But in the modern remaster, the eyes look more like they are probably something like foam spheres with plastic gems glued on.

the eyes were microphone covers.

This is the second time I have seen that said on Lemmy, and I just don’t see it. Do you have a source for that? I cannot find anything.

Your title makes this sound like a bad thing, but this looks like it would probably be preferable over being shown whatever it is YouTube wants you to see.

It does seem to be a coincidence. Or, perhaps that was chosen as the starting point, and after several rounds of focus groups, they settled on what we ended I’ll with.

I downloaded a copy of the album art, loaded it in GIMP, and used the color picker, and it considered that 89cd00. According to multiple sources online, it is officially 8ace00. Then, I compared those to a few possible 1337speak variations of the word “baddie”.

Can’t wait to see what they come up with next.

Framework smartphone please. Though I think that is VERY unlikely.

Lemmy seemed to parse that as two separate hyperlinks for me. This should work as a simple clickable link 🤞 https://web.archive.org/web/20240926051545/https://forum.makemkv.com/forum/viewtopic.php?f=16&t=19634

ALL NIGHT LONG

You don’t choose the Soy Sauce; the Soy Sauce chooses you

Hmm, I think this is an Mbin vs Lemmy issue. There are two differences in the URL:

1. The broken URL has %2C instead of ,. This part does not make a difference, because that resolves to a comma anyway
2. The broken URL has = at the very end for some reason. This is what breaks it. Remove that character, and the URL works fine

The weird thing here is that the broken URL only ever shows up on Mbin. Below are a few different links to the comment in which you shared the broken URL. If you view the comment on your Mbin instance, it is indeed broken. But if you view it on this community’s Lemmy instance or my home instance, your same comment actually has the working URL. Something about how the post/comment were federated must have messed things up.

• https://programming.dev/post/32148095/17523722
• https://lemmy.sdf.org/post/36630589/20713561
• https://thebrainbin.org/m/technology@lemmy.world/t/864885/We-re-done-with-Teams-German-state-hits-uninstall-on-Microsoft/comment/6706294#entry-comment-6706294

Is that not literally the same link as the OP?

EDIT: Ah, the OP’s edit from 30 minutes before your comment has not federated out to your instance yet.

Risk E. Rat’s

Wow, I misread “HM” as “HAHA” and had a different expectation of what the bottom text was going to be

May I go ahead and chisel your aromasphere?

I was thinking the League, but yes, that P&R scene was almost certainly inspired by the vaportini trend.

Although if you put it in vape form…

Vaportini was a short-lived trend that did not end up taking off.

There doesn’t need to be any evidence. This is something that is impossible to prove one way or the other, like Last Thursdayism.

Yes, this particular incident.

https://en.wikipedia.org/wiki/XZ_Utils_backdoor

In February 2024, a malicious backdoor was introduced to the Linux build of the xz utility within the liblzma library in versions 5.6.0 and 5.6.1 by an account using the name “Jia Tan”.[b][4] The backdoor gives an attacker who possesses a specific Ed448 private key remote code execution through OpenSSH on the affected Linux system. The issue has been given the Common Vulnerabilities and Exposures number CVE-2024-3094 and has been assigned a CVSS score of 10.0, the highest possible score.[5]

Microsoft employee and PostgreSQL developer Andres Freund reported the backdoor after investigating a performance regression in Debian Sid.[8] Freund noticed that SSH connections were generating an unexpectedly high amount of CPU usage as well as causing errors in Valgrind,[9] a memory debugging tool.[10]

Immediately get noticed

Realistically, though, we are only aware of that one because it was noticed in that unlikely scenario and then widely reported. For all we know, most open source backdoors are alive and well in our computers, having gone unnoticed for years.