-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Poll: Can projects with country or institutional based IP restrictions be whitelisted? #267
Comments
When project admins themselves block certain countries from participating for no justified reason, acting contrary to the spirit of openness and cooperation, such project should not be whitelisted. However, this never happened as far as I know. All existing geo-restrictions are imposed by third parties and project admins can't do anything with it. So I'm voting Yes. |
I'm from Russia. It's easy to guess which vote I'll choose. |
as i understand if vote Yes, this means DENIS@home will be whitelisted. They have weird university network security but if vote No, then by result of this poll SiDock must be blacklisted, cause it is banned for Ukrainian crunchers (as well as Rakesearch, Gerasim, SPT which are not whitelisted at this moment) i'm voting Yes |
What is the current policy of Gridcoin? In other words, currently is "IP restrictions" used in the determination as to whether a project is whitelisted or not? |
|
I would think a yes would mean that both would be able to be whitelisted. I think the the final say should be the Vote. Its hard to rationalize not whitelisting a project because 0.001% of crunchers cannot access. |
I would argue that a good chuck crunchers have at least 1 project that they are not eligible to due to hardware/software limitations. Much more then location limitations. |
These could change at any time. I feel that the whitelist should be independent of the whims of Government and/or entities that are out of the control of the projects and the gridcoin community. The Gridcoin Whitelist Vote should be the final say.
The text was updated successfully, but these errors were encountered: