Skip to content

Conversation

@rubo77
Copy link
Contributor

@rubo77 rubo77 commented Jul 30, 2016

No description provided.

@rubo77 rubo77 force-pushed the email-obfuscate branch 2 times, most recently from b4eefbf to 9403b1d Compare July 30, 2016 07:22
@jplitza
Copy link
Member

jplitza commented Aug 10, 2016

We already have instructions how to remove the owner information if desired. Obfuscating them is strictly inferior to removing them (do you really think bots don't recognize (a), (at), and all the other replacements?). Furthermore, your command does the replacement in all parts of the JSON, which is nuts. For example, node names should not be touched by such a measure.

@jplitza jplitza closed this Aug 10, 2016
@rubo77
Copy link
Contributor Author

rubo77 commented Aug 10, 2016

nodenames are not allowed an @ sign, and removing the information is not an option for us, we want open contacts, so obfuscation is the least we can do, maybe it will stom 50% of the spam-bots

@rubo77
Copy link
Contributor Author

rubo77 commented Aug 12, 2016

Actually, instead of closing this issue, I was sure, the pro's will come up with better suggestions, how to find a better solution (than just replacing @ with (a) ). That's, why I started this PR.

There should be a solution suggested in the README, because just publish all user emails plain in nodes.json is not a good practise. while broadcasting a contact information itself is a good thing.

Maybe we suggest to strip emails from the contact field here?

@rubo77 rubo77 reopened this Aug 12, 2016
@rubo77
Copy link
Contributor Author

rubo77 commented Aug 12, 2016

I edited the regex, so it only matches the contact and replaces @ with at. and added the hint

Be crative with the replacement rule or strip emails completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants