I was recently approached by a user claiming to be the developer of Sync for Lemmy who wanted to be a moderator of the community I created, !syncforlemmy.
I was able to verify this user was indeed LJ Dawson as I knew where to contact him on Discord.
It is quite possible that an impostor user on another instance may be created, for example ljdawson@beehaw.org could easily be made.
Should Lemmy have a verified user marker for members who are of importance to any given community? Are there any other options to protect users against nefarious persons playing impostor?
Should Lemmy have a verified user marker for members who are of importance to any given community?>
No, everyone is equal here and I want to keep it that way. I don’t want this to be twitter.
Are there any other options to protect users against nefarious persons playing impostor?>
You mean besides the one where you just successfully figured out the person was legit through verifying them?
No, it should be up to the community mods to verify someone is legit not the app itself.
I respect your position, but I think that as federated services gain popularity, the percentage of users who have the nous to validate any person decreases. Additionally, I can’t image users being happy about answering large numbers of validation messages.
If you have even just a bit of fame… you more than likely have a website that show all the way to contact you… so this is a non-issue.
Example, me: https://thefrenchghosty.me/contact/
I like mastodon’s solution. That is, validate a public identity, like a site, your site appears on your profile and it’s only verified it you have proof inside the site itself.
On this specific case, the Sync team may have their lemmy users on the Sync site.
Similar to the way nostr does verification: https://www.name.com/blog/how-to-get-nostr-verified-on-a-custom-domain
No.
Let’s say you trust billg@microsoft.com. Anyone can already create billg@scam-site.cn. You wouldn’t trust that, why would you trust any other account you can’t authenticate?
Like most impersonation questions, the answer is to verify identity through a known trusted source, as you did.
Nobody else can have the username Izzy@lemmy.world so that is proof enough that I am me within lemmy. If you have some identity outside of lemmy then that identity should be verified outside of lemmy.
That’s doesn’t mean anything though.
Nobody else can have the username Izzy@lemmy.world but Lemmy.world is only one of hundreds of instances on Lemmy.
I could go right now and make Izzy@<any other Lemmy instance> and depending on the client used, nobody would be able to tell the difference if that client doesn’t list the instance as part of the username. For example, both mlem and Memmy on iOS do not show full usernames by default. You just show up as Izzy to me. So Izzy@lemmy.world and Izzy@lemmy.ml would show as the same user to me.
That is a deficiency in those implementations, not in the platform itself.
Unless the Lemmy devs create their own app, the vast majority of users are going to use third party apps like mlem and Memmy.
So it’s still a problem with the platform if the username databases for instances don’t validate against each other to prevent reuse and impersonation.
A verified user marker? Maybe, like, a blue checkmark?
