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.
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.
Yeah. That’s normal if you subscribe to things through (iOS or android) apps.
Google and apple don’t allow apps you roll their own payment methods to “protect their users”. Apps have to use the Google/Apple payment system where Google/Apple take a 30% cut of every payment.
With YouTube being owner by Google they probably don’t have to pay those 30% on Android, but they have to on iOS.
I was subscribed to reddit Premium for a long time (at the old, grandfathered in price), because it gave me ad free browsing, the ability to sort saved posts into categories and filtering subs from r/all before that was available to everyone.
Premium also gave you 700 coins per month, so now I have 20000 coins saved up.
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.
I don’t think google fear Apple having to offer a choice to users. They fear Apple defaulting to Bing or something else.
While most people might choose google when presented with a choice, possibly more people are just going to keep the default settings when not presented with a choice.