• 0 Posts
  • 24 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle
  • stevestevesteve@lemmy.worldtoProgrammer Humor@lemmy.mlcarrot.py
    link
    fedilink
    arrow-up
    22
    arrow-down
    1
    ·
    3 days ago

    “RTFM” My irritation is that most recipes make a huge amount of assumptions - at least as many as code that assumes a certain version of library. You can get recipes that say things as vague as “prepare the chicken” and aren’t at all clear what they mean, unless you’ve seen someone do it first, but it’s published in a book like you should just know. I hate that. I also frequently see quantities like “1 can” which just drives me insane as though that’s a standard unit.

    There’s also plenty of cooking specific jargon, so densely packed that beginners might spend the majority of the recipe looking up what the terms mean. “Chop” parsley - how finely? “Mix the ingredients” how long? What the fuck is Golden Brown actually?







  • AV1 and VP9 are likely going to be your highest efficiency “free” codecs. AV1 is the way to go if you mean free as in free open source. It’s not very likely to be implemented in many TVs or set-top-boxes, but VLC/ffmpeg will be able to decode any of these. Webm uses vp8 or VP9 which are “free”(made by Google) but it’s just more specific settings for sharing online/viewing in browser.

    H264/H265 has license fees for non-free software and hardware, but they will be your most widely supported option. H265 is approximately twice as efficient as h264 (meaning you can get the same quality of encode from half the file size).

    Regardless of preset I think you can get handbrake to encode something reasonable from any of these codecs. Especially with DVD video you’ll be able to crank through videos with modern high efficiency codecs


  • It certainly is. ISO 27001 is a framework, not very prescriptive at all. Basically an auditor will ask “how do you ensure data isn’t leaving your facility in the form of discarded hardware?” If you say “here’s a link to our media destruction policy. It says all drives are wiped according to NIST 800-88 cryptographic erasure. If that is not possible or not applicable, the drive is destroyed. Here’s our log of decomissioned equipment” chances are very good they’ll say “OK great let’s move on to the next one” with only minor followup questions.










  • As someone who also has 15+ years of experience in the field and is currently infosec management, it’s not that bad. Certainly not something I’d say “you’re in for a world of hurt” about like somebody just bought a bad timeshare.

    Especially if you’re not hosting production email for a company and you’re not leaving the server as an open relay, it isn’t very painful at all.

    You could also be less condescending, but as you said: your call. :)



  • I’m a huge supporter of open source, so Plex being closed alone makes it gross to me. Very little about Plex felt selfhosted.

    I also like to tinker a lot and jellyfin lets me screw around with much more under the hood - precise encoding settings, dlna customizations, I’m sure there’s more but the primary driver was ideology. I’m not giving my money to some company that’s primarily developing features I don’t want so that I can use my own media to the fullest.

    I’ve had very little issue with hardware accelerated encoding, but I already had the right drivers installed and on unix OSes that’s probably the hardest part