A what? Let me explain my most recent idea to you.
Recently I've discovered the Mantecurated tool) by the 
It shows the diversity of authors, vote distribution and self votes. The better you score on these points, the higher your score. I find it a really cool tool to see how you are doing. And with 82/100 I'm doing quite well I think, although I could improve my distribution a bit.
This is a really cool tool that give you a really good insight of the quality of your voting or the voting of other accounts.
But this tool also gave me the idea for another tool. What if we make a dashboard with even more statistics?
Quality monitoring dashboard
Personally I find it quite hard to determine whether an account is adding value to Hive. Especially with the rise of AI and the high number of scammers. The only statistic that is shown on most front-ends is reputation level. And to be fair, this number doesn't tell me a lot. There are accounts with a high reputation that aren't adding much value anymore and newbies with a low rep that do. And also scammers are using accounts with quite a high rep of around 50.
Recently PeakD introduced the KE to (check my recent blog about it). But also KE doesn't tell everything. Some people just need the rewards to pay for their bills in real life.
So I thought; wouldn't it be cool if there was a dashboard like the Mantecurated tool, but then will all kinds of stats from an account?
With an overview of all stats from an account you will get a better view on their behaviour on Hive,
I think such a tool would really help curators make better decisions while curating.
It might look something like this (generated by AI based on the content of this blog):
Which stats?
I have created a list of stats that I think might be interesting to see on a dashboard
- Posts/Comment ratio (does the user only post or do they also comment)
- Interaction with own posts (does the user interact with its own posts)
- Unique downvotes (how many downvotes from unique accounts did this user receive)
- Number of comments per day/month
- Average post length
- Average comment length
- Autovotes received (does this account get a lot of upvotes from the same users at the same times)
- KE
- HW Blacklist (is the account on the blacklist of Hivewatchers)
- Outgoing transactions to known exchanges
- Transfers to other Hivers
- Send out vs Received
- Average reward per post
- Self votes (how many times did the user self vote)
- Vote distribution (not always voting the same users)
These are the stats I've come up with, but maybe there are some more interesting ones to add to the dashboard. Feel free to share yours in the comments.
Which timeframe
There are accounts that have been registered almost 10 years ago and a lot can happen over the years. Someone might have changed their habits over the years. It would be interesting to focus on a more recent timeframe like a year or even a month. Maybe it can even be made adjustable.
Configurable thresholds and traffic lights
It would be cool if some of the stats could have personal configurable thresholds. For instance if a user has a KE < 50, the bar is green, but when it goes above that threshold it turns red.
Indicator in front-ends
Ideally I would like to see the traffic light I mentioned above integrated in the front-ends.
The idea is that the traffic light turns red if any of your configured thresholds is exceeded.
The red light doesn't mean you shouldn't upvote, but should be seen as a warning! A sign for you to look into the stats of the author before curating.
As new accounts don't have any thresholds configured we might want to think of a default set of thresholds.
What do you think?
I realise this is quite a big project and there are probably a lot of things to say against some of the stats. But I do think it would be helpful to have a quick overview of these (and maybe even more stats). It would at least help me make better choices when curating.
And when we as Hivers can influence our own stats by changing our behaviour.
I'm really curious what you think about this idea.
I'm tagging a couple of developers to see if this idea is even feasible at all; 
Please share your thought in the comments.
