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 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.