I agree, the instances marked General are not really. I think you might also be correct about waiting a week. The lead developer seems to be fighting some other battles on Mastodon at the moment.
Indeed, thought I’d try again after a couple of days. Now getting 502 Bad Gateway errors from the joinfirefish site.
Also, some very strange reposting by firefish on mastodon. (possibly meant to do it from a personal account?) Some sort of unseemly personal argument between two people connected with the project that seem to have mental health issues.
That doesn’t make much sense. If firefish want iOS users then they are going to have to make it work on Safari
If you don’t mind about the local timeline, or that the main language is different or that other users might get it defederated then your approach will work.
They are marked as general but when you click or tap through it’s obvious most of them aren’t
Edit: Also, I thought this was a domain change not migrating the users. If they really are migrating users then that would explain why it’s taking so long. But why show the server as verified and available during the process.
I think someone not used to these things would see ‘Coming Soon’ and just leave it as not launched yet.
I understood that 0.18 was a release candidate and not production ready. There seem to be a few killer issues awaiting 0.18.1
I thought Meta had said they weren’t intending to federate (at least at first)?
The madness continues: the list of servers now shows calckey.social instead of firefish.social. When you click the button to chose it, you’re then invited to sign up to firefish.social. But as soon as you tap it there’s a message that signups are disabled.
You couldn’t make this up.