[–] 2 points 2 days ago* (1 child)

smartctl --scan | awk '{print $1}' | xargs -I {} sh -c 'echo -n "{}: "; smartctl -A {} | awk "/Power_On_Hours/ {printf \"%.2f years\n\", \$10/8760}"'

/dev/sda: 0.30 years #14TB WD Elements (shucked)
/dev/sdb: 2.64 years #8TB WD My Book (shucked)
/dev/sdc: 12.37 years #3TB WD Red
/dev/sdd: 2.86 years #12TB My Book (shucked)
/dev/sde: 13.47 years #3TB WD Red
/dev/sdf: 1.26 years #14TB WD Elements (shucked)
/dev/sdg: 10.55 years #5TB WD Red

Most of these drives served on Windows Server bare metal w/ StableBit DrivePool + SnapRAID before migrating to Proxmox mergerfs + SnapRAID & ZFS. My raidz1 pool has a combine total of 36+ years lol. Yes I do have backups. :)

  • source
  • [–] 1 point 3 months ago

    Duplicacy has a -nobackup-file option, documented with the set cmd.

    Some of your other info about Duplicacy is very obviously wrong or out-of-date. Stop relying on AI for research. :)

  • source
  • [–] 9 points 5 months ago*

    The source can be found here: https://terrorismlegislationreviewer.independent.gov.uk/ (direct link)

    It's an independent report by Jonathan Hall KC presented to parliament. I think everyone is under the impression that those highlighted paragraphs are a statement of law, they're not. But they are the guy's (correct) interpretation of existing law - namely, Schedule 3 of the Counter-Terrorism and Border Security Act 2019.

    The report itself is a good thing, coz now we know how far the UK government will try to stretch their powers and what we need to repeal when Labour (and the Tories) fucks right off.

    As part of his summary:

    Some of the powers and offences extend well into the zone of political activity,
    journalism, protest and day-to-day human activity. However useful, they must
    be tested against misuse and overreach.
    
  • source
  • parent
  • context
  • [–] 2 points 7 months ago

    Plex was running on his private computer, not a dedicated server, right?

    They opened it to the internet - that's the big difference (and the topic at hand). Security is a multi-layered thing, but if your weakest point is a gaping hole, the rest doesn't mean much. To my point - assuming Jellyfin ain't gonna have vulnerabilities even when you're fully up-to-date, is foolhardy.

  • source
  • parent
  • context
  • [–] 1 point 7 months ago

    Yea I haven't tried Pangolin myself - looks a bit bloated for my tastes, but I have tried rinetd across Tailscale and it worked brilliantly (very simple conf file), and I've done reverse ssh before (using autossh) which was a bit fiddly. frp does look promising though, just as a VPS<->home bridge.

  • source
  • parent
  • context
  • [–] 7 points 7 months ago* (last edited 7 months ago) (4 children)

    This video addresses many of the concerns of hosting stuff in public, and details a way (and some tools) to do it relatively securely. (There's always a risk there'll be a zero-day vulnerability in a web application like Jellyfin, but you can mitigate against them if you use the right strategies/tools, and you're vigilant enough.)

    Since you're on cgnat, you can set up Pangolin on a VPS, or Tailscale-->rinetd-->Tailscale tunnel, also on a VPS. (Apparently frp is another similar solution, with p2p proxying.)

  • source
  • [–] 7 points 9 months ago (1 child)

    Yes I read it when it first came out, and again after a recent update. It's very opinionated and I remain unconvinced the criticisms amounts to very much. At the least, certainly not to the point where words like nazi and fascist should be thrown around!

    For example, I dislike Yarin's and Lunduke's politics but I did at least watched Yarin's interview. (Did you? It was boring, and entirely tech-oriented, nothing controversial at all.) But... trial by association I guess. And anyway, it's not the article itself I have a problem with - it's the borrowing of second-hand opinions as if they should be your own. Sometimes, it's prudent to reserve judgement (until 'verifying every single thing'), or criticise specific ideas, without leaping to ad hominem per consortium.

  • source
  • parent
  • context
  • view more: next ›