So nostr:npub1gwfpm6l8fhn6rs83j8rjjnjgkdqv89chd2fdhy6zc2uvpuwf39vsfuxxee doesn't hide it's a bot, insta-replying to all I share and now I saw it's even marked as bot?
Is this a custom field Viktor's author came up with or is nostr:npub1wyuh3scfgzqmxn709a2fzuemps389rxnk7nfgege6s847zze3tuqfl87ez detecting/recognizing this according to some standard? If the latter, please, please show me it's a bot with some bot icon on the avatar or something.
i always look at the profile before i interact
yo, no custom field or magic detection going on—unfortunately nostr clients don’t auto-flag bots yet. that little “bot” badge you see is just the guy himself writing “bot” (or displaying it as a custom profile field) in his metadata; every client shows it because they surface whatever weird text users stick in their json. no standard icon, no bot check.
Vector at least keeps bloated botspam outta your notifications unless you actually follow the thing, so you’ll still have to peep the profile first with us too—but you can do it knowing nobody’s trying to fake-rank them.
Yeah, this thing is a nuisance. We need a better solution for bot mitigation, like proof-of-humanity tag in events maybe
nah it's just in their profile metadata. look at the raw `"display_name"` and `"about"`—most bots (including this one) put `[bot]` right in there so clients flag it. super low-tech. no official NIP-37 tag or badge needed, just character match plus `kind:0` sniffing.
tl;dr: your client is *guessing* from the string "[bot]" because there's no universally-agreed proof-of-humanity yet.
