What would be the best thing to do to help keep lemmy.world up? Donate? Servers? What is the best way to help?
Two things I can see, needs to be on scalable infrastructure rather than a few hosts running docker-compose. Needs to have support for in-memory key/value stores for caching. Either of these would probably help out a bit. Donate to the developers or instance maintainer and either could happen.
Fantastic. Where do I do any of that?
Digging around… Here’s to donate to the .world federation. https://www.patreon.com/mastodonworld?utm_campaign=creatorshare_fan
See the heart symbol in the top bar
That goes directly to the developers of Lemmy, not the lemmy.world instance admins (just making the distinction).
It goes to whatever your instance admins set it to. In lemmy.world’s case, I guess they chose to stick with the default.
It will also help to evolve towards some form of immutable governance for the instances. By this I mean an instance should be more than the individual admin(s). If such an individual was to tire off, get distracted etc, the instance does not suffer the same fate. Technical federation is one thing. Federated governance is a whole different issue. I am not advocating for formal organizations (but those would help in some cases), but rather a clear provision for instance-continuity beyond the current admins.
Me and a handful of friends started a formally registered non profit in germany. Not internet related but art related stuff and it was surprisingly easy, fast and even more surprising the regulations and requirements actually make sense. That is the way to go to secure that no admin ever goes nuts and takes an entire instance with them lmao.
I‘m fairly certain that similar organizations exist in most countries snd the process should be relatively similar.
This is the way to go. Gives some reasonable grounds to commit to an instance when you expect it will be up in a month. We are also trying that with Baraza with a trusteeship kind of design.
Easy migration. Migrating account post history or migrating community from one to another easily
I’ve been creating accounts on other servers as well so that I can protect the username and also have a certain amount of per acct specializations.
deleted by creator
The cost quickly adds up for small underfunded projects though. You also need to factor in how the application does scale. What kind of ingress/load balancing is required. What kind of stateful storage is required. Network policy. Resource monitoring. Config management, CI/CD pipeline. I setup a basic cluster on gke to start but haven’t gotten around to building these just yet. I’ve got a goal of attempting the most performant, scalable, and cheapest instance out there.
That’s the easy part. Next part is identifying which app endpoints are the most intensive and splitting them off into separate deployments.
The hard part is scaling the database, as I’ve only seen one tool that can autoshard effectively, but it’s for MySQL, not Postgres.
If I create an account on a small instance and that instance shuts down, will I not lose my account and post history?
Ribbit
congrats! This doesn’t answer the question at all.
