• 1 Post
  • 35 Comments
Joined 1 year ago
cake
Cake day: June 5th, 2025

help-circle











  • I think you missed the point entirely. Yes, the thread is about weird flexes. Just yesterday there was a discussion in !selfhosted@lemmy.world about Plex, and a lot of people who run Jellyfin were saying running Plex isn’t selfhosting. A weird (to me) anti-Plex flex.

    OP asked for weird flexes. Weird flex in reply.

    So when you replied:

    hosting your own media server is just so weird

    You seem to be disparaging the hobby of selfhosted media servers. That’s why I responded as I did. I never said that I participate in that hobby at all, so I’m not sure why you think I’m the one doing the flexing here.

    I guess what you may be saying is that you don’t recognize “running a media server” as a hobby at all, but some kind of weird flex within the space of “I like movies.” I can see your point that in a conversation about “I like movies,” jumping in with “I run my own media server, akshully” could come off very negatively. I agree. There are a lot of self-congratulatory dingbats in that space. But that’s not what happened here.

    Open-ended question looking for weird flexes people have heard. Weird flex was provided.

    Have a nice day.






  • For your situation I would be more likely to go with a single drive with btrfs and dup for metadata redundancy. Regular snapshots and scrubs.

    Use a second drive in the same system with btrfs to store snapshots at wider scheduled intervals. These will be bigger since no CoW on the separate file system. Scheduled scrub here too.

    Use a third drive with ext4 as a backup target using a separate backup mechanism.

    Use the fourth drive as a spare, or in a separate location as a target to send the backups if you don’t already have an off-site solution.