• Encrypt-Keeper@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    7 months ago

    Oh yeah like that’s part of it. If this article is supposed to be a call to action, somebody who starts looking into “homelabs” is going to get confused, they’ll get some sticker shock, and they won’t understand how they apply to what’s said in the article. They’ll see a mix of information from small home servers to hyperconverged infrastructure, banks of Cisco routers and switches, etc. my first home lab was a stack of old Cisco gear I used to study for my network engineering degree. If you stumbled upon an old post of mine talking about my setup and all you’re looking for is a Plex box you’ll be like “What the fuck is all this shit, I’m not trying to deal with all that”

    “Self hosting”, and “home server” are just more accurate keywords to look into and actually see things more closely related to what you want.

    • jj4211@lemmy.world
      link
      fedilink
      English
      arrow-up
      1
      ·
      7 months ago

      Yep, and I see evidence of that over complication in some ‘getting started’ questions where people are asking about really convoluted design points and then people reinforcing that by doubling down or sometimes mentioning other weird exotic stuff, when they might be served by a checkbox in a ‘dumbed down’ self-hosting distribution on a single server, or maybe installing a package and just having it run, or maybe having to run a podman or docker command for some. But if they are struggling with complicated networking and scaling across a set of systems, then they are going way beyond what makes sense for a self host scenario.