@bottitytto yes, that's what I was thinking. if you can manage your ID on other instances within one instance, then the issue of a central log-in system becomes moot.
@Migukin Every user's main instance becomes their *own* central login system. Which... is idea. Identity management should be 100% up to the user.
@bottitytto I agree, in general, but if you want this to compete against Twitter, you'd have to dumb it down so even the most brain dead person could do it intuitively :-)
@Migukin Well yes. Identity management can be scary (just like decentralisation in general!) but with a bunch of brains thinking on how to make it painless... it is definitely possible to make it feel natural.
@bottitytto I would compare it to how they've managed to make even Linux "easy" to use with a nice shiny GUI. I could see a setup whereby you would have a list of instances and a button you would tick off to "save" your ID on those instances. That's it. no more thinking than that. #UX #UI
@Migukin Considering Mastodon seems to have pulled in a portion of making GNU social federation "easy" to use for non-techies, it seems like a logical next-step to help make it easier to manage one's identity across several domans. How to manage identity has been one of the most-asked questions I've seen.
@bottitytto pretty much. you have to look into the soul of the service and ask what it is. is it a refuge from Twitter for easily triggered tech people, or is it an open source competitor to Twitter? If it's the latter, then ID management is something that has to be address ASAP. Otherwise, a startup with a single server setup like Twitter will eventually swoop in and make all of this moot.
@Migukin Using the app login system, one could cross-authenticate, in theory. Have your secondary instances become "apps" to the first, and then you would have a "list of usrenames" attached to your master account? :o