@jippi
Ok, so I’m reconsidering my position on this. Where would I enter these commands. And how would I undo these actions later, if I chose to?

@jippi
Hi again! So I got tired of dealing with these bot signups and attempted what you suggested. This is the output:
postgres=# ALTER TABLE public.user_invite_requests
ADD CONSTRAINT invite_block_spam_bot
CHECK (text NOT ILIKE 'Automated protocol deliverability probe');
ERROR: relation "public.user_invite_requests" does not exist

Any ideas?

@fname try to remove the public. part if the name - I use glitch fork so actually not sure if this table exists in vanilla mastodon

@jippi
I’m running Glitch also.

@jippi
Output:

```root@89d96e5b3b1e:/# su postgres
postgres@89d96e5b3b1e:/$ psql
psql (18.6 (Debian 18.6-1.pgdg13+2))
Type "help" for help.

postgres=# ALTER TABLE user_invite_requests
postgres-# ADD CONSTRAINT invite_block_spam_bot
postgres-# CHECK (text NOT ILIKE 'Automated protocol deliverability probe');
ERROR: relation "user_invite_requests" does not exist```

@fname i dont know your setup, but it might be connecting to the default Postgres database and not the one mastodon is using

Try to change the database to the one in your setttings/env file first

Maybe it’s mastodon or mastodon_production in name

@jippi
I'm running under docker, so the Mastodon DB is running in its own dedicated container.

Nevermind. I didn't mean to draw you into a tech-support conversation. I'll just live with the bots until they implement a fix in the software. 😀

Thanks for your time.