frustrating thing: it's using a federation trick that I also use to identify fetch aliases (when an instance uses multiple domains to bypass Authorized Fetch), which is annoying because I'll have to share the instructions for that in order to explain how this one works. And that means the KF harassment communities will just go and deploy the same mitigation and I won't be able to block them anymore ​​