[opheliate]

I agree it’s not a TOS violation, but I do think it could potentially be a shitty move to post the ASN from which a specific user is connecting to your service, if they’ve not said it’s okay for you to do so.

If you’re from a small town with a local ISP, associating that town with your first name could be enough to specifically identify you, with the help of yellow-pages directory sites. Even just knowing someone’s state or country is a data point that can be used to narrow down their identity. For the privacy minded, this could be very unfortunate.

I’m not sure why you would be publicly posting the ASN from which a user is connecting anyway? Could you explain the context a bit more here?

[CameronNemo]

Where did they state this was users' ASNs? I only read that they posted a list of them, not associated with any users.

[opheliate]

Good point, I think I misinterpreted the conversation in the second screenshot.

I think the point is still relevant though: if these are the ASNs connected to a server which you know has 10 active users, for example, then there is still a potential privacy concern.

[bottiger1]

We have 40+ servers, the ASNs did not have any other information tied to it like usernames as I had already mentioned.

This is a clear case of gross negligence by Discord.

Even if there was a potential privacy concern, that does not warrant an instant ban with no warning especially from a 7 year old account that is in charge of a Discord server for thousands of users and paying Discord $95/month in the form of boosts.

[jrflowers]

> This is a clear case of gross negligence by Discord.

I agree. This is clear because you’ve explained the context wherein you were posting those ASNs, and it is obviously not something anybody would have an issue with because