@soyrosa had a great detailed post about auto voting, lots of good comments under it.
Upfront here's what I'd like to see:
1. A tag such as #DeclineAutoVotes or #DAV
The Tag should be both long and short, interchangeably, so people can learn it. When it appears, auto-voting systems can then skip that content.
2. As a second suggestion I'd like to see entire communities be able to set this tag for all content on their community.
That would allow multiple posts per day, more like a vibrant message board.
If auto-voters want to allow their users to manually override this and vote despite the wishes of the content author, that's fine, but I'd like to see Hive.vote @steemauto adopt this as a default that people need to manually change (the way he reset the max votes per week in the last couple of days).
This is even more important now arising from new services which I'd like to use, like d.buzz to bring my tweets and perhaps some of my large twitter following to Hive. I can't freely tweet everything into Hive worrying that I'll get big whale upvotes sometimes and make a fool of myself with $8 for a dumb tweet.
I left a couple of comments on @soyrosa's post:
Curation by humans which scales with the platform, instead of the algos of Twitter and Facebook is a holy grail.
That is crushed by lazy autovoting.
Hive is close to getting it right but needs to be hyper careful with services like hive.vote. We all know that auto-voting is easy to code, but if the services aren't easy to use, fortunately, their use won't scale up.
I'm really concerned that we need a way to turn off auto votes on certain content. I am acutely aware that I get a few autovotes (thank you) and some of them quite big.
Which means I'm reluctant to use the upcoming service to cross post tweets to Hive if it means a stupid one line post is suddenly going to be auto-upvoted. There is a tension here and we do need it addressed.
D.buzz should bring their own site. It should not appear in hive.blog and other front ends. Otherwise hive will become a spammers' heaven. I am not sure what's the way out.
That is exactly what happens. Posts to d.buzz do NOT appear in my main Hive blog feed but they do appear in all posts. They do appear in the d.buzz front end. The issue is that even posts I make that go direct to a community get auto-voted up.
Ok...d.buzz is in testing phase I think. I didn't know that their posts were not appearing in hive.blog. But as you said these are being auto voted. If this issue is not solved, it'll make the platform clumsy. I really don't know the solution. Even if auto votes are stopped somehow, a whale's vote will give you 8$. It is equivalent to spamming the quality content generation of the platform. APPICS has already done it in steem.
Over on this new thread, someone has suggested the a little know max payout variable which seems like it might be perfect to cap rewards on these short little tweet length posts.
https://peakd.com/proposal/@dbuzz/proposal-to-change-usdhive-at-the-blockchain-level