Live voting explanation

Originally posted by: lostloveforever

My approximated guess of how live voting works.

Explanation of Live voting:

The live voting provides the result in form of % of positive votes which is calculated as ((positive votes)/(positive votes+ negative votes))*100

Display functionality: The voting system requires you to check in, meaning system is aware of maximum number of votes which can be expected. Let's take it as 100. So when people keep on voting, the display should most probably is only displaying the number of positive votes only. Like suppose 65 people vote positively, means the % cannot be less than 65 in even worse case scenario. Suppose nearing the end or at end, there are less than 35 negative votes, meaning thereby that final % will go up(people checked in but didn't vote at all)

So there is faster movement near the end moment based on number of negative votes or "not cast" votes are accounted for. There can be different approximation algorithm to predict it within limit and is subject to network latency and queue clearing at server end.

Originally posted by: Rithu0203

Not able to guess, coz many possible ways to implement it. Not clear about the checkin time itself, why do they need it and whether it affects vote percentage.

But, whatever it may be, it looks like they are doing trial run in BB, next versions will be used in their other shows. These votings are just a way to shift people to internet platform, and there by to earn more money. Basically, they are finding ways to earn more money.

Originally posted by: lostloveforever

My approximated guess of how live voting works.

Explanation of Live voting:

The live voting provides the result in form of % of positive votes which is calculated as ((positive votes)/(positive votes+ negative votes))*100

Display functionality: The voting system requires you to check in, meaning system is aware of maximum number of votes which can be expected. Let's take it as 100. So when people keep on voting, the display should most probably is only displaying the number of positive votes only. Like suppose 65 people vote positively, means the % cannot be less than 65 in even worse case scenario. Suppose nearing the end or at end, there are less than 35 negative votes, meaning thereby that final % will go up(people checked in but didn't vote at all)

So there is faster movement near the end moment based on number of negative votes or "not cast" votes are accounted for. There can be different approximation algorithm to predict it within limit and is subject to network latency and queue clearing at server end.

Originally posted by: NathuPyare

but in that case 'No' votes and "not cast" votes would become a greater deciding factor rather than "yes' votes" 😕

for ex - out of 100 votes, lets say only 35 vote 'yes' for A, 5 vote 'no' for A, and 60 votes are "not cast".. then the final result would be 35 + 60 = 95 > 95%

while, in contrast, lets consider - out of 100 votes, 35 votes 'yes'' for A, 65 vote 'No' for A and 5 votes are 'not cast' then the percentage would be 35+5 = 40 > 40% only, even though 35 voted 'yes' in both the scenario...

so doesn't it make the 'no' and 'not cast' votes more important then the 'yes' votes? 😕

Originally posted by: I_M_SultaN

gupta get 71percent

but that was fake at that time

😆