Quote from: Cloverdale on August 05, 2016, 04:25:27 PM

Quote from: Namworld on August 05, 2016, 03:45:00 PM

The problem with this is if we open publicly and have such instant payment, you know some people would make accounts up to minimum requirements, posting bad quality posts, then bot spamming hundreds of posts with randomly generated after joining campaign, right before a CRON, to then immediately withdraw.

Your payment is set to weekly, right? So that should not be a problem. If you want to control the spam then check the post manually a day before the payment or better yet daily before the creditting schedule.Since yahoo is already the manager, he should be able to monitor everyones post quality thoroughly.
Another option is to set a minimum character requirements gor post to be counted and limit the boards your user can post becase there are several boards here which receives a lot of spams from coinroll members for the past few months now.

Forgot that Yahoo was the campaign manager for this signature camp. So that is his duty when he took on the role to do the spam control for this project.

Quote from: European Central Bank on August 05, 2016, 05:23:03 PM

I don't care about instant or daily withdrawals but with the current withdrawal setup you can never be totally sure when it's gonna happen and you have to manually put it through. That's double uncertainty. other campaigns pay out automatically at a set time once a week.

it makes sense to manually check for junk posts but if it was automated you could still prevent payouts before they happen. it would be nice to know when a payment's gonna happen and not have to apply for it every time.

This seems to be the trouble many of the members that are part of this campaign are facing so far from what I have been seeing from past posts.
So if this is the case then a new way of how payments are handled should be looked at.
I just got payment from my campaign and it was requested, queued and dispensed to my wallet 'instantly' so why not this one? You have the attention of your devs right now so you should address them on coming up with a better solution for this then the one you have in place at this present time.