this post was submitted on 09 Nov 2024
211 points (92.4% liked)

Selfhosted

40670 readers
393 users here now

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
 

I thought this was an interesting post and discussion on selfhosted. Thoughts?

Some great points, but it's nonsense to say r/selfhosted isnt about selfhosting. I've learned so much there.

you are viewing a single comment's thread
view the rest of the comments
[–] sk@hub.utsukta.org 42 points 1 month ago (3 children)

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.

[–] MonkeMischief@lemmy.today 6 points 1 month ago (1 children)

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)

[–] sk@hub.utsukta.org 5 points 1 month ago

@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.

[–] sk@hub.utsukta.org 6 points 1 month ago (1 children)

@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.

[–] shnizmuffin@lemmy.inbutts.lol 13 points 1 month ago (1 children)

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.

[–] sk@hub.utsukta.org 6 points 1 month ago (1 children)

@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.

[–] poVoq@slrpnk.net 7 points 1 month ago* (last edited 1 month ago)

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 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.