Before youtube disabled recommendation for people with watch history turned off, having watch history turned off made it so your recommendations were only based on channels you are subscribed to and possibly videos you’ve liked, commented on, …

There are some categories where I only ever search for the category, then watch a video, but never subscribe to any channel. Those videos were never recommended to me. Meanwhile on my girlfriends pc with watch history turned on, as soon as I watch a single video from a channel she’s not subscribed to similar videos appear all over the front page.

After noticing that ctrl+c doesn’t work he tried typing exit, which put him in edit mode.

They recently announced that they will publish new exploits at DEF CON next week and recommend owners to not update their firmware if they want to take advantage of that.

So depending on how the exploit works installing Valerie might get a lot simpler. It usually takes quite some time until such exploits are not only fixed, but then also for devices with fixed firmware to hit the shelves.

There was no bot net doing the outlines. The r/placeDE Discord prepared an overlay and distributed it to many other large communities and twitch streamers.

At the time or the whiteout the r/placeDE had 6500 active users in the voice chat coordinating to draw the outlines. A German streamer sent his 100k+ viewers to draw the letters. Other big communities also contributed.

You’re probably thinking of Lemmy.ml

Do you use podman run followed by podman generate or are you using quadlet?

Quadlet is integrated in podman 4.4 and up and makes it possible to declare your containers in .container files that look like systems unit files and still get the full systems integration: https://www.redhat.com/sysadmin/multi-container-application-podman-quadlet

Every Rubik’s Cube, no matter how scrambled, can be solved in at most 20 rotations.

They blocked access in the back end, but didn’t adjust the frontend to deal with this situation.

If you try to access twitter while not logged in the frontend requests tweets from the backend, gets an error response and therefore tries again around 10 times per second.

Many of the keys sold on key reselling sites are bought with stolen credit cards. It usually works like this:

1. Someone obtains stolen credit card data (can be easily bought on the dark web)
2. The stolen credit card data is used to buy keys from official key sellers (or directly from the developer of they offer them)
3. Those keys are then sold on key reselling sites
4. The credit card owner notices that his credit card data was stolen, contacts his credit card company and does a charge back. 5.The official key seller has to pay back the money + a charge back fee.

Parking lots

Wow. Now you can finally build realistic American cities ;)