@Lea @mephisto :verified: @Admin (of friendica.utzer.de) The fact that you wrote "only about one research instance" shows to me that you had no prior understanding of how the troll works before deploying it publicly. This was reckless and absolutely not good research.

Requests to your domain will continue long after you've pulled the DNS record because Fediverse servers assume good faith from remote hosts, and you've carelessly betrayed this trust. Next time please ask someone, anyone who's already running a server before doing any kind of research involving the Fediverse.

@Admin (of friendica.utzer.de) And you're positive you added *.mastotroll.netz.org to your block list?

@utzer [Friendica] It's possible a worker process was already running, busy adding UpdateGServer tasks using the cached version of the block list without the new pattern, but then when it was time to process these tasks, it went really fast because it was using the updated block list and aborting early

@Hypolite Petovan yes, exactly like that with the star, now the queue is on 0 again.

@Lea Thanks, I appreciate the apology, and it’s definitely okay, even if a little late, to ask questions!

@Lea Yes, you're right, the effect is more severe for smaller servers without enough resource margin to handle even tens of thousands of bogus extra background tasks. In the original attack, some servers reported having stored millions of bogus server records that slowed their server to a crawl while trying to update them.