Lock down API events to stop mass scraping #6811
Replies: 2 comments
-
This is not scrapping, but passive sniffing. You can't stop that.
It's worth noting that Discord has already made some changes to reduce the amount of unnecessary information sent to the client that can be used for sniffing (although the main aim was probably to reduce the bandwidth used). Unfortunately, overall, even if you limit the information sent “by default”, it will still be possible to collect it in other ways. In conclusion, I think it's pointless even trying to do anything about it. The best we can do is to educate members not to divulge personal information in nicknames, biographies and status, and to avoid linking their social network accounts to their accounts. There's no other way. |
Beta Was this translation helpful? Give feedback.
-
Even if one can still access information in other ways, it is unnecessary to send such information. For instance, even if a user doesn’t have access to a specific channel in a guild, they can still see some information, like the channel’s name, through the client. These pieces of information are not useful and could be hidden. |
Beta Was this translation helpful? Give feedback.
-
Currently, users who are self-botting can join a server and collect a bunch of normally hidden info without doing anything. This info has been made public numerous times on third party sites where the intended outcome is to enable harassment, doxxing, and raiding.
A good thing to start off with would be bans, as ban information is one of the key features of such sites.
Beta Was this translation helpful? Give feedback.
All reactions