Protect event host emails from email harvesting

[annakrystalli]

A number of approaches discussed in these posts 1 & 2. Suggest going for:

1. a mix of machine but not human readable character encoding (eg using https://realpython.com/python-encodings-guide/) or
2. Introducing html comments into the address? (won't be able to deploy mailto: functionality though)
3. This django snippet also looks like an interesting approach! It uses a substitution cipher with a different key for every page load. It basically produces equivalent Javascript code for an email address. This code when executed by browser make it mailto link.(If implemented, please remember to credit in a comment in the code).

[annakrystalli]

Further suggestions, help evaluating approaches and help with implementation welcome!

There are two main places in templates currently where emails appear:

• Our email in the footer:

  reprohack_site/reprohack_hub/templates/footer.html

  Line 33 in 0911ace

  <a href="mailto:reprohack.team@googlemail.com">

• Event hosts' contact email on each event page (much more important to protect):

  reprohack_site/reprohack_hub/templates/event/event_detail.html

  Line 63 in bc053d5

  <a href="mailto:{{event.contact_email}}">

Other places links to contact us may appear are in markdown pages, for example

reprohack_site/markdown_pages/data_protection_and_privacy_policy.md

Line 76 in 0911ace

Please feel free to contact us at [reprohack.team@googlemail.com](mailto:reprohack.team@googlemail.com) if:

. I imagine this may need another approach. However, such pages will mainly contain our own contact emails which we are less bothered about. The key is to protect the emails of community members.