Thank you for your detailed explanation.
Do you envision any possible solutions?
Eg.
- a proposal to make inactive witnesses lose their rank.
- have proxies only accept X users and with a good balance of age of the account and reputation. These could be automatically and periodically rotated as well.
- automated warnings added to frontends for users that constantly circle jerk?
As for the part of the witnesses, on a post of @blocktrades a few weeks ago, it was said that there would be some sort of cleaning up on the old votes given, ( older than a year I seem to remember) But I don't know if the speech was more touched or carried forward, as you can imagine would mean a nice nuisance, for those who are there to do farming without doing anything...
(surely a moderate view where there can only be x proxies or only a value of x would be a better compromise)
Some alerts could be inserted why not ... on hive.blog there would be plenty of nice things to implement ... consider that practically nothing has changed between now and 5 years, only the community part ...
The code for expiration of old votes has been completed and will be included in hardfork 25.
Thank you for your answer!
Hey @blocktrades, do you have a post detailing the business logic for the expiration of votes?
It's described here: https://hive.blog/hive-139531/@blocktrades/roadmap-for-hive-related-work-by-blocktrades-in-the-next-6-months
But yeh peakd did the flippening a few months back.Right, I think that only @quochuy has actively been working on it. He added a few nice features.
I'm slowly adding more features introduced by Peakd and Ecency. More can also be done if the backend (Hivemind or API) is also updated.