-
Notifications
You must be signed in to change notification settings - Fork 164
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
Maintainers page: do not render valid email addresses #220
Comments
Any public address is an "invitation for spam", despite on whether you try to obfuscate it or not, and the mere fact it is so easy for repology to parse these just proves that obfuscation is useless. Most repositories do not obfuscate maintainer emails, and are the very same "huge collections of email addresses", largest of which is GitHub, and no one is complaining. Being of no use, obfuscation makes life harder for legitimate parties such as package users and fellow maintainers. Repology strives to improve collaboration between maintainers, users and software authors, and for that an easy way to contact a person is crucial. So no, repology will not hide emails. |
So a case of "wontfix because others are doing it aswell"? Okay then. |
No, wontfix because there is no problem. |
Well, I just send an email about this, I am opting out of this collaboration. Nobody has been asked to be on this site nor any opt-out mechanism has been put in place. According to recent eu-legislation, this is not correct. This attitude will force maintainers not to publish their email addresses in any form when they are getting handed out like this. And your site runs the risk of being reported for breaking privacy laws, which defies the reason for its existence... then there will be a problem |
In my opinion pages like these: https://repology.org/maintainer/a-burghardt%40gmx.de
are an open invitation for spam. In case the upstream project made efforts to protect their contributors
and maintainers against this, you would render these methods useless.
From the privacy/security point of view it becomes a huge collection of email addresses as the project grows.
I have no immediate solution, but there should be a method which does not reveal the email address and mailto: links unless something has been solved/achieved. Leaving out: capchas by google and other civilrights incompatible technologies and companies.
The text was updated successfully, but these errors were encountered: