Where is documentation for user signals?

[madscientista]

Description

I would like to see documentation for these signals so they can be automated over bots for spam purposes. This is in the new moderation feature "members" tab.

I do not see anything in the API documentation over it

Steps to Reproduce

N/A

Expected Behavior

N/A

Current Behavior

N/A

Screenshots/Videos

No response

Client and System Information

N/A

[KubLuk24]

For anyone who may stumble upon this as it seems like this thread ranks highly in search engines:
As of the time of writing this, you cannot receive user signals via the API.

[TwilightZebby]

For anyone who may stumble upon this as it seems like this thread ranks highly in search engines: As of the time of writing this, you cannot receive user signals via the API.

Fwiw, three out of four all of these signals have been in the public API for some time.

• "Timed Out" is the communication_disabled_until flag in the Guild Member object (API Docs link)
• "Unusual Account Activity", I believe, is the SPAMMER (1 << 20) Flag in the User object's flags/public_flags field. (Could be wrong since this one is based on my observation. This flag is not officially documented though)
• "Quarantined", I believe, is the AUTOMOD_QUARANTINED_USERNAME (1 << 7) Flag within the Guild Member's flags field (API Docs link)
  • and/or the officially undocumented AUTOMOD_QUARANTINED_CLAN_TAG (1 << 10) Flag in the same field too?

While writing this, I did notice a unusual_dm_activity_until field on Guild Member objects (also officially undocumented), which might be the 4th signal, "Unusual DM Activity"?

Either way, the data is there in the API, just some of it is officially undocumented from what it seems like.

[KubLuk24]

For anyone who may stumble upon this as it seems like this thread ranks highly in search engines: As of the time of writing this, you cannot receive user signals via the API.

Fwiw, three out of four all of these signals have been in the public API for some time.

• "Timed Out" is the communication_disabled_until flag in the Guild Member object (API Docs link)

• "Unusual Account Activity", I believe, is the SPAMMER (1 << 20) Flag in the User object's flags/public_flags field. (Could be wrong since this one is based on my observation. This flag is not officially documented though)

• "Quarantined", I believe, is the AUTOMOD_QUARANTINED_USERNAME (1 << 7) Flag within the Guild Member's flags field (API Docs link)

  • and/or the officially undocumented AUTOMOD_QUARANTINED_CLAN_TAG (1 << 10) Flag in the same field too?

While writing this, I did notice a unusual_dm_activity_until field on Guild Member objects (also officially undocumented), which might be the 4th signal, "Unusual DM Activity"?

Either way, the data is there in the API, just some of it is officially undocumented from what it seems like.

I must be going blind again missing all of that lol.
I also completely disregarded "timed out" being a signal for some reason :D
Thanks for the clarification and sorry for the incorrect reply.

[ManHatos]

• "Unusual Account Activity", I believe, is the SPAMMER (1 << 20) Flag in the User object's flags/public_flags field. (Could be wrong since this one is based on my observation. This flag is not officially documented though)

Pretty sure it is officially undocumented, see #3961 (comment)

[Swyter]

Good to know. I'm also interested in programmatically getting the Members tab info that says if the member joined through Server Discovery or an invite link.

I think it's useful as another signal to curb spam, as many of these fraudsters doing commissions join through there.

[Swyter]

Answering myself, the Members tab seems to use the undocumented https://discord.com/api/v9/guilds/:guild/members-search API.

More info here: #6781 (a common complaint seems to be that it's slow to show new members, a bit of a shame to enforce a stronger verification for people coming from Server Discovery, which is a spammer magnet), discord/discord-api-spec#34.

Each returned object has the following fields:

• join_source_type (1 for Bot Invite, 2 for integration (reportedly), 3 for Server Discovery, 4 for Student Hub, 5 for a user-generated invite (seemingly), 6 for the Server Web page or vanity invites (official invites in general, seemingly), 7 for Manual Verification)
• source_invite_code (null when coming from Server Discovery, otherwise a string with the random soup of characters of a invite string or the slug for the vanity one)
• inviter_id (null when coming from Server Discovery or official links, otherwise the user ID string who generated the invite)
• member object with the full thing and a user object inside.
  • user (where the public_flags and flags fields are 1048576 / 0x4000000 / 1 << 20 / SPAMMER when the user is tagged as "Engaged in suspected spam activity" in the UI, as mentioned above)

[ManHatos]

The guild member object's unusual_dm_activity_until property is now documented. #7650

[markmandel]

Apologies folks - rolling #7650 back - I read the wrong attribute on the PR 🤦🏻