@mayintoronto Assumptions: you know how to run a linux machine, install packages, troubleshoot issues, &c. You know how to punch traffic through your residential router to go to that device. You know how to use DNS or at least how to find a service to do DNS for you, or are comfortable with memorizing a periodically-changing numeric address. You are okay with the occasional flood of traffic from search engines and AI scrapers.
Discussion
Loading...
@mayintoronto Like, it fucking sucks, but the people who built the damned thing do all of this for a living anyways and so it is "easy" for them (it's me, hi, I'm the problem here, it's me, too).
@mayintoronto The folks in your replies talking about community run services and coops are probably the closest to a practical and meaningful option in this area - and in point of fact I think a lot of the push for self-hosting (specifically, to the exclusion of other non-corporate technical operations) is underpinned by the latent libertarianism that infects a lot of tech spaces.
@mayintoronto In that model, people who have built the skillsets that make this "easy" (hi) can turn that to their community's benefit, with some kind of interpersonal and relational accountability (vs. going and working at a venture-funded SaaS business, where accountability is deliberately excised).
@owen Sounds like a great worker owned co-op opportunity.
@mayintoronto @owen yes, running these things as a cooperative, on top of or in addition to compute as a public utility would be ideal
@jenniferplusplus @mayintoronto @owen I have wanted to do this for a few years. Ideal thing would be public infrastructure, but absent that, coop would be good too.
Currently run a small cluster with silly good battery backup in my basement because it was savings over cloud. For the foreseeable, this is even more savings, but definitely interested in formalizing this as a node in a coop.