Are these things literally Little Tykes Cozy Coupes like wtf

This change is likened to expanding a CPU from a one-lane road to a multi-lane highway

This analogy just pegged the bullshit meter so hard I almost died of eyeroll.

Damn it’s gonna take me a while to make a whole cup but I’ll get started

deleted by creator

So an option that is literally documented as saying “all files and directories created by a tmpfiles.d/ entry will be deleted”, that you knew nothing about, sounded like a “good idea”?

Bro, if it sounded like a good idea to someone, you didn’t fucking warn them enough. Don’t put this on them without considering what you did to confuse them.

Also, nfn, the systemd documentation is a nightmare to read through, even if you know exactly what you’re looking for.

(I’m still gonna keep using systemd because it’s better than the alternatives, though. OP, don’t write stuff off because 1 guy is a dick.)

Two stories like this–as in, “oops AI sucks actually”, in about as many weeks. (The other one was about Amazon shutting down their Just Walk Out mechanical turk nonsense.)

I think we’re starting to see the tide turn against Altman’s big con.

I liked this quote BTW:

the test left it confident “that a voice-ordering solution for drive-thru will be part of our restaurants’ future.”

lmao you… already have one of those? So the subtext of this message is “we can’t just say AI was a terrible idea but yeah, we’re going back to the shit that worked before”

Approximately 4-6 million to live on the interest for the rest of my life. That’s all it would take and I’m out forever.

Fair enough. I guess I’m not saying “there’s no point in --” because I know people do these things. (Man, I wish I had the attention span to read as much as you.) I’m just saying I’m not going to host something just to keep track with no recommendations or interaction because that doesn’t click for me personally.

Same. I don’t really see the point of tracking what you read if you’re not interested in connecting it to other peoples’ readings. Storygraph has been great.

I’m sure the richest company in the world is super worried about this threat.

deleted by creator

The woman who launched the site gets clocked as trans by gender prediction systems. It’s already happened.

Nothing could possibly benefit that company as much as Elon Musk getting demotivated and no longer coming in to work.

deleted by creator

“It’s broken in horrible, dangerous ways, and we’re gonna keep doing it. Fuck you.”

Similar to docker, but the technical differences matter a lot. VMs have a lot of capabilities containers don’t have, while missing some of the value on being lightweight.

However, a more direct (if longer) answer would be: all cloud providers ultimately offer you VMs. You can run docker on those VMs, but you have to start with a VM. Selfhosted stuff (my homelab, for example) will also generally end up as a mix of VMs and docker containers. So no matter what project you’re working on at scale, you’ve probably got some VMs around.

Whether you then use containers inside them is a more nuanced and subtle question.

They’re all scams. This one’s just more obvious.

EDIT: Noticed you’re talking about Gitlab in the question, and I responded about Github, but I’m certain that gitlab does everything the same way, because that’s all the technology is capable of. (I have no way to test the ssh -T command at the end for gitlab, though, so ymmv.)

To clear up some minor confusion here:

1. Github knows nothing about your private key. There’s very little metadata stored in the private key, and github.com has access to none of it. That includes email address or identity.
2. Github has identity information stored for you, and then, separately, you uploaded a public key. The public key also contains no information about you, but github knows it’s part of your account. Additionally, github enforces a requirement that your public key can’t be uploaded to any other account, for the reason I’m about to state below.
3. Github has an index built of everyone’s public keys (or more likely their digests, although the technical details of the index are not something known to me–and it doesn’t matter). When it sees an authentication request, it looks up the digest in the index, which maps to a user account.

At this point it already knows who is trying to authenticate. Once your authentication request succeeds with your public key (the usual challenge-response handshake associated with asymmetric cryptography), github interacts with your ssh client (most likely git) applying the permissions of your user and your user account.

BTW, github has a documented method for testing the handshake without doing any git operations:

ssh -T [email protected]

Depending on your ssh config, you might also need to supply -i some_filename.pem to this. Github will reply with

Hi aarkon! You've successfully authenticated, but GitHub does not provide shell access.

and then close the connection.

Note that the test authentication uses the username git and, again, contains no information about who you are. It’s all just looked up on github’s side.

You can infect a hospitalized patient with MRSA by paying off one (1) nurse, and I guarantee you can find a nurse who will play for cheap. At this point I’m 50/50 on whether the second whistleblower was murdered.

Well I didn’t see the comment you’re apologizing for so, no apology necessary ig?