Flackle retweeted
If you want to join @GetFlackle and test it out. Here's my beta invite code: CUWVFD45, 5 slots only.
Enter it here: flackle.com/signup
Replying to @Rimmy_Downunder
I think the main frustrating part here, is how detectable it is. You mentioned yourself that an account is sending the four same pictures to pretty much every single friend on their friends list and most channels of each server they're in, and it's true that's a pretty clear cut case for discord to work from, but on top of that, if you combine it with the fact that these things are happening most likely from a completely fresh IP/network (assuming it's not driven by a compromised device, but instead a stolen token), it's so clear-cut, it's almost like discord is letting it happen.
Normally with things like this you might first think to hash match the images and then block them, which is still a viable option, however the bad actors can easily just change something extremely minuscule which is where perceptual hashing comes in, which I admit does have its drawbacks, but like I said prior, the pattern here is extremely specific even aside from hash matching.
An existing token is suddenly being used from a new IP/location/client, which then immediately posts the same photos across a bunch of servers and channels within seconds (even across minutes, it's still a strong signal). It's a pretty narrow combination. Any one of those alone might be normal but all of them together is a red flag.
Still the argument could be made that some people might be wrongfully flagged in this situation, if, say they turned a VPN on, and in the same following moment had something they really wanted to share across all of their friends and communities. It's pretty unlikely but I'd still like to acknowledge the possibility, because in a perfect world, discord would've fought for its users, and then the spam would've adapted to become more human. But in that case, if it's not 100% accurate, just don't ban the user. Actually, REGARDLESS, even if it is accurate, the action isn't to ban the user. All you have to do is prevent the sending, flag their account, lock their session, and force a password reset.
So the literal worst case scenario with a fix is users needing to re log in.
The worst case scenario without is what you're living in, and Discord chose that for you. Servers of every size getting flooded with this constantly.
At its core this is a platform-wide moderation issue. It shouldn't be down to communities to build bots to solve something so widespread.
Flackle retweeted
Replying to @KellytoyDK
yeah i don’t think Discord, or a lot of other people, realize the recent outrage isn’t just driven by age verification (although that’s obviously a big factor)
it’s really a culmination of anger that’s been building up for years while people watch the platform go through enshittification - cuts to moderation, lack of adequate support, community programs getting cut, more and more greedy monetization, etc
age verification just feels like the thing that finally pushed a lot of people over the edge.
what an out of touch and almost condescending post to make?
this has been one of if not the most opposed decision discord has made in years. their initial rollout even had enough backlash for them to delay it in the first place.
is this who you want to trust with your data and online life?
Flackle retweeted
Replying to @DiscordPreviews
1. free for everyone
2. type whatever you want, no presets, still moderated and safe
3. server admins decide if they want them enabled in their communities
4. don't wanna see other people's? turn them off client side
no presets, no premium required 🐦
Product regression as a perk. Only at Discord 🫶
Discord in 2023: usernames need to be simple because incorrect casing and special characters make people difficult to find.
Discord in 2026: would you pay us to put confusing casing and special characters back?
Beyond the obvious backtracking, this creates real impersonation and safety problems when visually identical usernames become harder to distinguish.








