These “Automated protocol deliverability probe” signup attempts can eat my whole ass.
Short screen captured video of me scrolling through a list of attempted signups from this godforsaken bot.
Replying to @fname@kamloops.social
@fname i made a trigger in the database refusing any username with the 2 char prefix they all share lol - been quiet since
Replying to @jippi@expressional.social
@jippi
I’ve read about people doing this. I’m hesitant to start messing with my DB at the command-line level. 😬
Replying to @fname@kamloops.social
@fname yeah I get that, I got tired of banning networks and other things to try and sniff them out, so the trigger was bullet proof way to fix it with no side effects
ALTER TABLE public.user_invite_requests
ADD CONSTRAINT invite_block_spam_bot
CHECK (text NOT ILIKE 'Automated protocol deliverability probe');
and super easy to drop again - it just refuses at the database level any signup reason with the exact text they use
Replying to @jippi@expressional.social
@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?
Replying to @fname@kamloops.social
@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
Replying to @jippi@expressional.social
@jippi
I’m running Glitch also.
Replying to @fname@kamloops.social
@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```
Replying to @fname@kamloops.social
@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
Replying to @jippi@expressional.social
@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.