• 1 Post
  • 60 Comments
Joined 2 years ago
cake
Cake day: June 15th, 2023

help-circle


  • "Imagine appearing for a job interview and, without saying a single word, being told that you are not getting the role because your face didn’t fit. You would assume discrimination, and might even contemplate litigation. But what if bias was not the reason?

    Uh… guys…

    Discrimination: the act, practice, or an instance of unfairly treating a person or group differently from other people or groups on a class or categorical basis

    Prejudice: an adverse opinion or leaning formed without just grounds or before sufficient knowledge

    Bias: to give a settled and often prejudiced outlook to

    Judging someone’s ability without knowing them, based solely on their appearance, is, like, kinda the definition of bias, discrimination, and prejudice. I think their stupid angle is “it’s not unfair because what if this time it really worked though!” 😅

    I know this is the point, but there’s no way this could possibly end up with anything other than a lazily written, comically clichéd, Sci Fi future where there’s an underclass of like “class gammas” who have gamma face, and then the betas that blah blah. Whereas the alphas are the most perfect ughhhhh. It’s not even a huge leap; it’s fucking inevitable. That’s the outcome of this.

    I should watch Gattaca again…


  • psycotica0@lemmy.catoTechnology@lemmy.worldPasskeys Explained: The End of Passwords
    link
    fedilink
    English
    arrow-up
    18
    arrow-down
    1
    ·
    edit-2
    14 days ago

    Technically they are the 2fa. The second factor is something you have. I store all my passkeys in my password manager too, so I’m not faulting you, but technically that’s just undoing the second factor, because now my two factors are “two things that are both unlocked by the same one thing I know”. Which is one complicated factor spread across two form fields.


  • And for beginners, a flatpak is a particular way of bundling software so that:

    A) all of the dependencies come with the program so you can just download one thing and run it

    and

    B) it has some level of sandboxing, which means you have some level of control over what the software you downloaded has access to on your machine. In theory.

    So what they’re saying is that if some software you want isn’t already bundled as a flatpak, you’re going to have a hard time with bazzite, as it’s geared around making flatpaks easy, and requires more work to install things using other methods. Still works, just not as easy.





  • Uhmmmm, pretty sure it’s worse than that. My understanding of the term is that it comes from cars, where cheaper Asian cars were entering the American market and were called “rice burners” (racistly), and I’m pretty sure from there the concept of decking out a cheap car with spoilers and ground kits and a wild paint job and stuff was called “ricing” because it was a thing in the Asian communities. As in “ricing a car” is “doing what an Asian would do to that car, and you know how they’re all about rice”

    I’d be happy to be wrong here… but I think that’s the history on that word.




  • git log will only show you commits in your history. If you’re only ever working forwards, this will contain all the stuff you’ll ever need.

    But if you’re rewriting history, like with a rebase or squash or something, or you’re deleting branches without merging them, then you can run into a situation where the official history of your branch doesn’t contain some of the commits that used to exist, and in fact still exist but are unlinked from anywhere. So reflog is the log of where you’ve been, even if where you’ve been isn’t in the official history anymore, so you can find your way back to previous states even if there isn’t otherwise a name for them.

    If all you care about is your current history, git can use the dates of commits just fine to see where you were on Thursday without needing the reflog.


  • Maybe I’m just a wizard, or I don’t know what y’all are talking about, but rebases aren’t special. If you use git reflog it just tells you where you used to be before the rebase. You don’t have to fix anything, git is append only. See where the rebase started in reflog, it’ll say rebase in the log line, then git reset --hard THAT_HASH

    Pushing without fetching should be an error. So either they got the error, didn’t think about it, and then force pushed, or someone taught them to just always force push. In either case the problem is the force part, the tool is built to prevent this by default.

    Continuing after merge should be pretty easy? I’d assume rebase just does it? Unless the merge was a squash merge or rebase merge. Then yeah, slightly annoying, but still mostly git rebase -i and then delete lines look like they were already merged?








  • Okay hang on. Yes, Ice Ice Baby and Under Pressure don’t have a lot of notes in common, in terms of absolute note count, but when the songs come on, the layperson doesn’t know which is which. Any normal person would listen to 10 seconds of Ice Ice Baby and go “oh yeah, that’s Under Pressure by Queen”.

    So yeah, if there’s a prompt that people can use to trick an AI into spitting out a chapter verbatim that’s interesting, but I would say minor infringment. No one is going to read a Ton Clancy novel by systematically tricking the AI to spit out each entire chapter one after the other, and it’s presented to essentially an audience of one, the promoter.

    But if I was to take that chapter, the one it spit out verbatim, and put it as a chapter of my book that I published, then yeah, definitely I could be sued for copyright, even if I didn’t do it willingly. Because people would read it and go “oh totally, that’s Pelican Brief”