Nope, we’re largely at the defaults here. Those accounts in the screenshot above were still at TL0 when I deleted them… I suspect I caught them in the midst of working their way through the TL1 requirements. You can see how the topic views were likely populated in a secondary pass in that first screenshot.
2 Likes
Same for us. The ones I saw were all ads for some ed-tech software.
I started with that, but they were spawning so quickly, it was more effective to suspend all the identifiable accounts and turn on account approvals for now.
Since I’m reviewing all new accounts, I also caught on to a new set that concerns me – mostly fldubai.com domains (plus a few grr.la , pokemail.net on the same IP addresses). Started at a trickle, but picking up speed.
3 Likes
Yes, we’re getting the same domains. It’d be nice to have the option to block the entire email domain when deleting a user (instead of needing to do it manually):
A fourth option like Delete and block email host (spam.example.com) would be beautiful.
Yes, I know we could invert it and use an allowlist instead, but as a technical community we have lots of folks that have self-hosted emails like discourse@mbauman.com so I’m loathe to take that step.