Conversation
b4eefbf to
9403b1d
Compare
|
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. |
|
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 |
|
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 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? |
5306339 to
5fb8fb6
Compare
|
I edited the regex, so it only matches the contact and replaces
|
No description provided.