Remove tea-cleanerHEADmaster

Since I do not use gitea anymore and cannot maintain the compatibility
with the new versions.

1 files changed, 0 insertions, 37 deletions

diff --git a/README.md b/README.md
index 5a86041..aeba803 100644
--- a/README.md
+++ b/README.md
@@ -13,7 +13,6 @@ The repository contains a collection of random scripts and short programs.
 3. [rename.rb](#renamerb)
 4. [pg\_jekyll.rb](#pg_jekyllrb)
 5. [locopy](#locopy)
-6. [tea-cleaner](#tea-cleaner)
 
 ## 7digital
 
@@ -60,39 +59,3 @@ it should be able to find. Invokation example:
 ```sh
 locopy wordpress --root /path/to/wordpress --siteurl "http://localhost:8083"
 ```
-
-## tea-cleaner
-
-`tea-cleaner` tries to detect spam accounts on a gitea instance and can remove
-them automatically.
-
-### Run instructions
-
-See `tea-cleaner.toml.dist` for a description of the available configuration.
-Copy this file to `config/tea-cleaner.toml` and change at least `token` and
-`server` values. After that if you just run `tea-cleaner` it will give a list
-of user accounts which look suspicious to it. Rerunning the command with the
-`--live` flag will purge the listed accounts and all their activities, assuming
-the given token has amdinistrative access to the Gitea instance.
-
-Run `tea-cleanr --help` to see all available command line options. 
-
-### Applied rules
-
-Critical:
-
-- The account is elder than a month and the user hasn't logged in since then.
-- User information contains banned words (can be adjusted in the configuration file).
-- User's homepage contains percent encoded symbols.
-
-Possible:
-
-- User filled fields for personal information: description and website.
-- The mail address domain is unusual (can be adjusted in the configuration file).
-
-The accounts that violate one of the critical rules are marked for removal
-right away. Other checks trigger an additional lookup for the last user
-activities. If everything user did was creating an empty repository, these
-accounts are marked for removal as well.
-
-The rules are based on my invastigation of spam accounts on this instance.