• 3 Posts
  • 548 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?














  • I mean, recovery from parity data is how all of this works, this just doesn’t require you to have a controller, use a specific filesystem, have matching sized drives or anything else. Recovery is mostly like any other raid option I’ve ever used.

    The only drawback is that the parity data is mostly equivalent in size to the actual data you’re making parity data of, and you need to keep a couple copies of indexes since if you lose the index or the parity data, no recovery for you.

    In my case, I didn’t care: I’m using the oldest drives I’ve got as the parity drives, and the newer, larger drives for the data.

    If i were doing the build now and not 5 years ago, I might pick a different solution but there’s something to be said for an option that’s dead simple (looking at you, zfs) and likely to be reliable because it’s not doing anything fancy (looking at you, btrfs).

    From a usage (not technical) standpoint, the most equivalent commercial/prefabbed solution would probably be something like unraid.


  • A tool I’ve actually found way more useful than actual raid is snapraid.

    It just makes a giant parity file which can be used to validate, repair, and/or restore your data in the array without needing to rely on any hardware or filesystem magic. The validation bit being a big deal, because I can scrub all the data in the array and it’ll happily tell me if something funky has happened.

    It’s been super useful on my NAS, where it’s the only thing standing between my pile of random drives and data loss.

    There’s a very long list of caveats as to why this may not be the right choice for any particular use case, but for someone wanting to keep their picture and linux iso collection somewhat protected (use a 321 backup strategy, for the love of god), it’s a fairly viable option.