• 0 Posts
  • 266 Comments
Joined 5 months ago
cake
Cake day: June 9th, 2024

help-circle

  • I’m not sure I buy that: Trump is a cult, and his cultists are going to have an absolute riotous fit if someone tries to depose him.

    Short of him dying or doing something you just can’t ignore - like, say, he eats shit out of his diaper on national tv - he’s not going anywhere.

    Vance isn’t smart enough to 6D chess his way into the presidency without his nominal constituency rioting over it, so I’m doubtful that’s his play.

    He’s probably just going to pull the last-guy-in-the-room thing, since that’s the only person Trump listens to or remembers anyway which means you keep the cultists happy AND you get the figurehead to do what you want anyways without the mess.



  • Mastodon is, like, fine, but it has one gaping flaw that makes it utterly unusable for me.

    Basically, the issue is you cannot be assured that any particular instance contains the entire conversation thread/replies, because they’re not necessarily sent to every server participating in the conversation.

    Bluesky fixes that by the ‘firehose’ feeds federating out to the PDSes and providing complete reply chains, which just flat out makes it a better experience since you can actually see what everyone is saying, not just what people on servers you might be following already are saying.

    It’s a giant stupid flaw in Mastodon (since other AP based platforms such as, for example, Lemmy don’t have it) and really should be addressed since it makes the platform darn near useless since why am I following people to only get half of what might be a useful thread?











  • good ideia to run restic as root

    As a general rule, run absolutely nothing as root unless there’s absolutely no other way to do what you’re trying to do. And, frankly, there’s maybe a dozen things that must be root, at most.

    One of the biggest hardening things you can do for yourself is to always, always run everything as the lowest privilege level you can to accomplish what you need.

    If all your data is owned by a user, run the backup tool as that user.

    If it’s owned by several non-priviliged users, then you want to make sure that the group permissions let you access it.

    As a related note, this also applies to containers and software you’re running: you shouldn’t run docker containers as root unless they specifically MUST have a permission that only root has, and I personally don’t run internet facing ones as the same user as all the others: if something gets popped, then they not only do not have root permissions, but they’re also siloed into their own data in the event of a container escape.

    My expectation is that, at some point, I’ll miss a CVE and get pwnt, so the goal is to reduce how much damage someone can do when that happens, rather than assume I’m going to be able to keep it from happening at all, so everything is focused on ‘once this is compromised, how can i make the compromise useless to the attacker’.


  • Unifi Gateway Ultra

    How have you liked the gateway? Any stupid decisions that have annoyed?

    My USG has decided that, after a decade, it’s going to be flaky and crash if it wants to (even after replacing it’s 4th dead PSU and 2nd USB stick) and I’m thinking it’s probably time to upgrade.

    I’ll admit to both liking the Unifi ecosystem and firmly not trusting the Unifi ecosystem one damn bit, which is bit of a weird situation where I’ve been really really unwilling to upgrade anything because that hasn’t always gone uh, smoothly.






  • And it doesn’t mean they can take away anything.

    Not if they’re able to monetize your small bugfix

    The problem is they can, and that’s not the point - I don’t care if you make money with something I spent my time on willingly, I care that you’re forcing me to say you’re the full and sole owner of my contributions and can do whatever you want at any point in the future with them.

    Signing a CLA puts the full ownership of the code in the hands of whomever you’ve signed the CLA with which means they have the full ability and legal right to do any damn thing they want, which often includes telling you to fuck yourself, changing the license, and running off to make a commercial product while both killing the AGPLed version, and fucking everyone who spent any time on it.

    If you have a CLA, I don’t care if your project gives out free handjobs: I don’t want it anywhere near anything I’m going to either be using or have to maintain.

    And sure you can fork from before the license change, but I’m unwilling to put a major piece of software into my workflows and hope that, if something happens, someone will come along and continue working on it.

    Frankly, I’m of the opinion that if you’re setting up a project and make the very, very involved decision to go with a CLA and spend the time implementing one, you’re spending that time because you’ve already determined it’s probably in your interests later to do a rugpull. If you’re not going to screw everyone, you don’t go to the store and buy a gallon of baby oil.

    I’ve turned into the person who doesn’t really care about new shit until it’s been around a decade, has no CLAs, and is under a standard GPL/AGPL license (none of this source-available business license nonsense), and has a proven track record of the developers not being shitheads.