docs: links, wording, wrapping, new flags [ci skip]
This commit is contained in:
parent
53105cbf20
commit
cd7487556e
19
README.md
19
README.md
@ -31,27 +31,30 @@ chmod +x blurp
|
||||
|
||||
* `blurp delete` will remove statuses but not media attachments *immediately*
|
||||
for **local media**. Remote media is removed immediately. Unattached local
|
||||
media is removed the next time the media cleaning job runs.
|
||||
media is removed the next time the media cleaning job runs. See the [media
|
||||
caching docs](https://docs.gotosocial.org/en/latest/admin/media_caching/) for
|
||||
more.
|
||||
|
||||
* "If your post gets boosted or otherwise transmitted to a server yours doesn't
|
||||
know about and then you delete, you'll only send deletes to servers yours
|
||||
knows about, so copies of your post will remain on those other third party
|
||||
servers. so you can't rely on a delete reaching everywhere your post has gone
|
||||
even if you assume that servers will honour delete requests. but nonetheless,
|
||||
a best effort to remote delete will happen" - `sentynel` (`GoToSocial Help` chat 💝)
|
||||
a best effort to remote delete will happen" - `sentynel` (`GoToSocial Help`
|
||||
chat 💝)
|
||||
|
||||
* "And more servers should do what we do, which is when we attempt to refresh a
|
||||
status but found out it has been deleted we remove it" - `kim` (`GoToSocial Help` chat 💝)
|
||||
* "... more servers should do what we do, which is when we attempt to refresh a
|
||||
status but found out it has been deleted we remove it" - `kim` (`GoToSocial
|
||||
Help` chat 💝)
|
||||
|
||||
* There is (afaict) an ongoing plan to implement "status tombstones" in GtS so
|
||||
* There is (AFAICT) an ongoing plan to implement "status tombstones" in GtS so
|
||||
that when a deleted status is requested, it will return `410 gone` and then
|
||||
the requester will know it is time to delete any local copies.
|
||||
|
||||
* Be aware, "delete requests" will be sent to followers when you delete your
|
||||
statuses. This means you can end up spamming your fellow fedizens. It might
|
||||
be nice to run `blurp` at some "less busy" time period (but yanno, timezones,
|
||||
so 🤷) and/or consider some form of rate limiting (**TODO**:
|
||||
[`#3`](https://git.coopcloud.tech/decentral1se/blurp/issues/3) 🙈)
|
||||
so 🤷) and/or consider more strict rate limiting (`--rate/-r`).
|
||||
|
||||
## Delete stuff 🔥
|
||||
|
||||
@ -61,7 +64,7 @@ You'll need to log in first:
|
||||
blurp login -u foo@bar.zone
|
||||
```
|
||||
|
||||
You might want to archive stuff locally before deleting *all the things*:
|
||||
You might want to archive stuff locally:
|
||||
|
||||
```
|
||||
blurp archive
|
||||
|
Loading…
x
Reference in New Issue
Block a user