2026-09-24 22:03 UTC
@fname@kamloops.social 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
Replies (1)
-
@fname@kamloops.social 2026-09-26 14:00
@jippi@expressional.social 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?