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
I'd like to help with this improvement. Do you know any plans for it? Honestly, looks like that there is no "lemmy committee" and even lemmy's developers cannot organize something like this. Any ideas?
Nothing good can come out of a federation committee. Invite whoever you want wherever you want and give a little bias to smaller instances, and it should balance itself out.
I dont suggest adding a centralization =) I see two possible and actionable directions:
I'm confused about what you want. Why should I care about lemmy.ml being over run because they didn't put enough resources into their instance?
Because we are here because of content, made by users. I'm thinking about whole "lemmy-verse". If users encounter issues, they just stop using the service. You as an instance owner can choose to not participate. But if somebody already thinks rhat they helps, why not use it?
I'm getting plenty of content. Not sure what the issue is.