Thanks, bro. Yeah this was about 50% rant and 50% what I would like to actually accomplish. The next post from the @steemflagrewards account will be more succinct.

I hear what you're saying. To keep it simple, I was thinking of calculating the rewards in proportion to the vote negative rshares compared to the total so yes, technically, a whale using a full weight flag is going to get more than a minnow with the same. 

I don't necessarily see a problem with stake being a benefit for curation but I am not a fan of it being used on the author side. I have grown sick of the "Well I invested money in the platform so I get to put my comment/post at the top" mentality. 

But yeah, with our only able to set 50/50 rewards, not sure what the function of SP would have in light of this projects intent. I could have it upvote the flaggers last post which I could see as being a nice benefit.

On second thought, I did not consider that bandwidth limitations may be an issue. ![image](https://img.esteem.ws/w4tu1409la.jpg)

-4.02% bandwidth. That is the first time I've I have ever seen that! Wow. Lol

Any help via delegation would be appreciated. First post payout should get it over the hump so to speak

Hey @sreepyeldarb, I really appreciate the support. This idea is very new and I haven't fully considered how the account would curate while remaining objective (not taking sides on the wars going on for instance). 

So, one issue I am considering is that we are currently only able to 50/50 author rewards. I would prefer 100% SBD so the good flagger rewards will be greater. It may not be bad thing though for the account to gain influence via SP but I have reservations about self-voting so not sure how it may be gainfully employed. Maybe just upvoting the flaggers last post as an added reward for their service. Or I could power down and liquidate to send them Steem instead. Just thinking of ideas currently.

I created this link which should make it easy. This will delegate 2 SP which I believe is the minimum. I'm running into issues with the bandwidth again so I will be delegating to hopefully get things going again.

Here is the link. Feel free to adjust the vests to what you are willing to delegate.
https://v2.steemconnect.com/sign/delegateVestingShares?delegator=sreepyeldarb&delegatee=steemflagrewards&vesting_shares=4098.000000%20VESTS

I'm happy to report that we may have one to help fund the initial account creation. They just wanted more details which I have provided. Yeah, I think this is going to be pretty cool. Heck, think it will be fun even if it doesn't get a whole lot of support. 

Worse come to worse, I leverage my own account but I'm keen enough to be aware that the flags may fly. I'd prefer just letting it run and not necessarily take sides on the war but, at the same time, providing a mechanism for flags to be rewarded to those that find spam. That's a service to the community and thus should be rewarded. 

I am cognizant enough to understand that, without the proper precautions, it could be "weaponized". This is why posts will be screened for the common flag criteria. It should pertain to value and will not be used for any type of war if you know what I mean. Perhaps, forming a committee consisting of all Steem Power demographics would be wise to make the screening process democratic in nature. We will have minnow, whales, dolphins etc.

Sorry for the lack of clarity. That pic is only demo of the technical capability of the script compile the data of trending posts that have been downvoted. When the project is ready, the data will be used to detect abuse but that raw unfiltered data itself will not be published.

However, metadata on the posts deemed abuse or meeting the other criteria of flagging will be published. This is down the road as this project is in its infancy. The scripting started today as a matter of fact.

That data, in turn, will be leveraged to identify potential instances of abuse but these will be subject to manual review and possible approval via committee of Steem representatives from minnows to whales before they are even submitted as a post. 

I think that would serve as a good protection mechanism from the potential for this tool to be used irresponsibly. Hope that makes sense.