A small update on the CryptoCompany Voting Service. Long story short: I had to introduce the rule that the service only votes for posts that are not older than 24 hours when they are submitted.
The longer story | What, how, why:
The voting service is becoming more and more popular - understandable because of the high vote it gives, with such a low investment. After all, the voter can still be described as a money glitch. If the voting service runs out of mana and drops drastically below 80% voting mana, I have paused the submission of new vote requests and let his mana regenerate again. As soon as the mana was back above 95%, I switched it back on. This has worked really well so far. The voting service has been around for about 4 months now and I've had to take a short break of a few hours 2 or 3 times all in all.
We had such a further break about 2 days ago - and I "had" to switch off the voting service for about a day. Long story short: after it went back online, there were several users who immediately pushed a whole pile of posts into the service. This may be just about acceptable for one or two users, but it forces the voting service back into pause mode as soon as several users decide to act in this way.
Do you see where this would lead? The service would go from pause to pause and whoever is quickest in between would quickly add all their unvoted articles. The voter would be drained again and would have to be sent back to the pause mode.
I considered this and found several solutions, one of which I had to choose.
I have decided in favour of the 24-hour variant. This means that an article is only valid for the voter if the post to be voted on is not older than 24 hours. This seems to me to be the most user-friendly solution at the moment. This service should be available to everyone (except spammers) - and not just the fastest. (In the end, the particularly clever ones would write bots again to operate the voter via script and a regular user would have 0 chance to use the voting service... nobody wants that. [Except the tech and bot freaks. 😉 Dear tech freaks, don't take it bad on me, I love tech, too!])
This measure should prevent whole stacks of articles from a user being "pushed in" afterwards, so that the service's break can really be used to regenerate the mana and is not basically irrelevant because a flood of articles flows in after the reopening - I think you understand the system.
Alternatively, I could have lowered the vote value to reduce the mana required per vote, but this would have negatively affected all users unless compensated by additional HP - I didn't want to/couldn't do that. The voter acts with more than 75,000 HP... (Does somebody want to sponsor/invest this? I'm open to talk about this kind of support!) I could also have asked for a higher CCD stake - but again, those who have particularly high stats win... CryptoCompany should be there for everyone; not just for the rich or technically smart Hivians.
Why the current solution is currently the best:
The current solution means you can continue to have all your postings voted at the previous price/performance ratio - if you submit them to the Voter within the first 24 hours. If you have always pushed all your articles into the voting service, you can continue to do so - as long as you submit them within the first 24 hours.
Long-term perspective:
I will always make sure that I provide a fair distribution of votes. Everyone who writes qualified articles should get their votes. However, pure logic already says (at least for me, from the beginning on I planned this service) that the current system will have to be adjusted again at some point. A further reduction of the time window would be unusual. Since the voter uses over 75,000 HP to vote you, I can't simply set up a second voting account easily - unless a noble delegator can be found. (How raises the hand? Talk to me!)
What could happen: it could well be that I adjust the price/performance ratio in the medium or long term. Currently you get a 100% vote for 1000 CCD - I could reduce this slightly in order to be able to serve more vote requests in the end. However, this will be done in small steps and ideally always in balance with more HP, so that the voter always remains as highly profitable as possible. If there are any further changes in the future, I will announce them here again.
For now, however, everything will remain as it is and the voting service will become more and more profitable from day to day as our usable HP increases. But remember: I think it is logical that the voting service will have to be adapted at some point. If you have any suggestions on how you would do this, I would be happy to read about them in the comments or talk with you. Dynamic calculation? A limit above which only CCD stakers are voted? Something different? I'm looking forward to your ideas!
Any questions about? Please feel free to ask in the comments.
Now it only remains for me to say...
Thank you for being here. Remember: YOU. ARE. AWESOME!
See you later in the comments &
make the best out of the your day (and your postings)!
