The latest blog post about our .world and the Fedihosting Foundation. As you can read in the blog, the donations are no longer covering our running costs. If you are able to spare a few Euro’s or dollars or whatever currency, please check the list of our donation platforms in the blog.
Edit: I will add these to the blog: https://bunq.me/fhf (for EU bank transfers) https://github.com/sponsors/Fedihosting-Foundation (Github Sponsor)
we do have some limits in place, but lemmy only allows rate limits per ip, and those are counted in each backend process independently. I’m currently working on implementing better rate limits in our load balancer.
due to rate limits historically not working at all or not working properly, there are still various instances without decent limits. additionally, these rare limits only apply to local users. federated activities are not limited within lemmy. we recent added some fairly high limits to our automod to catch some of these cases and it’s been working alright so far.
Wouldn’t it be an idea to enable auto-deletion of messages after a set amount of time?
what would that have to do with this?
Would it not reduce the storage needed, and so too hosting costs? Granted I don’t know well how that works, but it was just an idea.
you could save some storage with this, but i don’t think it’s a good idea. a lot of people expect the threadiverse to have a lot more permanence than e.g. mastodon, similar to reddit. being able to find old posts/comments about a certain topic is one of the things that made reddit as useful as it used to be, especially when searching for tech related issues in my experience. old doesn’t necessarily mean obsolete, and whether this would be suitable would be highly dependent on the community. most communities are not intended to be for ephemeral content only.
Hmm, fair point. How about making it an option for communities? That they can enable/disable this permanency, with the default for new instances being ‘off’?