Permissions, scopes and intents

Three different switches decide what a bot does, and each is set by somebody different.

All three have to agree. A bot with the moderate scope can ban only where its role holds ban_members, above the member it bans. A bot whose role may send messages but whose tokens lack messages.write sends nothing.

Scopes

Set on the bot's Bot page in the portal. The server holds every action a bot sends to them before anything else runs: bot actions lists each action and the scopes that let a bot send it.

Permissions

illest.Permissions names ILLEST's own bits. Build invite links with it, or on the portal's Installation page, rather than with a number from elsewhere:

import illest
from illest import utils

perms = illest.Permissions(send_messages=True, manage_messages=True, ban_members=True)
link = utils.oauth_url(1234, permissions=perms)

The portal's Installation page builds the same link. The person adding the bot may untick any permission it asks for, and nobody can give a permission they do not hold themselves.

Some names have no bit of their own here, and read and write the bit that covers them, so code written against those names still runs:

Intents

The server pushes what the bot is a member of, without being asked, so an intent is a filter on the bot's side. An event whose intent is off is never handed to a handler, and a message whose intent is off is not even decrypted. An intent cannot grant anything: the library says at start, once, when an intent is on that none of the bot's scopes could feed.

import illest

intents = illest.Intents.default()
intents.typing = True
client = illest.Client(intents=intents)

Intents.default() is every intent but typing and presences. Intents.all() is every one; Intents.none() is none.

Finer-grained names set the intent they are a part of. ILLEST has one messages intent, and needs no privileged message_content: a bot in a conversation's group reads it whole, or not at all.