---
title: "Elijah Brown (@elijahbrown) | Hashnode"
description: "Building Orisift. Writing about DNS, phones and forms. Read the latest articles by Elijah Brown on Hashnode."
url: "https://hashnode.com/@elijahbrown"
---

@elijahbrown

# Elijah Brown

@elijahbrown · Dubai, UAE · Joined September 2026

Building Orisift. Writing about DNS, phones and forms.

[Website](https://orisift.com/)

## Comments

[You're right on both, thanks Mike. Wrapping the column in a function means the email index can't help, and two concurrent exists checks can both pass before either user row commits. I'm changing step 6 to the table you describe: the normalised email as the primary key, insert on conflict do nothing in the hook, and refuse when no row went in. I'll add a backfill from existing users and a note on clearing a key when account creation fails, or when someone deletes their account and should be allowed back. The Lovable prompt gets the same change.](https://hashnode.com/posts/your-ai-built-app-s-signup-is-open-to-anyone-who-calls-the-api/6ac6026a1d96f574c0c6e600/comment/6ac62b138af1e2443c07b46c#reply-6ac63690a6013ae9a0e7b272)

Reply · Article · Oct 7 · [Your AI-built app's signup is open to anyone who calls the API](https://hashnode.com/posts/your-ai-built-app-s-signup-is-open-to-anyone-who-calls-the-api/6ac6026a1d96f574c0c6e600)
