As it turns out, the max_accepted_payout route would not work.
Here's why:
@nathansenn just informed me of a major flaw in the max_payout route @holdger08.
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.
Users would then be incentivised to post to our DAPP from 3rd party front-ends and our real users would be punished by being restricted by in-house rules that are not applied to Buzz's posted from 3rd party front-ends.
Please help us gather attention on this, we were scheduled to launch today but this issue delayed us.. if it delayed us, it will delay other DAPPs too.
Thanks for the reply, Always a way around with code.
I wonder if your DAPP could cryptographicaly sign posts so third party posts could be detected and dealt with by groups like @hivewatchers. When you attach token benefits to users using the DAPP the signed posts would be detectable and therefore properly dealt with.
Just my 2 cents worth