@[email protected]

Not easy but I believe it will be a barrier for real/mass adoption.

My first idea would be to have a single specific service where you register your handle. From there, you sign in to instances. You don't/can't register within instances, only sign in.

Existing collisions will be messy to deal with but it would be much much better in the long run

@halcy @Gargron

@Gargron

Like... this just can't be a thing that goes on and doesn't change. The whole point is to be better than twitter and this right here is worse than twitter. And I know we are all here basically for a Better Twitter

@five @halcy @[email protected]

@Brenner oh that's my fault bc of how I handled my migration @Gargron @Trev @halcy

@five no not your fault. If anyone on two instances follows someone on a specific instance from both accounts, this will happen. I could have 100 followers and they could all be 1 person on 100 different instances.

Not only that, it's confusing AF. Do I wanna see your maly tweets in my social feed? And/or vise versa? If i tweet at your from one instance, I have to go back to that instance to see a notif you responded?

@halcy @[email protected] @Gargron

@Brenner for me personally, I'll def be sticking to Maly until a clean port is possible, you can unfollow my M/soc if you want https://maly.io/@five/10405 @Gargron @Trev @halcy