Interesting approach, good luck! Admittedly I'm not sure if many users want to take their media uploading in their own hands and pay for it but maybe I'm wrong. Where are the images stored? Do you have your own hardware? Backups etc?
Also since you're interested in Fediverse media storage, I recently read about https://jortage.com/ It's a third party storage for your instance with deduplication, pretty interesting idea. Takes away a bit of the federated part though
My company does host an instance, but I've never used it for game streaming. No idea what the fps is
Jitsi or Element call
It seems like the vps stuff is fine, but the company I work at uses them as cloud provider (many VMs plus K8S clusters) and the quality is not so great to say the least. Also the support is sometimes blaming us for their outages and generally not too helpful.
This sounds super cool, I've been looking for something to keep track of my plants! Gonna try this
Wait, how do you know my password?
That's actually better I think. A project with zero open issues/requests is usually dead, not fast in solving issues.
Didn't see it back then, just came across this on mastodon today. Sure they are competitors, given that nextcloud started as am owncloud fork, but they probably monitored ownclouds development closer than everyone else.
The resources required by federating depend on how many people follow each other across those two instances and how much these post. Just existing and theoretically federating doesn't need any resources if there's nobody following, assuming threads isn't doing that different from everyone else.
For each post a user makes on your instance, it sends that post to each instance where someone follows the poster. There's no automatic sending to every known instance of every post on your instance.
This should be possible, in nginx you would just have near identical entries that deliver the same content. The service itself sometimes takes a domain to build internal links etc, and those usually only take one.