decentral1se/blurp
1
0
Fork 0
Code Issues Pull Requests Activity

docs: links, wording, wrapping, new flags [ci skip]

Browse Source
This commit is contained in:
decentral1se 2024-08-04 10:38:47 +02:00
parent 53105cbf20
commit cd7487556e
Signed by: decentral1se
GPG Key ID: 03789458B3D0C410
1 changed files with 11 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -31,27 +31,30 @@ chmod +x blurp
* `blurp delete` will remove statuses but not media attachments *immediately* * `blurp delete` will remove statuses but not media attachments *immediately*
for **local media**. Remote media is removed immediately. Unattached local 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 * "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 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 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 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, 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 * "... 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 💝) 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 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. 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 * 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 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, be nice to run `blurp` at some "less busy" time period (but yanno, timezones,
so 🤷) and/or consider some form of rate limiting (**TODO**: so 🤷) and/or consider more strict rate limiting (`--rate/-r`).
[`#3`](https://git.coopcloud.tech/decentral1se/blurp/issues/3) 🙈)
## Delete stuff 🔥 ## Delete stuff 🔥
@ -61,7 +64,7 @@ You'll need to log in first:
blurp login -u foo@bar.zone 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 blurp archive