I self-host a lot of stuff.
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil in a better timeline, i'd like the idea of neighborhood/community hosting. like, the local library doing it, with help of tech savvy volunteers. that would be wholesome
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil "It appears that “self-hosting” might mean different things to different people."
Definitely. We are able to do #selfhosting because we are local ISP for 25 years. We run our own datacenter from at least 8 years, and I was planning how to do the waste heat recycling for 10 years. We have access to second-hand hardware, because it would be hard to afford only the new hardware.
So #selfhosting is still collective activity of some kind, you need small business, or cooperative, or something, because you have expenses.
I suppose aggregating VPS-es for multiple instances on same physical hardware may have some advantages eg. with containers sharing the same ZFS filesystem (you can turn on eg. de-duplication of files)
So the #selfhosting usually anway about seeking some kind of cooperation. I would not be able to "selfhost" without cooperating with experienced admin...
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil
Do you recommend yunohost? -
@neil
Do you recommend yunohost?@unqualifiedtechbros I have no experience of it, I'm afraid.
-
@neil and you gotta hope the tools you’re using is actually secure
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil That is an excellent article.
I do think that you can self-host on someone else's computer, shrinking all the financial costs to a couple of small ones (hosting fee and domain name; just those are cheaper than having any kind of home internet connection).
I run a root server in the cloud, on an OpenStack instance. The entire machine is defined by me. I regard it as self-hosting.
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil And (I'm yet to read the full article, but) the upcoming raise in hardware prices will make the entry price on self-hosting even more complicated to reach -
@neil That is an excellent article.
I do think that you can self-host on someone else's computer, shrinking all the financial costs to a couple of small ones (hosting fee and domain name; just those are cheaper than having any kind of home internet connection).
I run a root server in the cloud, on an OpenStack instance. The entire machine is defined by me. I regard it as self-hosting.
@khleedril Great!
-
@neil in a better timeline, i'd like the idea of neighborhood/community hosting. like, the local library doing it, with help of tech savvy volunteers. that would be wholesome
@NocturnalNessa @neil We, in Russia had such thing before (and looks like will have in the future
), when the ISP prices were high and unaffordable for usual people, but there were a lot of coaxial cables and 10BASE2 (IIRC) network equipment on the market for a reasonable price. So, people just connected apartments and buildings with these cables and had a local network in the block (or between some blocks) for filesharing, gaming in local network, etc… Something like this: https://medium.com/@pv.safronov/moscow-state-university-network-built-by-students-211539855cf9 -
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil I think this summarizes why I'm suffering from more or less severe burnout symptoms on a daily basis.
When I'm done developing depressingly poor quality software projects designed to "generate" revenue for a greedy tech company for the day, I am expected to keep on top of the never-ending bot attacks against my self-managed services.
Every time I install a new kernel version or significant package updates, my anxiety peaks while I wait for machines and services - some of them being the backbone of my digital existence - to come back up.
I'd rather just pay for someone else to do it, but experience has shown that companies can't be trusted with anything anymore as increasing profits has become the driving force behind everything with quality and reliability being downgraded to a mere afterthought.
I hate that system and I hate being part of it but I have to pay my ever growing greed and inflation driven bills so what can I do?
-
As opposed to 'just pay the faceless corp instead of self-hosting.' This is notably not techno-libertarian at all, very inclusive, and the opposite of atomizing --
just look at Facebook and Twitter after all, they are the *Threads* that knit together our nations!!!If self-hosting shit is anything like a political statement, I'd say it's closer to anarchy than libertarianism.
@petko @neil @Colman Agreed. If you need something, like some black-box to share files with other people — you could just make something yourself with existing technical skills. Or organize with some other people with necessary skills and make a thing. This looks like some kind of anarchy and definitely not like "techno-libertarianism" lol.
The "how-to" knowledge is freely acessible and no one hides it with paywall — you can learn or get help from other people (for beer or money, etc) if you don't have a time/courage to learn.
-
@neil I think self-hosting is a bit like doing your own car servicing.
Sure, you can do it and if you know what you're doing you'll probably be happy and saving yourself some money - but unless you *actually* know what you're doing, many things can and will come back to bite you in the ass
Hell, I *do* know what I'm doing and I'm very happy to pay someone else to do quite a lot of things I could, theoretically, do myself.
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil Neil is absolutely spot on and we need to talk about the politics of this. Telling people to "just self-host" to escape surveillance capitalism is the exact same tactic as telling people to "calculate your carbon footprint" to stop climate change.
It individualizes a systemic, corporate failure.
Privacy and digital safety shouldn't be luxury goods reserved for cis-white-male engineers with unmetered fiber connections, rack-mount servers along with free time and financial stability to pull it off. When our response to the collapse of digital rights is "run your own infrastructure," we are engaging in digital redlining. The solution to predatory data brokering isn't forcing single mothers working two jobs to learn Kubernetes; the solution is ruthlessly regulating the data brokers out of existence. -
Thanks for sharing. This is useful info
-
I self-host a lot of stuff. Nearly everything that I use. FOSS and self-hosting is a massive part of my computing experience.
I love reading about people enjoying / exploring self-hosting stuff.
I struggle when people advocate "just self-host it", without giving due consideration to the costs, risks, security considerations, and so on.
I know that I've posted this a few times now, but this discussion seems to pop up quite a lot. So:
@neil
Sort of off-topic (and I agree that not everyone has the skillset/desire to self-host) but I followed your guide to upgrade my GlitchSoc instance and it was great. Thank you for posting it. -
@neil "It appears that “self-hosting” might mean different things to different people."
Definitely. We are able to do #selfhosting because we are local ISP for 25 years. We run our own datacenter from at least 8 years, and I was planning how to do the waste heat recycling for 10 years. We have access to second-hand hardware, because it would be hard to afford only the new hardware.
So #selfhosting is still collective activity of some kind, you need small business, or cooperative, or something, because you have expenses.
I suppose aggregating VPS-es for multiple instances on same physical hardware may have some advantages eg. with containers sharing the same ZFS filesystem (you can turn on eg. de-duplication of files)
So the #selfhosting usually anway about seeking some kind of cooperation. I would not be able to "selfhost" without cooperating with experienced admin...
-
@neil
Sort of off-topic (and I agree that not everyone has the skillset/desire to self-host) but I followed your guide to upgrade my GlitchSoc instance and it was great. Thank you for posting it.@fname I am so pleased - thank you!
-
@neil Neil is absolutely spot on and we need to talk about the politics of this. Telling people to "just self-host" to escape surveillance capitalism is the exact same tactic as telling people to "calculate your carbon footprint" to stop climate change.
It individualizes a systemic, corporate failure.
Privacy and digital safety shouldn't be luxury goods reserved for cis-white-male engineers with unmetered fiber connections, rack-mount servers along with free time and financial stability to pull it off. When our response to the collapse of digital rights is "run your own infrastructure," we are engaging in digital redlining. The solution to predatory data brokering isn't forcing single mothers working two jobs to learn Kubernetes; the solution is ruthlessly regulating the data brokers out of existence. -
@fname I am so pleased - thank you!
@neil
I used the official guide the first time I did it and managed to mash my way through, but yours was much easier to follow.
-
@neil
I used the official guide the first time I did it and managed to mash my way through, but yours was much easier to follow.@fname Excellent
