![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://lemmy.ml/pictrs/image/2QNz7bkA1V.png)
This is just V-tuber with extra steps
This is just V-tuber with extra steps
All of your points only considers the community itself, which is not my argument.
I’m mostly approach this from technical standpoint. It’s impossible to have 100% uptime if there’s no horizontal scaling capability. For example on updating version, currently the instance will need to shut down for maintenance until it’s finished and usually there’s still some issue to fix. If horizontal scaling exist, the instance can update server (or add additional one), move the traffic a bit to test it, and then fully rollout if everything going well.
Why not? I don’t see the drawback to develop ability to do horizontal scaling. If the instance owner doesn’t want to add additional servers, it’s up to them. Obviously they paid for it if they decide to add.
Just to be clear, horizontal scaling means multiple servers handling same instance, it can be the backend service to allow handling more traffics, or multiple db to reduce database loads.
Additionally it allows high availabilities, so if one of the backend service is down (either unexpectedly or do rolling update) the other service can still active so the instance can still be accessed by users
until beehaw defederate your own instance
I use git fork on Mac, same reason, I don’t remember all the commands. Also want to see the history visualization
MacOS is not that locked down compared to other desktop OS. I’m pretty sure you can already run emulated windows in mac