KE integrated into interfaces such as peakd? @ecoinstant mentions this, and it could be quite telling and embarrassing for some unless you intent on 'getting out'.
I haven't visited my BOT rules lately but it is jammed with my own personal preferences, so if someone decided to change direction, whether they are whitelisted or not, the votes will stop if certain criteria in not met.
Adding all this to a public interface, I don't know about that. We all have our choices.
We do all have our choices, but there is also a bit of an asymmetry for stakeholders. Those who have stake and want to vote Hive supporters, have to do a huge amount of work in order to see the info. As a result, they probably keep their vote circle smaller than if it is easier. For a small to zero stakeholder, down to the extractors, it is far easier to "hide" in the masses, attracting votes from stakeholders who don't have the time to check. For instance, since most of my votes are manual, if I could see a couple parameters to use as a general heuristic with a rollover, I am likely to vote more often. Somewhere between your bot, and me having to do all the research that went into creating your bot, before every vote.
I do some manual voting (yes really!..), and likely fall foul of a >10KE person occasionally. Has this concept been put to the likes of @jarvie / @asgarth, adding the KE rating to their dapp interface?
I think there would be very mixed options about it.