From d027d329fbc757865b112d0ca819c417dfa6ef03 Mon Sep 17 00:00:00 2001 From: decentral1se Date: Sat, 3 Aug 2024 15:19:23 +0200 Subject: [PATCH] docs: moar yellow [ci skip] --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b2f3964..6b2d1d7 100644 --- a/README.md +++ b/README.md @@ -17,11 +17,11 @@ chmod +x blurp ## Field notes on how deletion works in GoToSocial -> ⚠️ How this exactly works seems to depend both on a shifting development sands +> 🟡 How this exactly works seems to depend both on a shifting development sands > of GtS (**ALPHA SOFTWARE** etc.) but also how other Fediverse softwares deal > with deletion (e.g. [Mastodon](https://oisaur.com/@renchap/112882201793431045), > also shifting sands). This is a best-effort explanation and might quickly be -> out of date. Help welcome! ⚠️ +> out of date. Help welcome! 🟡 * `blurp delete` will get you rate limited by your own instance. I temporarily solved this by [turning off rate limiting](https://docs.gotosocial.org/en/latest/api/ratelimiting/#can-i-configure-the-rate-limit-can-i-just-turn-it-off), running the command and then turning rate limiting back on again. I could probably implement some backoff in the code but this is just easier.