Technology

37739 readers

766 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

alyaza@beehaw.org

TheRtRevKaiser@beehaw.org

gyrfalcon@beehaw.org

rs5th@beehaw.org

Los@beehaw.org

coldredlight@beehaw.org

SemioticStandard@beehaw.org

TheRtRevKaiser@kbin.social

remington@beehaw.org

I don't think "command line hard" is the worst part of self-hosting. (beehaw.org)

submitted 1 year ago by mtset@beehaw.org to c/technology@beehaw.org

47 comments fedilink hide all child comments

I've seen a lot of people saying things that amount to "those tech nerds need to understand that nobody wants to use the command line!", but I don't actually think that's the hardest part of self-hosting today. I mean, even with a really slick GUI like ASUSTOR NASes provide, getting a reliable, non-NATed connection, with an SSL certificate, some kind of basic DDOS protection, backups, and working outgoing email (ugh), is a huge pain in the ass.

Am I wrong? Would a Sandstorm-like GUI for deploying Docker images solve all of our problems? What can we do to reshape the network such that people can more easily run their own stuff?

you are viewing a single comment's thread
view the rest of the comments

[–] aksdb@feddit.de 8 points 1 year ago (1 children)

The sad truth is that non-techy types will never want to host something themselves unless there’s a reason why doing so is better.

Not even techy types want it. It's not a coincidence that SaaS offerings are viable in enterprise contexts. Why build a shit ton of knowledge and drag yourself through the mud of learning tons of different tools if you can as well pay someone who already has all that knowledge. Then you can use the free mental capacity to solve your actual problems.

The only reasons to self host are "paranoia" (no matter if warranted or not) and - which is the important thing for us self-hosters here - curiosity (or rather the drive to learn shit). We basically do it for the sake of doing it.

[–] freeman@lemmy.pub 2 points 1 year ago (1 children)

That’s true. Though I would sub paranoia with control.

I self host things because I want control. I want to be in control of when it gets updates and goes down. I want to be in control of how to fix it when it breaks. I want to be in control of my account and whether it’s backed up etc.

[–] aksdb@feddit.de 1 points 1 year ago* (last edited 1 year ago) (1 children)

I thought of that as well but concluded that this is also some kind of paranoia. The SaaS providers promise you availability, security etc, but don't believe them and want that in our own hands. So IMO we only want to be in control, because we fear we could suddenly lose access or get betrayed. Which is a specific manifestation of paronia.

[–] freeman@lemmy.pub 2 points 1 year ago

Fair point.