My voting power took a huge hit today as the voting weight adjustment on SoMee doesn'
My voting power took a huge hit today as the voting weight adjustment on SoMee doesn't seem to be working properly and did not register the voting weight decrease i implemented for comments that way i can save voting power in order to upvote posts at 100%
The result of this has been a hit on my voting power that has put me under 70% mana. To strategize around that while this is fixed, i will only upvote comments from somee.blog or ecency. For now i need to wait a few days until i completely regenerate. I have just reported this problem to Phil via private message on Telegram.
My voting power took a huge hit today as the voting weight adjustment on SoMee doesn'
0
0
0.000
Hey @greywarden100!
Actifit (@actifit) is Hive's flagship Move2Earn Project. We've been building on hive for almost 5 years now and have an active community of 7,000+ subscribers & 600+ active users.
We provide many services on top of hive, supportive to both hive and actifit vision. We've also partnered with many great projects and communities on hive.
We're looking for your vote to support actifit's growth and services on hive blockchain.
Click one of below links to view/vote on the proposal:
Don't get me wrong. I do not regret having given all of those big upvotes to people on comments. The only thing that frustrates me about this is the fact that the adjustment bar is not working and i would have prefered to use some of my upvotes on posts instead. But i am actually happy for all of the people that got big whale upvotes on comments and i won't take them back.
I would be really nice to see some whale vote posts and comments cause I noticed they only vote there fellow whales. Some don't even reply comments or compliments. That's really bad that's why building power on SoMee is kind of difficult we need more people like you.
Thanks Ezuntimmy. There were more people as i years back but they aren't active now. I have no idea why though. Hopefully they return in the near future.
Posted using SoMee
I pray they come back real soon, I don't post on SoMee like I used to but I move around a lot. People dont get upvoted, Just people using the boost package and whale getting the most vote. I might be wrong but I'm just sharing my view. I invited some friends they got tired and left. The platform won't see the growth everyone is hoping for if the big upvote are just among a circle. It gets worst as new user comes in.
What would you consider big upvotes? How many SME per vote would be reasonable in your opinion? Is 1K SME per Upvote good? Problem is that whales upvoting 12K SME per Upvote can't reach out to many people since it would take 100% upvotes and that would just drain their voting power really quick like what happened to me.
Posted using SoMee
Thanks for the update and thanks for informing the team to get this fixed. It's important to wait a minimum of 30 seconds after vp adjustment. If you upvote someone's post as soon as the vp adjustment has been made with waiting for the minimum duration and refreshing the screen, the changes to your vp is not registered (fyi)
That was not the case though. It was far more than 30 seconds and none of my upvotes were at the weight adjusted level but at 100%..
If this matter is not fixed i will only upvote comments from Ecency or Hive since i have never had a problem like that there.
yafet.ashkenazi I have experience this issue before and it took awhile for it to be fixed. Looks like the issue has come back again. I wonder what triggers it when the platform goes through an update for vp adjustment issue to be impacted
Sometimes you also give your response to my post on SOMEEOFFICIAL
So, I have been attempting to isolate this issue since I was notified on it. However, I'm not able to replicate it. I was able to change (via settings and on the slider), the voting power, to 79% and then was able to vote on someone's post at 79% as well. And, the effective comment vote on the blockchain, was indeed 79%.
I did find something in the code that could POTENTIALLY have caused the issue - but i'm not able to replicate w/ or without the change. But, for now, I have adjusted the code.
So, steps to troubleshoot on your part: