You are viewing a single comment's thread from:

RE: Community Update - Applications of the MUTE Function 1/25/22

in #vyb3 years ago

My approach here is technical. This means I can be subject to action with some ignorance of the greater picture. It's also the reason these actions are transparent. I read @manorvillemike's statement differently than perhaps I should have.

I'll take another look.

Sort:  

Now I'm wondering what has just happened to my recent post https://www.vybrainium.com/vyb/@frot/the-flu-renamed-every-two-years-is-still-the-flu-r6a6bg

It had 52 upvotes and the rewards were showing at approx 20VYB

Now the rewards are showing at zero and all the upvotes from accounts with any VYB are not showing. But they are still showing on Peakd so I know that I previously had upvotes that would pay out in VYB.

image.png

There seems to be heaps of other accounts having the same issue:

image.png

Sorry, this seems to be a front-end display issue resulting from the recent switch from a 4-day voting window to 8 days. eonwarped is working on fixing this issue.

Basically, the front-end is displaying the post as if it had already paid out (because 4 days has already passed). Since zero VYB has already been paid out, it is showing zero.

The errant display will hopefully be fixed shortly.

Right, that makes sense - glad to hear it's nothing too major.

Thanks for the update.

You're not muted on VYB. Only one person's article has been muted and it hasn't been any of yours. It has to be a front-end issue. @trostparadox? Did you get any error reports like this at all? I just read a similar error in discord from @onealfa. So, the issue is not isolated. No reasons exist for muting either individual.

Accounts verified not muted by terminal.

Hello. trostparadox replied back on discord:

I think this is merely a front end display issue because of the change in voting window from 4 to 8 days.

He contacted eonwarped and eon confirms it's a front end issue. He states:

From eon: "Getting fixed for new posts, need to backfill indexing."

The problem will be corrected soon across the front end.

Right, that makes sense - glad to hear it's nothing too major.

Thanks for the update.