@terryenglish @LarryFoulke @endlessmike @icameheretoawoo I don't think it's the blockbot, I think it probably has more to do with the changes being pushed to the database.
Could be easily fixed by creating a delay (of about 1-2 seconds) in which only the last block state selected (by the blocking user) is issued to make changes to the rest of the database. Instead of what it is now, which is pushing those changes effective immediately on request and fulfilling all subsequent requests ignoring none of them
So yeah, he could do it for a few days but someone would fix that shit