archomrade [he/him]

  • 5 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle









  • Lots of good suggestions here

    I’m a bit surprised by your budget. For something just running plex and next cloud, you shouldn’t need a 6 or even 3k system. I run my server on found parts, adding up to just $600-$700 dollars including (used) SAS drives. It runs probably a dozen docker containers, a dns server, and homeassistant. I don’t even remember what cpu I have because it was such a small consideration when I was finding parts.

    I’d recommend keeping g your synology as a simple Nas (maybe next cloud too, depending on how you’re using it) and then get a second box with whatever you need for plex. Unless you’re transcoding multiple 4k videos at once, your cpu/GPU really don’t need much power. I don’t even have a dedicated GPU in mine, but I’m basically unable to do live 4k transcodes (this is fine for me)


  • If i’m understanding the last graph right, it’s showing the total number of active monthly users per instance’s top communities, filtered by the overall top 100 communities?

    So if an instance has activity spread out over many niche communities, that activity isn’t represented on this graph?

    I would think having a diversity of smaller communities is more in-line with the spirit of the fediverse, I’m not sure of the value in slicing the data in this way.









  • Thanks, corrected my comment above.

    I’m interested in ksmbd… I chose SMB simply because I was using it across lunix/windows/mac devices and I was using OMV for managing it, but that doesn’t mean I couldn’t switch to something better.

    Honestly though, I don’t need faster transfers typically, I just happen to be switching out a drive right now. SMB through OMV has been perfectly sufficient otherwise.


  • SATA III is gigabit, so the max speed is actually 600MB/s.

    My mistake, though still, a 4tb transfer should take less than 2hr at 5Gb/s (IN THEORY) Thank you @Max_P@lemmy.max-p.me for pointing this out a second time elsewhere: 6Gb/s is what the sata 3 interface is capable of, NOT what the DRIVE is capable of. The marketing material for this drive has clearly psyched me out, the actual transfer speed is 210Mb/s

    The filesystem is EXT4 and shared as a SMB… OMV has a fair amount of ram allocated to it, like 16gb or something gratuitous. I’m guessing the way rsync does it’s transfers is the culprit, and I honestly can’t complain because the integrity of the transfer is crucial.




  • My understanding is that it’s a combination of correctly deploying authentication (DMARC, DKIM, and SPF) and the actual IP address of the server that can get you into trouble. If you incorrectly set up authentication, OR if a malicious sender spoofs you (likely because you didn’t set up auth correctly), it can get your IP blocklisted. And unless you’re monitoring if you’re blocklisted, you often don’t know that things aren’t getting delivered until someone tells you.

    And then you’re still kind of at the whim of the big players, because they could change or update their authentication standards, and if you’re not on top of it you can find yourself in the same boat, even if you’re doing everything else right.

    It’s not impossible, it’s just a headache. But if i’m being honest, i’m a bit of a novice so it could be easier to a more trained network administrator.


  • I edited the comment, I really meant hosting server, not domain.

    Having a custom domain isn’t a big deal, it’s really where that domain is hosted that creates forwarding issues. Since the majority of email is handled by the ‘big three’, anything that’s hosted outside of that is often flagged as spam or is refused to be delivered. That’s allegedly because there are malicious senders also hosted on third party servers (and fair enough, there likely are), but this causes a bit of a potential monopoly that could easily be abused, and there’s obvious motivation to push people into a particular service for data collection.

    Even if it doesn’t happen often, occasional failures can be a huge problem if you’re sending critical communication and it isn’t reaching target inboxes because of filtering. It’s enough of a headache that even most avid self-hosters tend to avoid it.