Thanks for the quick fix. And thank you very much for this really awesome app!
I agree that a lot of subscriptions are really overpriced, but updates to an app are also a sort-of service. Pixelmator explained it quite well when their app switched to a subscription model, mentioning some fair (I think) pros and cons of the succession model, both from the perspective of users and developers.
Autoscaling isn’t only used the grow the number of servers under load, but also to guarantee availability of a fixed number. If the max is set to 1, the bastion host is protected against hardware failure, zone outages, or just you screwing up. Accidentally killed your bastion host? No problem, within a few minutes autoscaling will have provisioned a new one and you’re good to go again.
Arstechnica runs on WordPress on AWS, and they have a really nice series of articles about it. Sure, you could use just one EC2 instance for everything, but on a high traffic website you would need a bit more.
I remember the developer mentioned something about this once, and I had to scroll way to far back to find it: https://lemmy.ca/comment/1264956
I can totally understand being somewhat insecure about your code, or have the feeling that you need to do this/this/that before you can publish it online. And indeed dealing with an issue tracker, pull request that people expect you to review, forks of your code being published elsewhere, finding and trusting other developers to commit directly to your project can feel stressful. Disabling issues and pull request on GitHub could resolve some of these issues.
Connect is a fantastic app, and still my favourite lemmy client. I hope it will continue to work en be great for a long time. And most importantly that the developers still has fun working on the project.