PUBLIC-INBOX-PURGE(1)
π public-inbox-purge β bestie's guide to yeeting messages out of history π
okay so this is the public-inbox-purge page from the public-inbox user manual, and bestie, we're gonna talk about it. buckle up π
β¨ NAME β¨
public-inbox-purge β erase messages from a public inbox and its history ποΈπ
πΈ SYNOPSIS πΈ
# requires ~/.public-inbox/config
public-inbox-purge --all </path/to/message-to-purge
# for testing with unconfigured inboxes:
public-inbox-purge $INBOX_DIR </path/to/message-to-purge
like, you feed it the message you want gone on stdin, and it goes poof. no cap. β¨
π¦ DESCRIPTION π¦
So public-inbox-purge lets you remove entire messages in a given inbox from history. the way that it β¨deletesβ¨.
But ngl, it is only intended as a last resort π because it will cause discontiguous git history and it will draw more attention to the sensitive data in mirrors. it's giving "the opposite of subtle." π
If you're just trying to get rid of spam, public-inbox-learn(1) is preferable, because it preserves contiguous git history. much cleaner vibe π§
If you want to edit sensitive info out of messages instead, consider public-inbox-edit(1) instead β but keep in mind it still leads to discontiguous git history. yeah. π
π OPTIONS π
--allβ purge the message in all inboxes configured in~/.public-inbox/config. this is an alternative to specifying individual inboxes directories on the command-line. one flag, every inbox, slay π
π ENVIRONMENT π
PI_CONFIGβ the default config file, normally"~/.public-inbox/config". seepublic-inbox-config(5). iykyk π
β οΈ LIMITATIONS β οΈ
okay this is the important part, bestie, read it fr fr:
- Only
public-inbox-v2-format(5)inboxes are supported. π«Ά - This is safe to run while normal inbox writing tools (
public-inbox-mda(1),public-inbox-watch(1),public-inbox-learn(1)) are active. β¨
π¨ Running this in parallel withpublic-inbox-xcpdb(1)or"public-inbox-index --reindex"can lead to errors or purged data remaining indexed. do not do this. seriously. π
- Incremental
public-inbox-index(1)(without"--reindex") is fine. π - Keep in mind this is a last resort, because it will be disruptive to anyone using
git(1)to mirror the inbox being purged. main character energy, but for chaos. π
π¬ CONTACT π¬
Feedback welcome via plain-text mail to <mailto:meta@public-inbox.org> π
The mail archives are hosted at <https://public-inbox.org/meta/> and <http://4uok3hntl7oi7b4uf4rtfwefqeexfzil2w6kgk2jn5z2f764irre7byd.onion/meta/> π
Β©οΈ COPYRIGHT Β©οΈ
Copyright 2019-2021 all contributors <mailto:meta@public-inbox.org> π
License: AGPL-3.0+ <https://www.gnu.org/licenses/agpl-3.0.txt> π
π SEE ALSO π
public-inbox-edit(1), public-inbox-learn(1)
and that's the whole page, bestie!! π this came out of the public-inbox.git tree, dated 1993-10-02 (yes really, iconic date, don't ask π), and it's page PUBLIC-INBOX-PURGE(1) of the public-inbox user manual. go forth and purge responsibly, and remember: last resort means LAST resort π β¨π¦πΈ
π¦ where this page comes from
- fedora 43: public-inbox 2.0.0~20230714git590023f-6.fc43 Β· AGPL-3.0-or-later
- fedora 44: public-inbox 2.0.0~20230714git590023f-6.fc43 Β· AGPL-3.0-or-later
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms