(moved) boots‮🌸🌿‭Apr 4, 2017

okay look
#mastodev, there needs to be a brainstorm on something:
a lot of users are concerned about cross-instance users using their username and impersonating them

what would be a good and userfriendly way to fix this?
gnu social doesn't even have a fix for this yet, it seems, so...

Show thread(moved) boots‮🌸🌿‭
people are misinterpreting the issue
*verification* doesn't matter rn
*impersonation* is the issue here
i want two users with the same username and the same avatar to still be identifiable as different people
Apr 4, 2017 at 11:09pmWeb
Show thread(moved) boots‮🌸🌿‭Apr 4, 2017
(same username and same avatar but different instances, mind you)
Show threadthe anarsmurfApr 4, 2017
@b Alternative example for the same issue, if I understand it right: I use the same @ on different instances, and I've already missed notifications because the person talked to the wrong account when using autocomplete... ^^°
Show thread0x7fa046c9Apr 4, 2017
@b To carry on with the email analogy, the solution is the same here: asymmetric key encryption and signing. Hopefully this platform is still malleable enough to allow for a seamless introduction.
Show thread(moved) boots‮🌸🌿‭Apr 4, 2017
@0x7fa046c9 look, i just want [email protected] and [email protected] to be distinct
i don't think *implementing keys and signing* is the solution to what is effectively an ui issue
Show thread0x7fa046c9Apr 4, 2017
@b I suppose the question I should ask first then is how much more distinct do you want it and with what amount of verifiability? As it is toots already list the user and instance of origin.
Show thread(moved) boots‮🌸🌿‭Apr 4, 2017
@0x7fa046c9 I want the instance of origin to be visible on this screenshot from the timeline. https://icosahedron.website/media/mO2WnPbsnPnZuTPURtM
Show thread0x7fa046c9Apr 4, 2017
@b I'm on board with that. All we need is a newline! :grin: