---
title: "Discussion on \"Stop one person claiming your Python free tier twice: Gmail dots, plus tags and googlemail.com\" | Hashnode"
description: "Discussion on \"Stop one person claiming your Python free tier twice: Gmail dots, plus tags and googlemail.com\". A small email normaliser, a trial_claims table with a unique key, and one transaction around the grant, in Django, SQLAlchemy and plain sqlite3"
url: "https://hashnode.com/posts/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com/6ace10ffcdcf6fd21b1b2350"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [Stop one person claiming your Python free tier twice: Gmail dots, plus tags and googlemail.com](https://elijahbrown.hashnode.dev/stop-one-person-claiming-your-python-free-tier-twice-gmail-dots-plus-tags-and-googlemail-com?utm_source=hashnode&utm_medium=feed)

A small email normaliser, a trial\_claims table with a unique key, and one transaction around the grant, in Django, SQLAlchemy and plain sqlite3

Oct 13 · 9 min read · elijahbrown.hashnode.dev  
Read the article

-   [#python](https://hashnode.com/tag/python)
-   [#django](https://hashnode.com/tag/django)
-   [#saas](https://hashnode.com/tag/saas)
-   [#webdev](https://hashnode.com/tag/webdev)

## Written by

[Elijah Brown](https://hashnode.com/@elijahbrown)

@elijahbrown · Dubai, UAE

  
[View profile](https://hashnode.com/@elijahbrown)

Building Orisift. Writing about DNS, phones and forms.

I'm building Orisift, a developer API that checks phone numbers, email domains and IP addresses against reference data, and says what it couldn't find out. I write about the small standards details that decide how forms behave.

## Responses 1

Markdown supported · ⌘↵ to post

[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?
