← All bots

Legal · Discord apps · Developer Portal

Nefarious News privileged intents

Effective September 12, 2026 · Last updated September 19, 2026

Configuration guidance for Nefarious News (application ID 1021496474258911423), based on its reviewed newsfeed source. The client uses discord.Intents.default(), which excludes the three privileged intents.

Do not apply for Message Content, Server Members, or Presence.This bot only sends embeds through Discord's HTTP API. Grant View Channel, Send Messages and Embed Links in its destination channels; a Gateway intent is not a send permission.

On this page · 6 sections

01Reconsideration and fallback functionality

#

Prepared October 26, 2026. No privileged intent requested. This is review material, not a submission receipt or approval.

Feature-specific reconsideration reasoning
The newsfeed consumes external news sources and publishes its own messages. Incoming member messages are not an input, so there is no implemented Message Content dependency to appeal.

Alternatives considered
Publishing outbound feed updates continues with ordinary channel permissions.

Continuity while access is reviewed

No user command is required for the existing scheduled/external feed.

Do not confuse an external news source with a Discord source-message relay.

02Intent matrix

#
  • Message Content — NO. The application has no command prefix, slash-command handler or on_message listener. Headlines come from third-party HTTP/WebSocket feeds, not member messages. Receiving ordinary gateway metadata through library defaults does not make Message Content necessary.
  • Server Members — NO. The bot does not welcome members, assign or inspect roles, ping role lists, or enumerate the member list.
  • Presence — NO. The bot does not read online, idle, DND, or streaming status.

Non-privileged use

  • Guilds — provides channel cache information; the code also supports fetching configured channels over HTTP.
  • Sending embeds uses Discord's HTTP API and channel permissions (View Channel, Send Messages, Embed Links). Guild Messages is a receive-event intent, not a requirement for sending.
  • The reviewed client uses discord.Intents.default(), which enables additional non-privileged events. Those events are not newsfeed feature requirements.

In Developer Portal → Bot, turn off Message Content, Server Members and Presence if any are enabled. Verify the deployed process matches the reviewed source before changing its configuration. A large-server warning does not make these intents necessary for an outbound newsfeed. See Discord's Gateway intent documentation and the Create Message API.

03What does your application do?

#
Nefarious News publishes third-party market headlines from Ainvest, Moomoo and a Benzinga web feed into two configured Discord news channels. If Telegram is configured, Ainvest breaking items are also sent there. Its application code has no member-message handler, prefix commands, slash commands, member-management features or presence features. All three privileged intents are disabled in the reviewed source. Posting embeds uses Discord's HTTP API and channel permissions; it does not require the Guild Messages or Message Content intents. The default library configuration may receive and temporarily cache ordinary gateway metadata, but the newsfeed does not use it to profile members.

04Message Content — do not request

#

If the form still has a Message Content box, leave it unchecked. Paste this if they ask why you do not need it:

We are not requesting Message Content. Nefarious News does not use members' Discord message text, attachments or commands as feature inputs. Headlines are fetched from Ainvest, Moomoo and Benzinga over HTTP/WebSocket. The bot sends embeds to configured channels. Message Content is disabled in the reviewed client and is not needed for delivery.

05Off-platform storage of Discord message content

#
The application does not persist other members' Discord message content. It stores destination channel IDs, third-party article IDs and timestamps for deduplication, and the headline text it publishes itself (source, article ID, title, source timestamp and send timestamp). Deduplication records expire after 7 days during pruning and are capped at 10,000 per source. Headline and operational logs have no automatic expiry in the reviewed source. These headlines originate in external news feeds, not member conversations. The Discord library may also hold ordinary gateway metadata temporarily in memory.

06Proof

#

These real message records show the bot delivering externally sourced headlines. They support the product description; they do not establish a requirement to read members' messages.

View this bot’s evidence →

Questions: Business@nefarious.trading.

Back to top