Alright, hey everyone, me again discussing POSH. After Twitter abruptly halted our service a few days before their initial deadline it put a little fire under our butts to figure out a solution and quicker than expected. After much thought into it I think I've come with a pretty good and reasonable plan that I'd like to share and get some feedback on. Let me first list the issues and my thoughts around it.
Problem:
The automated part of @poshtoken became completely obsolete, while this whole process may look simple on the outside, we've put quite a bit of work into it working smoothly and distributing both POSH and Hive fairly. For instance the grouping together many tweets of shares of the same post, editing them into the same comment and mentioning all the sharers who are registered with the website. Then after a day calculating their performance on Twitter to distribute the rewards after 7 days based on the performance.
It would've sucked to let all of that go and to instead have everyone manually share twitter embeds under posts they shared. At the same time this could've caused for a lot of "spam" since each comment is separate and it would've made life way harder for curators to have to curate each comment on their own of the same post rather than curate them all with one vote.Our idea to allow non-hive accounts to POSH and earn hive+posh in the form of another currency (with added fees) if they don't already have a hive account but would like to earn a little crypto for their reach. This was one of the ideas that bummed me out the most that the Twitter API put in the dirt. While many people had great ideas they put forward my way (thank you again everyone), I really wanted to figure out a way to still make this work even without the API functioning.
Spreading out POSH in an automated way based on performance. While this wasn't a big problem it was nice to have it all work in an automated way. While some people were trying to abuse it we implemented ways for us to ban the users from earning POSH and Hive rewards. Even though this problem could've easily been fixed for instance sending out the daily POSH rewards based on how @poshtoken curated the comments that day, I think this problem can also be solved like the ones above with our solution.
Alright, so this is the solution we had in mind, I'll address some of the reasons we want to go this way as it involves some other plans we've had in the future and then after mention the con involved with it.
Solution:
After careful consideration and shoutout to @nickydee who came closest with her idea to it, I think the best way forward would be to have everyone POSH'ing come to the website and easily input their twitter share there.
This would allow @poshtoken to still operate the way it used to in the past. It would register the input, who the link in the tweet belongs to, share it under the post and know who to send rewards to based on who inputted it on the website being logged in with their account. It would basically remove the need for the API and every sharer would have to manually share the link on the website each time they POSH something.
This solution would still work with non-hive accounts as long as they are signed on to the website with their Twitter or Reddit account, another input where they can choose which address to receive rewards on and everything else would be handled by the service.
We've been meaning to make the website more "visit" friendly for a while now and are currently working on revamping it. We've been thinking of things like daily login rewards, stats/achievements based on how many POSH tweets you create, how your performance is. Give people "soulbound" nft's as achievements with some passive POSH earnings, gamifying the project and actions more.
The con:
This of course means people will have to share each tweet manually. It may not be a big issue and is currently the smallest hindrance out of any solution we've thought of and it will enable quite a lot of ideas and plans we have been brewing for a while.
All in all I think this would be the best change, with added incentives to visit the website people may overcome the fact that they have to login once to share their links on there.
Anyway, let me know your thoughts behind it and if you see any other issues we may not have thought about with this solution. Any feedback is appreciated!
Thanks for reading and your continued support for POSH!
