Add filter to do a basic email obfuscation #340
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Email Obfuscation Implementation
Context
This implementation addresses the email protection concern raised in the Compiler Research Group Discord (November 7, 2025). The discussion highlighted the need to protect team members' email addresses from automated harvesting while maintaining human readability.
Implementation Details
Added a reusable Jekyll include component that transforms email addresses using simple text substitution:
@becomes[at].becomes[dot]For example:
Usage
To display an obfuscated email address in any template, use:
{% include email-display.html email=member.email %}Implementation Details
The core logic is implemented in
email-display.html:{% assign obfuscated_email = include.email | replace: "@", "[at]" | replace: ".", "[dot]" %} <p><i>email: {{ obfuscated_email }}</i></p>Security Note
This implementation provides basic protection against automated email harvesting while maintaining human readability. Future enhancements could include JavaScript-based solutions or contact forms for additional security.