“Carrier has arrived.”

Who gives a fuck what Sharon Osbourne thinks?

You know they are. Morten Messerschmidt has already been kissing Musks and Trumps asses on Twitter and he visited Mar-a-lago shortly before Trump was inaugurated.

I think they vastly underestimate how many things Meta tracks besides ad tracking. They’re likely tracking how long you look at a given post in your feed and will use that to rank similar posts higher. They know your location, what wifi network you’re on and will use that to make assumptions based on others on the same network and/or in the same location. They know what times you’re browsing at and can correlate that with what’s trending in the area at those times, etc.

I have no doubt that their algorithm is biased towards all that crap, but these kinds of investigations need to be more informed in order for them to be useful.

Damn. I would probably try a more mainstream distro for Optimus support, like Pop_OS! or Debian/Ubuntu with non-free repos enabled.
I remember Bumblebee was a thing back in 2013, but it seems that it hasn’t been updated since then: https://www.bumblebee-project.org/

Optimus as in Nvidia Optimus? I remember struggling with that under Linux in 2013. I would have thought it was supported by now. (Unless of course it’s another “Optimus”, in which case just ignore me.)

Yup. I remember it from when Atlanta hosted the Olympic games some time in the '90s. Despicable.

Didn’t something similar happen in Turkey with Erdogan a few years back? Pretty sure he was accused of being behind it himself too; don’t know what the final verdict was though.

I think it’s a pretty common accusation, just like when a politician is attacked, someone will invariably suggest that they staged it in order to get more support.

I don’t think anyone should fear for their lives because of their opinions regardless of how stupid they are.

Edit: It’s pretty fucked up that this is somehow controversial…

Ah, cool. I do have WSL installed on every Windows box I use regularly, but it’s good to know for when I run into a more locked down machine.

Seems a bit excessive to install WSL just to get an SSH client.

Using a password manager I’d have to copy-paste or remember each password. Not all have a web interface.

Then pick one that has a web interface or a CLI, Bitwarden has both and is free. KeePass databases can be hosted on your NAS and accessed to CLI tools. There are plenty of options. Or use passphrases (which are just as good as—or better than—complex passwords) and just type them? I use Bitwarden for literally each and every password/lock code/PIN that I have, and I have plenty of Pis and other things that don’t let me easily log into Bitwarden, but finding “Excentric4-Waxing-Adopted-Giraffe” on one device, and typing it in another really isn’t much of a hassle. (Also, why not just SSH into your Pis? Then you only need to worry about accessing a password manager on the machine you’re opening the SSH connection from.)

From the comments on this post it seems that you’re mostly looking for validation of the idea you originally had rather than actual feedback on how secure that idea is. You’re obviously free to manage your passwords exactly as you want, but this idea of a “base password” is objectively less secure than the alternative put forward by many people in these comments, namely to use the Yubikey to log into a good password manager that then handles all the different (completely unique) passwords.

There are always instances where doing things the best and most secure way is more cumbersome, and it’s up to you to decide if you want all of your passwords to be poor (and difficult to change, in this case) just because you occasionally need to log into something that doesn’t neatly integrate with a password manager.

Why not use the Yubikey for the master password on a KeePass DB (or another password manager) and then use actual different passwords—not just prefixed ones—saved in said password manager for your logins?

It doesn’t matter if your base password is a 255 character high-entropy annoying-to-type-manually-on-a-phone-keyboard or a 16 character string of alphanumeric characters if you reuse it in a slightly predictable manner. For it to be somewhat secure, the prefix would have to be completely random, which kinda defeats the idea of you being able to remember them. A “base password” is, to be frank, only one small step up from using the same password everywhere.

And as someone else pointed out, it makes it very difficult to change passwords, which also should be a huge red flag.

Take a look at the leaks on Have I Been Pwned and see how many of them include either clear text passwords or extremely weakly hashed (perhaps even unsalted) passwords. If you show up in just one or two of those, then you’re in a significantly worse position than you would be had you just used different passwords.

Did you read the article? She’s not saying that she didn’t know that measles are dangerous, she’s saying that she thinks people would vaccinate more and sooner if they knew the potential delayed effects of measles. Her son died 4 years after catching it and he wasn’t vaccinated at 2 because he was on a delayed vaccination program (it doesn’t say why). It’s a super tragic story really and it doesn’t seem like she’s anti-vax or anything like it, quite the opposite.

A little more info in the title than just the CVE number would make these posts a lot more useful.

Thanks!

I’ve skimmed through the whole thing, but I’m unsure what you’re referring to. A little help, please?

Similar thing with “a nickname”, which came from “an ekename”.

Literally no one but you has used the word “federated” in his thread of comments… You responded to the original comment about git being decentralized by saying “it’s still 1 centralized server that has the code”. I corrected you, because that’s not how git works, and now I’m not sure what the fuck you’re on about…

Edit: Screenshot, in case you forget.

You’d still have a complete copy of the current HEAD, you’d just be missing a bunch of history depending on the depth at which you cloned.