view the rest of the comments
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.
-
No spam.
-
Posts are to be related to self-hosting.
-
Don't duplicate the full text of your blog or readme if you're providing a link.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
-
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.
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!
I think federated networks are healthier and better in the long run. Also there should be more smaller instances so the load is not too heavy to bear for any one instance.
@Saiwal For instance specialized communities like #^https://selfhosted.forum/communities should be made use of instead of having all the communities on a single instance. This would be more sustainable and cost effective for the admins too.
This (along with basically all instances with communick news behind them) is a classic example of scaling up prematurely.
When this community is brimming with so much content that users start to "miss" posts about [thing x] because there are so many posts about [thing y], then you make offshoot communities, not before.
@shnizmuffin I agree. I am not complaining, just saying what could be an ideal scenario. Someone on the reddit thread complained about their instance becoming too large too soon and they had to shut down, so was reflecting on that.
They probably used on of these federation "helper" scripts that just siphons up the entire fediverse. That is just a bad idea and results in a bloated database like they were complaining about.
I like that idea, although I think we need some simpler guides as to what exactly one might he getting into if they're setting up an instance that's not just a domain name. (Costs, potential usage blowing up, legal issues with content, etc...)
Also, I really think there needs to be a smoother way to navigate between instances. I guess, so you're still aware of "jumping nodes", but also don't feel locked in there. (Although maybe I'm just a newb still haha)
@MonkeMischief oh i agree. Setting up an instance is not easy. And choosing a place on the fediverse can be tricky based on how you decide to interact over here. For example I'm not on lemmy but I use my hubzilla instance to interact with the communities I am passionate about which I find is really cool.
And it does take some time to really understand how this allworks together but once you understand it's fairly easy to use and navigate.
I agree with spreading it across multiple smaller servers. Sadly, this is my third account after my previous instances shut down. So, there are some risks on that side as well.