The common complaints i’ve read are that it had mediocre battery life and the screen felt cramped.
That’s the thing, if instance admins do that to avoid duplicate communities, won’t that just mean that a few huge instances will be the ones with most of the popular communities, and have outsized sway/traffic costs?
Then we’re back to square one and defeat the whole purpose of distributing load across many medium instances. Or am I misunderstanding how this works?
So if the ideal Lemmy structure is a large number of medium sized instances, would you say there should be a mechanism (either at the API level or handled by clients) to randomly select a general purpose instance at sign up?
If you want to follow Twitter accounts from Mastodon, there’s a bridge called Bird.Makeup that still works and is working on a workaround to this issue.
I’m working on a Mastodon client called Agora that integrates this bridge into the search, so that if you search for “[email protected]” it automatically loads the bridged Mastodon version of the profile: https://agorasocial.app/#/andrew.masto.host/a/111844567849084915