While I’m not interested in encouraging /r/selfhosted users to leave reddit, I thought it would be good to have some discussion around the possibilities for a selfhosted community on lemmy.
It looks as though most users are washing up in [email protected], but this is but a temporary refuge in these troubled times. The single mod is not responsive, lemmy.ml is already struggling with load, and the background lemmy.ml community may not be right for us. If we set up shop here we’re just going to have to move, probably sooner rather than later.
So if we move, do we create our own instance or move to an existing one better aligned with our needs?
Given that there don’t seem to be any instances which are really ideal, the remaining advantages to choosing an existing instance is simply that we rely on someone else’s infrastructure (and the associated time, skill, and responsibility). This is a significant advantage which makes this option tough to pass up, but the equally significant disadvantage is that we don’t get our own place. It’s like renting a room in a frat house rather than building our own mansion.
The remaining option is to create our own instance. If we were to go this route, in my opinion it is critically important that the responsibility for this be shared amongst several people. This dramatically reduces the odds that someone loses interest, or lacks the resources to support the community long term. While I’m certain that everyone in this sub could spin up an instance, we all know that providing high availability to potentially thousands of users is not something to be undertaken on a whim. There’s a significant risk to the community in allowing someone to take this on themselves.
I think fosstodon (mastodon) with several admins is a good model of how something like this can work. I also think it would be a good idea to broaden the subject to FOSS rather than merely self hosting.
So the questions are…
Do you think we should create & support a community on an existing instance, or create our own instance?
If an existing instance then which one?
If a new instance then how would you like to see it operated?
I think it would make most sense to collaborate with similar subreddits, which overlap with /r/selfhosted.
/r/selfhosted /r/homeserver /r/homelab /r/datahoarder
These subreddits and more overlap, so to me, it would make sense if these subreddits would come together on the same Lemmy instance, jointly controlled and managed, with each of their own community.
Yep, this is what I said in the post more or less. Cover FOSS, not just selfhosted.
You keep recommending the FOSS umbrella, but at least on Reddit the selfhosted/homeserver/homelab/datahoarder subs are interesting, while the FOSS reddit tends to be so boring I unsubscribed a long time ago.
The interest there seems to trend more in the direction of license and convincing people, with an undercurrent of “where can I find a carbon copy of this expensive program for free”. My interest is in resource-efficient infrastructure, so I don’t see a lot of overlap.
I don’t really understand. I’m not talking about creating a “foss” subreddit / sublemmy / community.
Anything self hosted is by it’s very nature free open source software (foss). This also applies to homeserver & homelab. Admittedly datahoarder is to a lesser extent but there’s still a very large cross over.
Therefore foss seemed like a good umbrella term, as a way to group the majority of these communities. So you create a foss instance which would be the ideal place to host selfhosted, homeserver, homelab, and datahorder subreddits / sublemmys / communities.
If I was looking at a list of instances, and saw a FOSS one, that’s where I’d expect to find these communities.
That said, I’m open to being convinced that there’s a better way to categorise these things ? What would you use as the umbrella term?
Having FOSS discussion isn’t bad, but there is most definitely a lot of proprietary software in the selfhosted world. Game servers, most network device software, applications like plex, heck, lots of people run windows on their selfhosted infra.