Saving to the Wiki

The pushpin reaction is the main way content gets into MemoryCord. React with it, and a message becomes a searchable wiki entry. This page covers exactly how that works, including the rules that keep it from being abused or cluttered.

Where it works

The pushpin only does anything in channels an admin has opted in with /optin. In any other channel, reacting with a pushpin does nothing at all - the bot behaves as if it isn’t there. See Getting Started for how to opt a channel in.

It works inside threads and forum posts too, as long as the thread’s parent channel is opted in. A thread does not need to be opted in separately - it inherits its parent’s status automatically. The one exception is private threads: messages in a private thread are never captured, under any circumstance, because their content isn’t visible to the server at large.

The self-flag rule

Regular members cannot flag their own messages. If you react with the pushpin on something you wrote yourself, nothing happens - not an error, just silence.

Admins with the Manage Server permission are exempt from this and can flag their own messages. This exists so an admin seeding the wiki with a known-good message they wrote (a pinned announcement, a canonical answer) doesn’t need to get someone else to flag it for them.

What gets skipped

A pushpin reaction is silently ignored (no error, no reply) when:

• The channel isn’t opted in.
• The reactor is flagging their own message and isn’t an admin.
• The message author is a bot.
• The message has no usable content - see the next section for what counts as usable.
• The per-user flag rate limit has been hit (see below).
• The bot can no longer see the channel or fetch the message (it was deleted between the reaction and the fetch, or the bot lost access).

Text and attachment-only messages

If a message has text, that text is stored, up to 4,000 characters (longer messages are truncated).

If a message has no text but does have attachments - an image or file posted with no caption - MemoryCord stores a placeholder like [attachments] screenshot.png, notes.pdf instead of leaving the entry blank. This only applies to the pushpin reaction path; the attachment names are searchable, though the attachment itself is never stored or re-hosted by the bot.

A message with neither text nor attachments (which practically never happens, but could in principle) has nothing to save and is skipped.

How reaction counts work

The reaction count on a wiki entry is read directly from the message’s live pushpin count at the moment it’s captured or updated - it is never incremented by the bot itself. Practically, this means:

• If a message already has three pushpin reactions and a fourth person adds one, the stored count updates to reflect the current total, not “previous count plus one.”
• Removing a pushpin reaction re-syncs the stored count down to match.
• Re-flagging a message that’s already saved (someone else pins it again after a removal, for example) refreshes its content and reaction count, but does not create a second entry and does not change who is recorded as the original flagger.

Rate limit

Flagging is rate-limited per person, per server, to keep reaction spam from flooding the wiki. The default is 10 flags per 10 minutes. If you hit the limit, further pushpin reactions are silently ignored until the window rolls forward - there’s no error message, since a reaction can’t carry a reply the way a slash command can.

/wiki save: the explicit alternative

If a message you want to save doesn’t have a pushpin on it yet - or you’d rather not react to it - use:

/wiki save message_link:https://discord.com/channels/123.../456.../789...

Right-click any message and choose Copy Message Link to get the link. A few differences from the pushpin path are worth knowing:

• /wiki save requires actual text content. Unlike the pushpin reaction, it does not fall back to an attachment-name placeholder - an image-only message with no caption will be rejected with “That message has no text content to save.”
• The link must point to a message in the same server, in a channel you can see, that’s already opted in.
• Bot messages are rejected.
• Messages in private threads can’t be saved this way either.
• It has a five-second per-person cooldown, same as /ask and /wiki search.

Deleting an entry

/wiki delete message_link:https://discord.com/channels/123.../456.../789...

Right-click the saved message and choose Copy Message Link, same as /wiki save. Deletion is allowed for three people: whoever flagged or saved the entry, the original message’s author, and any admin (Manage Server). Anyone else gets a permission error. If the link doesn’t resolve to a saved entry - because nothing was ever saved for that message, or because you can’t see the channel it’s in - you get the same “No saved entry found for that message” reply either way, so the command never confirms that hidden content exists. This only removes wiki entries (pushpin//wiki save/import captures) - it does not remove Q&A pairs created by /solve; those are covered in Questions and Answers.

If you’d rather remove everything you’re associated with in a server at once, see /forgetme in Privacy.

When the original message is deleted

If the source Discord message is later deleted - by the author, a moderator, or auto-moderation - its wiki copy is automatically deleted too. There’s no separate cleanup step needed and no way to keep a wiki entry alive after its source message is gone. This does not apply to Q&A pairs from /solve, which are stored independently once created; see the caveat in Privacy.