I think best practice is to use a 2nd account for buzzing any ways. Even comments can clutch up your account, especially when you search for blog comments. So my plan is to use another account, and I think max payout is a good way to progress. No need to interfere with a hardfork imo

HECK yeah. I think this is a much better approach than trying to hack it. I want DHive to win and it shouldn't be penalized by the format that you use.

Trying to get a change at the blockchain level sounds like it would delay this by quite a few months as who knows how long that would take if it was even accepted by the community to do in the first place. As that sounds like it would require a hardfork so could that even be doing by the end of this year?


I personally would prefer just using a second account.  Regardless if there was a limit on post rewards or not if you are going that route. 


While at first I thought “why not just make them all comments or give an option to make Tweets comments instead.” I would agree it be limiting the growth of this project if they could only comments. 

I do sometimes wish if I was commenting on a Tweet that had a Hive link that it would auto post it to the blockchain as a comment on that post for me.   

The best option that I could think of so far is posting the buzzes as **comments** and not posts. Just like how @anonramblingscom posts a [daily placeholder](https://peakd.com/hive-116328/@anonramblingscom/ramblings-2020-05-16) and all buzzes will be posted as comments. It will pretty much look like a mess while using peakd or hive.blog but the good thing there is that people will use Dbuzz more often.

> I am also concerned that opportunists would take advantage of the lack of posts in our community. To try to post garbage or other spammy, scammy types of posts

There's always gonna be spammers. All you could do is mute them after warnings. 

> I think if the Hive community wants social media Dapps but is concerned about the reward pool abuse, a protocol change needs to be made at the Hive blockchain level

I disagree with this one. There are several short posts that I see that I think deserve the rewards. This could be a one-photo post or a video with less text. Or one-liner text that received a lot of engagements. The *length* of a post doesn't define the *quality* of it. We can't limit the rewards for short-form posts (in general) on a blockchain level just to adjust to a new dapp as it would seem unfair and would sound like it will defeat the purpose of the blockchain.


I could say limiting payouts that are posted on Dbuzz is okay, but there's no need to do it on a blockchain level as still, quality is subjective.


> My last concern is that if we decide to use comments for posts, people will build bots to upvote comments as the Dapp becomes more popular, defeating the entire purpose.

Abusers are always there and they will always make a bot for that. If they want to abuse, they will always do what they can to abuse. My suggestion would be: have something like a section where you could see **trending buzzes based on payouts** and the community can decide to give them downvotes or not.

> Users would be able to post to our Community & DAPP from 3rd party front-ends like Hive.Blog and @peakd with those Posts (Buzz's) being exempted from the max_payout code that we hardcode into our DAPP.

The **trending buzzes based on payouts** could probably solve this. 

Or those adjustments could probably be made specifically in the Dbuzz community? So whether they use hive.blog or peakd it will be applied when it's posted there. I'm not sure if that's possible though.

Congratulations @dbuzz! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :

<table><tr><td><img src="https://images.hive.blog/60x70/http://hivebuzz.me/@dbuzz/upvotes.png?202005191117"></td><td>You distributed more than 200 upvotes. Your next target is to reach 300 upvotes.</td></tr>
</table>

<sub>_You can view [your badges on your board](https://hivebuzz.me/@dbuzz) and compare to others on the [Ranking](https://hivebuzz.me/ranking)_</sub>
<sub>_If you no longer want to receive notifications, reply to this comment with the word_ `STOP`</sub>



**Do not miss the last post from @hivebuzz:**
<table><tr><td><a href="/hivebuzz/@hivebuzz/proposal-2020"><img src="https://images.hive.blog/64x128/https://i.imgur.com/qYidoDJ.jpg"></a></td><td><a href="/hivebuzz/@hivebuzz/proposal-2020">The Hive Gamification Proposal</a></td></tr></table>

###### Support the HiveBuzz project. [Vote for our proposal](https://hivesigner.com/sign/update_proposal_votes?proposal_ids=%5B%22109%22%5D&approve=true)!

I think there is no need to modify the Hive at the blockchain level as there is `max_accepted_payout`. This parameter can be set between 0 and  1000000 HBD.

For short-form content, this parameter could be set to 1-5 HBD and the post payout will not exceed this. Everything above this threshold will be returned to the reward pool.

You can see here how it looks when the parameter set to 1 HBD:
https://peakd.com/hive-174578/@abitcoinskeptic/experimenting-with-max-accepted-payout

When auto voters are checking this parameter, it can be used to mark a post as short-form content.

 I like the max_accepted_payout feature as mentioned by @holger80. I guess the next big discussion would be where to set it 1-5 HBD.

max_payout feature would only be affective if they used in our front-end anyone using other platforms we would not be required to set max_payout. 

Will you guys have keychain support as well? I hate giving authority when keychain can do the job.

I personally feel that you should be able to do as you please. That being said after reading some comments I would say using max_payout is the most logical solution to mitigate abuse at the moment, just so as you mention it when people post just they know what to expect.

The problem is what is an acceptable payout for shortform content? It's entirely subjective. Personally I feel up to $10-15 seems fine. 

Thanks for the mention. 

Yes, I fear that such a platform can lead to a lot of unnecessary spam... but posting on the comments? I don't think it's the way to proceed as well. That would be unfair. Freedom should be the main thing in this platform...

Maybe we should simply allow the community to deal with those posts as they see fit. We already have tools like downvotes, limits to maximum rewards per post, declining payouts... 

... and I'm sure it would be simple enough to change Hive Vote to ignore such posts... (@mahdiyari, @steemauto, is this possible?)

Thanks for taking in consideration my concerns.