Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
The thing you’re overlooking is that for a lot of the people hosting small instances, this is a hobby.
Speaking for myself, the cost of a domain is basically nothing, and adding Lemmy to my hosting setup was zero - I already have more ram, cpu, and disk space than I’d ever need for this instance.
Financial incentives are not the only thing people care about, and until relatively recently weren’t the general default purpose of online social spaces.
Ok, sure. But what if your instance became popular and started costing you hundreds per month? Or in a couple years and you lose interest, do you keep paying for it? What happens to all of the content that users created on your instance?
Well, I'm very explicitly not running it with the intent of it getting larger than maybe a couple dozen people I know who are interested. I'm not really interested in content moderation at any scale, let alone with random people I don't know from the internet. (My most recent job was dealing with content & abuse for a large cloud provider, and I have zero interest in picking up shitpost babysitting if it's avoidable.)
I'm otherwise going with the Mastodon Server Covenant as the basic guidelines: I've got a trusted friend I'm going to add as a 2nd admin, doing backups nightly, and at least a 90 day notice if/when I decide to stop hosting this.
I'd happily transfer the domain & data to anyone who wants to continue to admin it, or ask the community members what they want done.
I'll admit that makes WAY less sense if I wanted to run an instance with thousands of users, but that's very much not the goal.