---
title: "Comment by Praneet Brar on \"Stop one person claiming your Python free tier twice: Gmail dots, plus tags and googlemail.com\" | Hashnode"
description: "Keeping the typed address for mail and using the normalised key only for matching is the detail that's easy to skip. The Workspace caveat is a good one too, sin"
url: "https://hashnode.com/posts/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com/6ace10ffcdcf6fd21b1b2350/comment/6ace22f617b8de3575222475"
---

[Discussion](https://hashnode.com/posts/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com/6ace10ffcdcf6fd21b1b2350)

Comment [Stop one person claiming your Python free tier twice: Gmail dots, plus tags and googlemail.com](https://hashnode.com/posts/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com/6ace10ffcdcf6fd21b1b2350)

[Praneet Brar](https://hashnode.com/@praneetbrar)

[Oct 13](https://hashnode.com/posts/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com/6ace10ffcdcf6fd21b1b2350/comment/6ace22f617b8de3575222475)

Keeping the typed address for mail and using the normalised key only for matching is the detail that's easy to skip. The Workspace caveat is a good one too, since j.smith and jsmith can be two different colleagues there. How do you handle a real second person whose address collides with an existing key?
