I think instances should be by topic / community born into existence once sign ups for that community hit critical mass (pick a number in the thousands)
1. These are timelines that show a collection of communities' tweets. Anyone can make any collection.
2. These are specific communities of atomic size
You can choose to tweet to a community, collection, or into the commons
1. I hope you use neither of those 😜
2. Most people I know have at mostttt 3 email addresses
- personal
- work
- junk (maybe)
Even then, it can be annoying to know which email to email them at. "Oh sorry i don't check that one often"
I envision people being on many more Mastodon instances. Managing all of them will be very hard.
I would be annoyed if I had to think about which email would reach you vs not
@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?
Yes. That was my only reservation on that. But, I'm not against that compromise. If the rest is decentralized, what is the downside of name registration being centralized? That's a very small piece of the whole thing. And not a very important piece from the standpoint of optionality / being under control of a corp / etc
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
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
@Gargron @halcy @[email protected]
I'm also inclined to be loyal to Mastodon vs Qvitter & Classic purely based on the fact that Mastodon is not in PHP (meaning I'm open to trying Pleroma (but not Aegnus because who the fuck would name something with a non-english keyboard letter in the name?))
@[email protected] @halcy @Gargron
Could @[email protected] be someone besides me? (answer is yes) but that's confusing AF!
I would suggest having @handles be the same across all instances before the rest of twitter joins here. I understand that's probably technically difficult to do.
@Gargron @halcy @[email protected]
May some time of visualization / infographic on how it all works will help new Mastodoners.
The connection between other GNU social instances (from https://social.guhnoo.org) and Mastodon instances from instances.mastodon.xyz isn't too clear either - do those messages cross-post too? I'm sure the answer is buried somewhere