Thanks for this wonderful look under the hood of the visibility category. As a representative for one of the whitelisted projects, I've often thought of creating specific task requests for this particular category. Some of the latest examples have obviously been the Steem airdrop (though that caught on and spread like wildfire all on its own) and the Use-a-Thon.

However, often the timing doesn't allow task requests to be made, a conteibutor to catch up on it, study the project and start a campaign before it's all over. Particularly in crypto, things move extremely fast and a week is an eternity in crypto.

Another rather important thing to factor in, is different social media platforms' view on crypto. Facebook, Google and most of the other tech giants have rather strict rules on what type of content they will allow. This can make campaigning for a particular story or specific feature really complicated.

Lastly, one thing I've found out myself, is how difficult it actually is to know how to properly create a task request. What should it contain? How specific would it have to be? You quickly get a feeling that with every requirement you add, you reduce your chance of someone picking it up and helping with the campaign.

What to me would be the most beneficial, was a sort of template or even examples of past task requests serving as a guideline on minimum requirements, structure and other relevant details.

I think I'll try to hit you up on Discord and see if I can manage to work out something that contributors would both find fun and challenging as well as being beneficial to our project.

Cheers,
Punqtured of Byteball