RE: Programming Diary #35: Steem's fundamental challenges
Similarly, there are some Hive participants who also add real value here on Steem, and we'd like to share historical rewards with them. However, there are also many Hive participants who are actively hostile to Steem, and we don't want to deliver rewards to those accounts.
Personally I only use Hive for Actifit posting, maybe there's a way to differentiate between transactional users and those who are deeply invested in the war. (And saying the word "invested"... maybe just checking someone's Hive Power can be a rough estimate for how strongly they care about Hive).
In the future, I hope to put checks like that into Thoth so that human curators can review its output with the knowledge that it's recommending posts that probably weren't plagiarized or created by LLMs.
It strikes me as wasteful that curatorial efforts, because they tend to independently consider each post, can end up examining and re-examining the same posts for abusive content. It's like mining for precious metals but dumping the chipped-through rock back down the shaft to be dealt with by the miner on the next shift. I wonder if there's a way to more easily acquire knowledge of what known-bad content is out there.
If "curation bots" are trying to use the Steem reward system, until now they typically try to guess what content the bigger voters will support. But, it doesn't have to be that way. If a "curation bot" like Thoth creates articles about the posts that it finds, then it can influence the things that people vote for. By finding good content, it will receive more rewards - both as a virtual-author and as a curator.
I don't know exactly how this can play into the social dynamics, but one thing that perpetual-rewards-via-beneficiaries does is bypass the curation rewards on the original post.
That's probably worth looking at. I suppose it could also look for STEEM to HIVE transfers in the wallet history. I've also been thinking about using whitelisting to address this. I even had to put a specific exclude filter on an account that has been inactive on Hive for more than 4 years because the account owner was so aggressively hostile to Steem at the time of the split. There just doesn't seem to be a 100% way to handle it. In the long run, I think whitelisting coupled with decentralized operation would probably get the closest, but multiple layers of checks are also good.
IIRC, for a while before 2020, Cheetah would lay down a 1% vote on content that it thought was plagiarized, then other curators could disregard the post if they saw the cheetah vote. I never thought Cheetah's plagiarism detections methods were great, but the signaling method was good. That could be useful for both plagiarism and AI detection.
We also have the current method where community mods/admins post their findings in a comment. That feels spammy to me, though, and it makes automation more challenging since natural language processing would be needed.
This is a good point that I hadn't thought of. I'm also not sure how how that would influence the incentives, but it bears consideration.