Revert "add unusual_dm_activity_until to member object (#7650)"
#7656
Conversation
This reverts commit 1520a81. Apolgies folks - I looked up the wrong attribute on the PR. Rolling back while we work out if this should be enabled as public or not. Totally my fault for not looking properly. The version of the docs platform will make these issues far less of a problem (or 🤞🏻 get rid of them entirely).
…" (discord#7656) This reverts commit 1520a81. Apolgies folks - I looked up the wrong attribute on the PR. Rolling back while we work out if this should be enabled as public or not. Totally my fault for not looking properly. The version of the docs platform will make these issues far less of a problem (or 🤞🏻 get rid of them entirely).
|
It's disappointing that this is unlikely to be made public. Yet another important piece of data we're not allowed to use to at least make a small part of Discord a semi-safe space. |
|
This will most likely cause many false flags. I don't think you should be banning people based on this; it's not fool-proof nor fully accurate. |
|
I agree that in isolation it shouldn't be used to ban. No doubt that's why they're called "signals" in the UI. But when used in combination with other metrics such as:
Then there's high confidence in removing someone, or at least flagging them to the mods for manual removal. Could we get this data by just using a puppeted user account? Sure. But we'd prefer not to break discord's terms. |
|
this field is exposed in the bot API, but is undocumented and so usage is not recommended |
This reverts commit 1520a81.
Apolgies folks - I looked up the wrong attribute on the PR. Rolling back while we work out if this should be enabled as public or not (looks unlikely tbh). Totally my fault for not looking properly.
The version of the docs platform will make these issues far less of a problem (or 🤞🏻 get rid of them entirely).