257
[-] DasFaultier@sh.itjust.works 57 points 7 months ago

I still don't understand sports fans and how they interact with each other.

"Did you see that ludicrous display last night?"

[-] DasFaultier@sh.itjust.works 104 points 7 months ago

"Age" and "H" sound alike, so when the Doc wants to know the patient's age, the patient thinks the Doc wants help with spelling the name.

[-] DasFaultier@sh.itjust.works 132 points 9 months ago

Well I mean, we're all just mostly LARPing this whole adult thing, right?

[-] DasFaultier@sh.itjust.works 100 points 10 months ago

Whole place was crawling with pussy.

[-] DasFaultier@sh.itjust.works 64 points 10 months ago

If it's a Corgi, I would estimate the power output at .1 horsepower max. But if it's a small dog the size of a large dog, then that's something entirely different.

[-] DasFaultier@sh.itjust.works 59 points 11 months ago* (last edited 11 months ago)

You're asking the right questions, and there have been some great answers on here already.

I work at the crossover between IT and digital preservation in a large GLAM institution, so I'd like to offer my perspective. Sorry of there are any peculiarities in my comment, English is my 2nd language.

First of all (and as you've correctly realizes), compression is an antipattern in DigiPres and adds risk that you should only accept of you know what you're doing. Some formats do offer integrity information (MKV/FFV1 for video comes to mind, or the BagIt archival information package structure), including formats that use lossless compression, and these should be preferred.

You might want to check this to find a suitable format here: https://en.wikipedia.org/wiki/List_of_archive_formats -> Containers and compression

Depending on your file formats, it might not even be beneficial to use a compressed container, e.g. if you're archiving photos/videos that already exist in compressed formats (JPEG/JFIF, h.264, ...).

You can make your data more resilient by choosing appropriate formats not only for the compressed container but also for the payload itself. Find significant properties of your data and pick formats accordingly, not the other way round. Convert before archival of necessary (the term is normalization).

You might also want to consider to reduce the risk of losing the entirety of your archive by compressing each file individually. Bit rot is a real threat, and you probably want to limit the impact of flipped bits. Error rates for spinning HDDs are well studied and understood, and even relatively small archives tend to be within the size range for bit flips. I can't seem to find the sources just now, but iirc, it was something like 1 Bit in 1.5TB for disks at write time.

Also, there's only so much you can do against bit rot on the format side, so consider using a filesystem that allows you to run regular scrubs and so actually run them; ZFS or Btrfs come to mind. If you use a more "traditional" filesystem like ext4, you could at least add checksum files for all of your archival data that you can then use as a baseline for more manual checks, but these won't help you repair damaged payload files. You can also create BagIt bags for your archive contents, because bags come with fixity mechanisms included. See RFC 8493 (https://datatracker.ietf.org/doc/html/rfc8493). There are even libraries and software that help you verify the integrity of bags, so that may be helpful.

The disk hardware itself is a risk as well; having your disk laying around for prolonged periods of time might have an adverse effect on bearings etc. You don't have to keep it running every day, but regular scrubs might help to detect early signs of hardware degradation. Enable SMART if possible. Don't save on disk quality. If at all possible, purchase two disks (different make & model) to store the information.

DigiPres is first and foremost a game of risk reduction and an organizational process, even of we tend to prioritize the technical aspects of it. Keep that in mind at all times

And finally, I want to leave you with some reading material on DigiPres and personal archiving on general.

I've probably forgotten a few things (it's late...), but if you have any further questions, feel free to ask.

EDIT: I answered to a similar thread a few months ago, see https://sh.itjust.works/comment/13922388

[-] DasFaultier@sh.itjust.works 103 points 1 year ago

"Home thinking kills the AI industry."

"You wouldn't imagine a pair of juicy titties."

[-] DasFaultier@sh.itjust.works 63 points 1 year ago

You know, I said a similar thing about Brexit. To a British person. In their face. While being way less intoxicated than I care to admit. And she replied a thing that still resonates with me to this day. She said that I have to remember that there were a significant number of people who didn't vote Leave, and they're now being fucked over as well. They didn't want that, they didn't vote for that, and yet they still have to live with the consequences. And leaving the country is not an option for most people.

Remember that when you talk about what "y'all Texans" voted for. Have some empathy and compassion for the people that did the right thing and still have to live through this shit now. Learn from my mistake.

It's been, idk, six years or something since, and I still cringe at least once a week thinking about how ignorant I was. Never had/took the chance to apologize either.

252

... with one ear clearly out of place.

[-] DasFaultier@sh.itjust.works 58 points 1 year ago

Also, taxes aren't theft. You get something in return for it, usually services and infrastructure. Dad didn't give anything back for the stolen Duplos. Says my dog.

(Oh, and please tell your dog I said hi.)

[-] DasFaultier@sh.itjust.works 77 points 1 year ago

This was a helluva ride!

95
submitted 1 year ago* (last edited 1 year ago) by DasFaultier@sh.itjust.works to c/selfhosted@lemmy.world

Hey everyone,

I'm looking for a system that:

  • I can self host
  • Is slim, because I don't have beefy hardware (Intel J5040, 32GB RAM, shared by all VMs/containers)
  • can be used to create an inventory of all the tech/hardware that I have in my house (not exclusively IT, I also wasn't to track things like warranty for my chainsaws and the like)
  • does take at least the device make/model, serial number (for insurance cases) and warranty dates
  • is not some kind of enterprise-how-many-items-of-this-article-do-i-have-in-stock-things, because that seems to be the only thing I seem to be able to find, and they neither match my use case nor do they seem to be lightweight enough.

... and honestly, I don't even know where to start looking. Do you guys have any recommendations?

Of course, I could just use a spreadsheet, but where's the fun in that?

EDIT: Thank you all so much for the engaged discussion and all the suggestions, you're the best!

27
Shoutrrr alternative (sh.itjust.works)

Basically the title. I was trying Beszel monitoring, which supports alerting via Shoutrrr, but with Shoutrrr being an abandoned project, are there any well-maintained forks that the community has agreed to use?

If not, what are your recommendations? In familiar with all things sysadmin, but I'm new to notification tools, hence me asking. Bonus points for single binary deployment and frugal use of resources; I'm sick of running a stack of fat container images. Boring is good.

Thank you everyone!

[-] DasFaultier@sh.itjust.works 134 points 1 year ago

See, as a German, when I see a country go down the same route as the Weimar Republic after handing over the power to the Nazi party, I think it's just very obvious. Hitler took some two months to completely destroy democracy, and the US are juuust in the middle of that. History doesn't repeat, but sometimes it rhymes, and the similarities are just remarkable.

So yeah, I guess that would be a big fat trench in the sand.

234
Lotta loves the snow (sh.itjust.works)
view more: next ›

DasFaultier

0 post score
0 comment score
joined 2 years ago