the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation pt2 Show more
the problem of block evasion and impersonation pt2 Show more
the problem of block evasion and impersonation pt2 Show more
the problem of block evasion and impersonation pt2 Show more
@blackle On the back end, for a system with robust banning and blocking, the admin should have access to more information than guesswork based on who an account follows. IP information, things like that.
Obviously there's a balance with privacy concerns. But with a foss project, even if the dev is resistant because of one ideological choice over another (privacy vs security) the possibility exists to fork and create a version with different features.
@blackle It's an interesting discussion though. Glad I saw your posts. :)
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
@blackle I feel like these are problematic as solutions because they rely on hunches and guesswork.
I've seen several ill-founded witch hunts in various communities b/c people believed someone was someone else. And were wrong.
Impersonation seems a minimal issue; if it gets to be a big issue, banning similar user names/names on other instances doesn't seem a good place to start. Some kind of integrated signing would be better, like with email, where it allows user control.
@frankiesaxx I've heard from others who are very worried about the concept of being impersonated on other instances, so I'm weary of dismissing their concerns.
I suppose the most "tech" solution for discouraging impersonation is to integrate an identity verification system like keybase into mastodon
@blackle It's not a concern people are gonna stop raising, but it's not always based in reasonable understanding.
I've been seeing a few people who think of a username as personal brand territory that they're staking out and putting a fence around, and who don't understand someone else having similar on a different instance isn't impersonating and that frankie@social.tchncs.de is a totally different username than frankie@mastodon.social & that's a user education issue.
@frankiesaxx that's why there should be a report mechanism for that kinda thing, so a moderator can say "oh they're not impersonating, they just happen to have the same name as you" vs "they are definitely impersonating, they've copied your bio, avatar, and everything"
@blackle There is a report feature I think? Our admin on tchncs.de mentioned last night that 'similar user name' isn't something that needs reporting because people had been reporting it. Or maybe they emailed about it? Not sure. But definitely people are finding a way to report it. XD
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
the problem of block evasion and impersonation Show more
@blackle this is definitely not a problem that can be solved with algorithms without a significant amount of false positives and negatives