well server uptime is usually, and in the case of fediverse observer, coupled to a successful response. If the server spits out a 500 internal server error, that does not count as being up
Interstellar could support iOS, but the dev was actually the one that told me about the costs and that he just don't want to pay it. Maybe he could be convinced to support iOS if a developer or tester with an iPhone helped him and the community chipped in for the dev account. After all he does everything for free, like most of us do
I think the instance is not showing because it is not online at the moment... here you can see the stats of kbin.social on fediverse observer https://kbin.fediverse.observer/kbin.social
Regarding the amount of instances and the rather small users/server: a lot of the mbin instances used to be kbin ones (like you can tell by their name) including mine. So we did not start with one central instance that all the users went to, but with a lot that already had a small number of users. And the project itself is not that old, not even a year (we start in September or October 2023). I'd say we really only have one hyperfocused instance and that being rimworld.gallery
https://kbin.fediverse.observer/kbin.social there you can go to graphs and see the uptime. The overall uptime is actually still quite good with 95.94%, but in recent months it has been a bit rough
I think it is good to point it out though. kbin.social is missing from the fediverse observer, but if you have a look at this: https://mbin.fediverse.observer/list you'll see that almost all mbin servers have a >98% recent uptime and a >95% uptime over the whole lifetime of the server. Sadly, fedidb does not have an uptime metric
(yes mine is not up there, because it was offline for a week in september last year)
Here is a list of mbin instances: https://fedidb.org/software/mbin
We do not really have a "flagship" instance, as we saw that it created a bunch of problems for kbin having one
You should be using bcrypt or something similiarly designed to hash passwords, since they are much safer than sha256/512. Sha is not designed for hashing passwords and therefore a fast algorithm which you shouldn't use for passwords
I decided to upgrade, and so far everything is working fine. I had some hiccups after the installation, but a reboot fixed all of them. Thanks for your input :)
well server uptime is usually, and in the case of fediverse observer, coupled to a successful response. If the server spits out a 500 internal server error, that does not count as being up