We’ve been working on a few functions for the bot. The focus was now making it a curator’s tool for being objective with their criteria. I know each person votes on others based on how they like the content, bonds, and for shits and giggles as an individual choice. But this becomes an issue when one is involved with a community curation activity especially when voting involves the use of other people’s stake. 

#### Enter the !profile user command:

<center>![Profile.jpg](https://files.peakd.com/file/peakd-hive/adamada/23tRzbA46m6G9n1mDDFMxoeCdKWbwUUyB7MPBn46tCfQHB565U372Y1jQcSARxzRk2i95.jpg)</center>

The picture shows you exactly what it says. The unique commentees shows the number of unique accounts you have interacted within the past 31 days (includes bots) at least it should be. Total comment count is what it means. Unique commentees count gauges how many unique users you’ve initiated conversations with.

Though the number of total comments made can be misleading especially when you engage with short comment talks or lengthy conversations with only a few people. This is just a quantity meter and not quality. I could've sworn I would have more users that placed me on their blacklist and muted list by now.  

The top 10 users voted on by the user are also displayed here. I initially wanted to find a number where you can consider it circle jerking but gave up on the idea and just let the person that asks to interpret it on their own. The percent shown here is relative to how many times they voted on the author for the past 31 days compared with the total votes they gave within the same time period.

<center>
![hiveph.jpg](https://files.peakd.com/file/peakd-hive/adamada/23tRzbA48CKu6vWXcVkCa3sr3MeEnzfSKskdsWgwiSYDocrh4eY6MQgGmmU8wWTSD5yFh.jpg)</center>

A user that votes on multiple people per month versus a user that votes on a few users per month would show different results. This tool is useful to see whether a curation community is really distributing their votes without showing any favoritism.
  
> Disclaimer: It’s still up to the individual or community to decide how much allowance they want to give per user. 

#### The !verify user command:

<center>
![verified.jpg](https://files.peakd.com/file/peakd-hive/adamada/23wqkRxfN6MND8h8v4xn2dMmZvrMQUQxKJRiAxzPCkxKD6tDogGwcEbYif6xDx9Zi2nCo.jpg)</center>

Same function as the blacklist but with a different label. Ideally mean to be used on posts where the author has shared proof recorded on the blockchain that they are who they claim to be. 

#### Some future changes with the blacklists and verification lists:

Having the option to “subscribe” to another individual or community’s blacklist. One of the frustrating experiences I had with the bot was going through multiple servers to verify and blacklist the same person.  Part of the decentralized community management is having the community members take initiative to do it on their own but I think we all know antiabuse is a niche demand. 

This tool tries to bridge HiveSQL functionalities with Discord to the masses. 

If you made it this far reading, thank you for your time.