Every time I see the rainbow fediverse icon on a post or a comment, I cannot help but smile.
This is the internet. By the people, for the people. Thank you all for participating.
I have a few ideas for niche communities, debating if I should host an instance or just the communities.
Would you have an idea of what kind of traffic/storage I would be looking at, if I were to host a community that gets 500 posts a day? I know this is a very vague question, so a ballpark answer would suffice. Asking because I’d like to host niche locality based communities for my country (India) and hosting is not cheap here. I could perhaps do Hetzner auctions but the latency would not be pleasant.
My instance is just me rn but I’m federating with about 500 communities, including all of the most active ones and Lemmy is running really well. My system is only using about 10% cpu and about a 1gb of ram, I’m just using a Hetzner arm vps with 4 vcpus and 8 gb of ram. Even a single small server should be able to handle a lot of users imo.
Hey, thank you, that’s good to hear.
Are there tools to “purge” media and cached posts? If I did delete older caches, lemmy would simply re-cache them the next time they are requested, right?
As far as I know there aren’t any tools to do that, Lemmy doesn’t automatically fetch older / deleted posts from federated communities like that, the reason is the way that federation works. When a user subscribes to a community on another server, that server will then start notifying their server when there’s new posts, comments, etc to fetch, but Lemmy doesn’t fetch older content, so only new stuff from that community will show up. I believe it’s possible to fetch old posts and comments using the search function though, you can read a bit more about it here: Lemmy docs
Thank you!
I’m having trouble with my LAN, I’m not even close to thinking about public facing stuff.
just goto @selfhosted and ask around.
Hi there! Looks like you linked to a Lemmy community using a URL instead of its name, which doesn’t work well for people on different instances. Try fixing it like this: [email protected]
Fair, thank you!