RE: Hive Improvement Proposal: Decentralize blacklists on Hive
You are viewing a single comment's thread:
We appreciate bringing this up and providing a viable option for decentralization of these lists.
We have wanted to see lists select-able by the users. With certain lists opt in and some opt out by default. So if this helps towards this end that would be wonderful.
If this goes through we would love to see lists have a few fields to help inform potential subscribers of these lists about what the list is and why they may be interested.
- Who runs the list, maybe who is involved for selection. (user decided or committee etc)
- Short introduction to the list
- Qualifications for adding to the list
- System employed for removal from the list (if any)
I think PeakD together with users will likely make decisions which lists provide valid information and benefit to users (like level of consistency and specificity of the list etc) and provide those lists as options to users to opt in or if for some lists limited to dangerous accounts we could see them as opt-out instead of opt in.
What is next up for helping this proposal happen?
We're implementing a prototype of it now. I'm fast tracking this idea because the current blacklist processing is the remaining bottleneck on hivemind performance at the moment in our prototype hivemind.
Unless there's a serious objection to the idea, I'm planning on just bundling the costs into our upcoming proposal for hivemind optimization in general.
Nah thhgu