@UbiquityDevPool Retweet Perpetual Bounty

[0x4007]

I did a quick search and couldn't find a tool that will allow me to do the following in perpetuity:

It would be really interesting to incentivize people to retweet DevPool tasks.

In order to do this optimally, we can design the pay scheme based on what is optimal according to the Twitter algorithm.

Follower Count

You want your following to be max 60% of your followers

We can check for this, and then we can pay based on follower count. For example mine is 776, so if I had the correct ratio (I don't) I could get paid 7.76 xDAI up to once a week for retweeting.

Then people like my friend with 183.8k followers could get paid up to 1,838 xDAI per week etc.

View Count

I see some of his posts get around 800 views and some get like 27k views. Perhaps it's smarter to pay based on views (we can probably get this from the API)

Maybe we can value a view at 0.05 xDAI or something.

Architecture

I'm unsure what the simplest implementation looks like, but we could probably start semi manually and figure it out from there.

Maybe a minimal UI that lists the Twitter handle of the retweeters of the previous month, and calculates the rewards next to them.

We need to monitor our tweets for retweets. For the first step we can manually handle payouts. Later if we get traction we can automate with permit payments.

[sergfeldman]

@pavlovcik In the context of tasks and X (Twitter), it may be interesting to read about this project
https://www.launchcaster.xyz/bountycaster/65491c0bf01de1b8b16bd95b
https://www.bountycaster.xyz/faq

[0x4007]

I know about it at a high level. That's what inspired the total bounties count on ubq.fi

[SyedMoin-lab]

I appreciate your ideas on incentivizing retweets for DevPool tasks. Basing rewards on follower counts and views aligns well with Twitter's dynamics. A simple UI to track retweeters and calculate rewards is a smart starting point, and I’m excited about how we can implement this effectively. Let’s explore this further and figure out the optimal approach!

[obeys]

I would advise against paying per view, or at least putting a limit to the amount that could be earned per view. Twitter has a massive botting problem and paying per view could turn south really quick if there aren't safeguards to filter that.

[rndquu]

Users can simply retweet either github issues either a link to work.ubq.fi with a ref code (implemented in ubiquity/work.ubq.fi#74) so it's not really necessary to build a whole infrastructure for tweet monitoring.