@discord Thank you for replying. I did open a request. Support stated that the "violation" was confirmed, and referred me to the original vague email. I would just like to what happened, because I don't know.
My @discord account got banned. Pretty sure I wasn't compromised, so I must've done *something* wrong. I honestly don't know what or when; support gave me a canned response (#18259542). Without a proper justification, I worry that I may unwittingly trigger a future ban...
Hey, I’ve got a brand new sponsor this week, it’s @probely! Tired of poor coverage and false positives with your DAST scanner? Reinvent web application security. Try Probely today! https://t.co/3EHsQJtE97
@chbm Some guesses: 1 - It's significantly easier/faster to prototype different approaches in userspace vs having them in the kernel. 2. Using UDP vs creating a new protocol improves the chances of the traffic not being blocked by firewalls/middleboxes :)