RE: Idea for Hivebuzz about potential ranks changes on Hive.blog🐝 Attempt 2.0🚩

[asgarth]

Well, the "badges" on peakd are pretty open already.

• We use standard Hive accounts and standard follow operations: https://peakd.com/@badge-500505/following

• And we have a simple open source script to manage them: https://gitlab.com/peakd/peak-badges-automation/-/blob/main/src/badges/badge-500505.ts

• PLus we use HafSQL by @mahdiyari to collect account balances

Not sure what you have in mind to be more "open and decentralized" than that.

Comments

[mahdiyari]

Maybe we could integrate that somehow into HafSQL at some point. I'll add it to my list.

[asgarth]

Totally.

But I think it's still good to have the badge accounts to be regular Hive accounts. For example you can see a feed with all posts by accounts with 1+ million HP here 😁

https://peakd.com/b/badge-500506

[gtg]

https://gitlab.syncad.com/hive/hivemind/-/issues/218
Absolutely, using existing system of follows is great, once hivemind can do that with better API it would be even more straightforward to use on frontends.
So I guess you are doing it that way + using scripts to handle dynamic badges (like based on accounts or given actions on blockchain, i.e. for disabled witnesses)?

[asgarth]

So I guess you are doing it that way + using scripts to handle dynamic badges (like based on accounts or given actions on blockchain, i.e. for disabled witnesses)?

Yes, exactly