Yeah honestly I don't mind the costs that are coming up to prevent things like that, and especially all the scams and botnets that currently exist there due to how easy it is to create accounts and have bots run them all over the place.
The shitty thing is that we could've easily covered a reasonable cost, something that I'm sure most botnets or profiteers would've gotten blocked by, but this amount is just too absurd at the current stages where Hive and POSH itself isn't that big. Even if we were a billion $ marketcap it would've probably hurt to pay $500k/year for something as simple as API requests.
While POSH is built to bring value to Hive through visiting links, we've maintained it well where we ban abusers/maximizers/bot users on Twitter and aimed for genuine engagement and growth similar to how we run things on Hive. POSH has in many ways encouraged people here to sign up and use Twitter more often so it's not like POSH was just "extracting" value from Twitter but activity was being created and going back over there as well. I can speak for myself that I wouldn't have been active on there at all if it wasn't for POSH for instance.
Either way, will be interesting to see how these changes will affect Twitter and how we'll adapt. POSH still remains as a very cool project with a unique usecase and fair distribution so the sky's the limit of what we can accomplish with that if we keep working on it and spreading over other usecases.
Definitely, I recently revived my Twitter account for Hive and Posh...
This post has been manually curated by the VYB curation project