Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)S
Posts
3
Comments
137
Joined
3 yr. ago

  • The transparency is the feature that makes it great. I can buy drugs or whatever, and exchange you buy an NFT from me of equal value. Now when the bank comes and says “where did this >$15k transaction come from?” I can point to the blockchain and say that I sold my fancy monkey pic.

    This has been a thing in the physical art world for a while, https://complyadvantage.com/insights/art-money-laundering/, this just made it easier.

  • Is there a cannonball sized hole in its chest where the sunlight comes through?

  • My team runs an async standup on Slack where you just respond to a bot with all the usual stuff. We also do a slightly longer meeting on Tuesday morning where we go into more details, but never more than a half-hour.

  • Yeah, these indictments are absolutely devastating to Hunter Biden’s presidential campaign.

  • You’re on the right track here. Longhorn kind of makes RAID irrelevant, but only for data stored in Longhorn. So anything on the host disk and not a PV is at risk. I tend to use MicroOS and k3s, so I’m okay with the risk, but it’s worth considering.

    For replicas, I wouldn’t jump straight to 3 and ignore 2. A lot of distributed storage systems use 3 so that they can resolve the “split brain” problem. Basically, if half the nodes can’t talk to each other, the side with quorum (2 of 3) knows that it can keep going while the side with 1 of 3 knows to stop accepting writes it can’t replicate. But Longhorn already does this in a Kubernetes native way. So it can get away with replica 2 because only one of the replicas will get the lease from the kube-api.

  • Yeah. I’m really curious what this person is standing for here.

  • Longhorn is basically just acting like a fancy NFS mount in this configuration. It’s a really fancy NFS mount that will work well with kubernetes, for things like PVC resizing and snapshots, but longhorn isn’t really stretching its legs in this scenario.

    I’d say leave it, because it’s already setup. And someday you might add more (non-RAID) disks to those other nodes, in which case you can set Longhorn to replicas=2 and get some better availability.

  • Maybe try for something more appropriate for your experience so far that demonstrates you branching out into higher skills. CKAD for example.

  • What kind of job are you looking for?

    A+ is for help desk type folks. I wouldn’t really see that as relevant for a developer with 8 years of experience. I would assume you got it early in your career and still list it for whatever reason.

  • The biggest danger you’re going to run into is that those distros all lie downstream of the real changes, so non-gaming (and potentially security related) fixes might be slow or incompatible.

    If you go with something like Fedora or Ubuntu, there is going to be full support on all the core things, and you can build the gaming experience you want on top. Any changes that Nobara or Drauger are making to their distros you could probably make yourself.

    (I’ve never used any of those distros, but I’ve found winehq and other tools on Fedora more than sufficient)

  • Can you easily switch drives in your system? I’ll often do that on my computer because little m.2 SSDs are so darn cheap now. It’s easier and cheaper to pick up a little 64GB drive for one off projects than it is to do a proper backup and restore.

    Also, I’d just go with Tumbleweed. I don’t distro hop like I used to, but that’s because as everyone else is saying, most of the distros have gotten really good. Most of the time, my little projects are trying out specific features of a different distros. So I’ll just pop a new drive in, test drive it, then either switch back or not.

  • Also, all of us have done things because we didn’t know better. The only dumb thing to do here is to not learn how to fix this. Try and fail, so next time you know how it works and can do better.

  • Unless it was encrypted, it prob doesn’t matter. The partition table is just the road map that points to the houses (files). A tool like FTK or PhotoRec goes byte by byte to find the files and figure out what they are. You won’t have file names, but the data might still be there.

  • It sounds like you need to learn about disk forensics before you go any further. Check out FTK

  • I’d say he’s only rough on them if they don’t take food safety seriously or they don’t want to learn.

  • I’ve been playing around with MicroOS, which is based off of OpenSUSE and is supposed to be the successor to RancherOS

  • Last week, when Carlos and Lando were the ones with older tyres, the plan worked though. That was why it was so impressive. It’s a bit embarrassing that two drivers from different teams can work together better than the two Mercedes drivers.

  • If you want to build a new container on top of nginx, that will serve a static site like a champ

  • Forget? They chose their favorite and if he wanted it to be him he should have done better in quali, or at least pull ahead of the two drivers ahead of him on medium tires.