I'm strongly against this. I think deciding the line on what is "the real bot" can genuinely get difficult at scale (though the same can be said for communities; which already have a verification mark given out by instance operators). Fluxer probably shouldn't have any kind of verified mark on bots, unless it is a system bot (operated by this instance's admins).
Instead, I'd much rather like to see the ability to add connections to bots. Then, you could see that it's definitely operated by someone who controls the official help site for that bot. Moreover, this mark looks the same across instances, so it's easy to tell that e.g. "Fluxcord on FluxFur" is genuinely operated by the Fluxcord developers, instead of being just something somebody hosted early enough and got verified that way for being "the main Fluxcord bot on this Fluxer instance".
With web-standard rel=me connections, you could also add a connection proving that the bot represents a particular git repo (because the invite link is in the README with rel=me), or that it really belongs to a specific public account on a microblogging site providing announcements.
This could be a way of verifying the bot, it doesn't have to be specifically a check next to the "Bot," I just gave that as an example.
I'm suggesting bot verification is a good idea overall, and just gave a single easy way of proving that it could be the bot. Connections could also be another way, and wouldn't require moderation.
Thread
Comment by sodiboo
rel=me), or that it really belongs to a specific public account on a microblogging site providing announcements.Comment by William