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

docs: moar rewording [ci skip]

Browse Source
This commit is contained in:
decentral1se 2024-08-03 15:22:37 +02:00
parent 83ad92f88c
commit 7a47d741bb
Signed by: decentral1se
GPG Key ID: 03789458B3D0C410
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
README.md
View File

@ -29,15 +29,15 @@ chmod +x blurp
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.
> 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` 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 * "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` 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
@ -47,7 +47,7 @@ chmod +x blurp
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 some form of rate limiting (**TODO**:
[`#3`](https://git.coopcloud.tech/decentral1se/blurp/issues/3) 🙃) [`#3`](https://git.coopcloud.tech/decentral1se/blurp/issues/3) 🙈)
## Delete stuff 🔥 ## Delete stuff 🔥