• 0 Posts
  • 22 Comments
Joined 11 months ago
cake
Cake day: July 31st, 2023

help-circle
  • 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 removeding 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.)





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




  • I’m not gonna read this person’s Evangelion analogy, but I did go to the trouble to hunt down what Jon Ringer actually did.

    Here’s a link.

    I don’t agree with him, and representation of particular minority groups, including gender minorities, are important when they are particularly under attack. It is important to actively resist the marginalization of groups under attack by elevating their voices.

    That said, I’m not sure what Jon did was actually “actionable”. I’d say, stop listening to him and treating him as a leader? As someone with lots of close trans friends, I think this guy lowkey sucks, but I think this suspension is weird.






  • This is incorrect. It’s true that most (in fact, I would say almost all) forks go nowhere but that doesn’t mean forking isn’t incredibly valuable. Even the example you cite, “original project is dead” isn’t just incidentally useful, it’s critical to open source. Other examples include:

    • project’s core team is part of a for profit org that is moving the project in a bad, profit motivated direction:
    • project’s leader suddenly and dramatically loses respect (maybe he killed his wife or something);
    • project’s leader dies without leaving a digital will regarding who controls the core repo;
    • project continues to direct effort into features while falling to address major security concerns;
    • project is healthy and useful in every way but there is an important use case not being addressed, and the fork would address it.

    Even if 99% of forks fail, that’s irrelevant because 99% of original projects fail in the same ways. Forks are critical to open source.




  • Do you know why Facebook paid a billion dollars for Instagram? Instagram wasn’t worth that much. It wasn’t generating a billion dollars in revenue. It probably still doesn’t.

    Facebook bought Instagram because Instagram was a growing app that was popular with a demographic Facebook wanted to control. They spent a billion dollars to eliminate a growing threat.

    Mastodon and, to a lesser extent, Lemmy, represent a growing threat. Not a very big one right now, but it could become a bigger one. It could become another billion dollar problem for the goliaths on the Internet, in a few years. They need to have total control, if a social media app starts to fragment it just collapses instead as users decide to go wherever the other users are.

    Facebook’s 1000:1 user ratio would make Lemmy irrelevant and stave off that billion dollar problem for Facebook down the road. An incredibly cheap way to kill a tiny but growing competitor.



  • Proxmox VE is a packaging of Linux as an operating system. It is a distribution. Straight from the wikipedia page:

    It is a Debian-based Linux distribution with a modified Ubuntu LTS kernel[7] and allows deployment and management of virtual machines and containers.[8][9]

    Cool way to respond to a comment btw:

    Am I taking crazy pills?

    The VMs I’m running in Proxmox are also Linux, but that’s less interesting to me.