Inspect the cache
.s (aliases .snipe and .c) shows deleted messages and accepts page, channel, and member filters. .rsnipe lists recent reactions; /s and /reactions are also available. These views expose up to 25 cached items. .snipe and .c alias .s; .reactionsnipe and .reactions are prefix aliases for .rsnipe. /s accepts channel/user filters and a page from 1 to 25; /reactions accepts amount from 1 to 25 (default 1) and pages through reactions without channel or member filters.
Headless-generated labels appear in English; names and recovered content are not translated.
Deleted messages
.s
.s #general @member 2
/s
.snipe and .c aliases also work.
Recent reactions
.rsnipe
.reactionsnipe · .reactions
/reactions
Clear the cache
.cs
/cs
.clearsnipe alias also works; use .cs full to clear the recent-message cache as well.
Permissions
For.s, .rsnipe, /s, and /reactions, the runtime accepts Administrator, Manage Messages, or Moderate Members. Prefix .cs requires Manage Messages; /cs accepts Manage Messages or Administrator. .cs clears deleted-message and reaction histories; full also removes the recent-message cache.
Retention
Deleted-message and reaction histories are in-memory caches bounded to 100 events each per server; views show up to 25. The recent-message cache holds up to 20,000 messages per server and expires after seven days. None of this is permanent storage or a substitute for Logs as durable evidence. Restarting or clearing/expiring a cache makes those items unavailable.Steps
1
Use narrow filters
Use channel/member filters only with
.s or /s; .rsnipe and /reactions page through reactions without channel or member filters.2
Minimize exposure
Do not repost recovered content where it should not be visible.
3
Clear deliberately
Before
.cs full, confirm the server accepts losing the recent-message cache.