pull down to refresh
291 sats \ 14 replies \ @grayruby 1 Apr \ parent \ on: Million Sat Madness 2 - Is it necessary for stackers to hide their identity? meta
I am pro stackers being able to hide. That being said, in these contests I don't think hidden stackers should be able to win top prizes (so maybe not eligible for top 3 or 5). Should be some trade off for anonymity.
It's kind of odd to have a contest and have no idea who the top 3 winners were. I am certain you were amongst the top 3 if not number 1 and for all you contribute to the community I think that is well deserved but in my opinion the purpose of these contests should be to drive new users and engagement to the site.
When I put myself in the shoes of a new stacker, or even a less frequent stacker who is intrigued by the contest. Having no daily rewards to keep them interested, a top heavy zaprank algo, and not having a clue who the top 3 participants are so you can see what they are doing to rank so well is a horrible new user experience.
This doesn't change your point, because it's about optics, but the second and third place finishers can be inferred from the current rewards page. Neither ended up being hiders.
Something is screwed up with the estimated rewards and rankings algorithm.
reply
This doesn't change your point, because it's about optics, but the second and third place finishers can be inferred from the current rewards page. Neither ended up being hiders.
I don't know what you mean by this. I can't tell who came in 2nd or 3rd based on the current rankings. I don't see anyone with more sats than DavidW and we know he finished 4th.
reply
It's not the current rankings. Our MSM rewards are included in "stacked".
Do we know davidw finished fourth? If so, 2nd and 4th can be inferred from that page.
reply
reply
reply
It was me! But apparently I was getting paid for past performance. Classic mistake SN.
reply
reply
Well now we know it was a glitch.
I was 2nd and davidw was 3rd.
reply
Did you get 3rd place? 😉
reply
No. I got second...in February. That glitch was quite the godsend.
reply