> all posts that have max_accepted_payout set to 1 HBD are D.BUZZ posts, no matter on which frond-end the post was written

> all posts that do not have max_accepted_payout` equal to 1 HBD are not a D.BUZZ post.

If you or someone else that is more connected in the HIVE community can get Hive.Blog and @peakd to implement this change, of setting the max payout for posts published to the DBuzz Community to $1, please make it happen.

It would still be a temporary and somewhat messy fix since DAPPs could still launch, even tiny ones that are bootstrapped as simple services to game the system. 

I believe if you were us or another DAPP wanting to offer a reliable service without interruption from rogue actors, you'd be interested in code that made it impossible to game the max_accepted_payout as opposed to relying on verbal agreements with others, and the belief that everyone else in the future would agree to those agreements too.

> My proposed changes are not temporary frond-end fixes. Agreement if a post is a D.BUZZ post is already defined at blockchain level. There is no way to cheat, either a post has the correct value for max_accepted_payout or not.

There is a way to cheat.. 

1. Fork Hive.Blog and publish to our community without the max_accepted_payout code included in our community of the forked front-end.

All of the posts published in our D.Buzz Community reflect onto our site so the posts published to that forked front-end would not be constrained to $1.00 payouts and would therefore trend higher than our real users who posted from D.Buzz.