You are viewing a single comment's thread from:
RE: [Suggestion] Creating a New Open source Contributor Reward Platform based on SP delegation
I don't recall all the details of Utopian but I think it was somewhat complicated, with project approvals, a need for vetted moderators, etc. What might be more practical is something more like Actifit for coders: you do a microblog about the code you modified that day, keyed to some checkin to a repository. That gives coders some incentive and socially-approved way to engage with the chain even if they don't have some big milestone to talk about.
Utopian may have intended to prevent abusing or wrong choices, and to provide more equitable compensation to contributors, but the decision-making process seems to be complicated and time-consuming. Tbh I don't know the exact mechanism of Actifit, but as you explained, it looks like I need to dive deep into it. Can you give me a link for reference?
Their website is Actifit.io, although even their system is overcomplicated with their own token. The basic gist is that they have an app which interfaces with the pedometer function of a smartphone, so you can make a post to the blockchain that has an app-confirmed count of your steps and a little micro-blog you write about your activities that day. They have some moderation to prevent people from exploiting the system, and the smartphone-app-based nature of the interface makes it harder for exploiters to get upvotes for multiple accounts.
I think the benefit is more social than technical: it's a "big" account saying "If you make a post that satisfies conditions X, Y, and Z, I will upvote it even if it doesn't look like a traditional 'high quality' social media post". That's good for people new to the platform who might not know anybody willing to upvote them. And it's also good for people who might question whether what they have to say is 'good enough' to justify a blockchain post -- the ecosystem around the app establishes the norm that a stepcount of 5k or more accompanied by a microblog is a valued post.
The analogy would be that writing "lines of code" could be something worth rewarding, just like getting steps in, even if it doesn't exactly look like a traditional blog post. I think there's a natural inclination of software developers to only want to post things when they have something interesting to show off, which leads to a pattern of a low number of posts rather than consistently engaging with the chain.