This might be of interest to some projects. Of course one couldn't guarantee the voting couldn't be gamed, but some projects may think it is worth the risk.
Would be nice for developers to include it on their website, to give an opportunity to non-techies.
I could also see a potential for including the voting from within an app itself; e.g. a special 'feature vote' screen in an Android app (based on webview). There, double votes could be (to some extent) be limited by an app-specific cookie (?)
Still voters may be able to go online, log in and vote again, but a person could only vote twice (or more with multiple GitHub accounts).
Guess it would be great if this could be a setting.
Ecco commented about 5 years ago Admin
This might be of interest to some projects. Of course one couldn't guarantee the voting couldn't be gamed, but some projects may think it is worth the risk.
| keunes commented over 4 years ago
Would be nice for developers to include it on their website, to give an opportunity to non-techies. I could also see a potential for including the voting from within an app itself; e.g. a special 'feature vote' screen in an Android app (based on webview). There, double votes could be (to some extent) be limited by an app-specific cookie (?) Still voters may be able to go online, log in and vote again, but a person could only vote twice (or more with multiple GitHub accounts). Guess it would be great if this could be a setting.
| astrofrog commented over 4 years ago
This would be great - Feathub could always provide a separate vote count for authenticated vs anonymous votes.
| spacem commented over 4 years ago
My users don't have github accounts and creating one is a hurdle to them voting or suggesting
| Betree commented almost 2 years ago
Would be nice to have and as @astrofrog says, having two counters would avoid the risk.
Another solution to address this issue is adding the ability to login with other third-parties like Facebook or Google.