• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: July 31st, 2023

help-circle
  • I have a very cynical reason. If you look at what most religions say about it (against), you have to wonder why they all agree on it and it seems to me that if you off yourself, you’re not supporting the team. When there weren’t many humans, you really needed a bunch of team players on your religion making more babies, and the dead ones can’t carry out your crusades.

    Now we put capital above religion, but it’s the same thing: we need workers for our factories. We need babies to become workers for our factories. Dead people can’t make cars or babies.





  • Mostly it’s just CYA for google since cycling is more dangerous than driving (due to the people driving), so there’s more surface area for them to get sued.

    But yeah

    • turns and crossings that look safe on a map don’t have very much data on whether they’re actually safe, because google has a thousand times as much information about drivers than cyclists.
    • google sometimes suggests routes that can’t be traversed, legally or at all, by a bike. Same reason.
    • sometimes google suggests avoiding something a bike doesn’t actually have to worry about. This is actually the category of error I see the most: google sends you around something when you could simply walk your bike through it, or ride through it, because you’re not a car.

  • Linus is the leader of the kernel project. As a leader, it’s his job to get the maintainers to agree. It’s not Rust’s job to make the C devs stop bullying them.

    If Linus thinks Rust is a good direction, he should show it by actually standing up to Ted and developers like him and making them behave.

    If he doesn’t think it’s a good direction, he should say that too, so the remaining Rust devs can stop wasting time on the project.

    When someone in a niche part of the project steps down like this, that’s a problem with the top-level leadership. Linus’ record on leadership is… mixed. Trending in a good direction the last few years, but this makes me wonder. He can still save this, but he has to want to.


  • Bcachefs has all of this. And it’s supposed to be faster than ZFS and btrfs. In a few years it can really be the golden Linux filesystem recommended for everybody

    ngl, the number of mainline Linux filesystems I’ve heard this about. ext2, ext3, btrfs, reiserfs, …

    tbh I don’t even know why I should care. I understand all the features you mentioned and why they would be good, but i don’t have them today, and I’m fine. Any problem extant in the current filesystems is a problem I’ve already solved, or I wouldn’t be using Linux. Maybe someday, the filesystem will make new installations 10% better, but rn I don’t care.










  • 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.)



  • Absolutely none of this is true.

    1. Alzheimer’s is only one specific disease that leads to rapid mental breakdown. There are many forms of senility, all of which including Alzheimer’s become more likely as you get older, which means that
    2. There is absolutely a strong correlation between age and degraded mental facilities. If I gave you three citations I’d be leaving out hundreds more citations.
    3. There won’t be a scientific breakthrough that doubles the average lifespan of every human on earth. There are so many flaws with this idea it’s exhausting just to think about it.
    4. Mandatory retirement ages are in use all over the place. Judicial appointments have this in place already in 18 states. Executive boards can legally have this rule in place as well. Any situation where old age in a job is a safety issue creates an exception in the form of an unmet bona fide occupational qualification. I would definitely argue that old men who create policy for hundreds of millions of people create a safety risk for those people if they aren’t mentally qualified to do the job.


  • 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 git@github.com
    

    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.