Update README.md

README.md

@@ -1,4 +1,4 @@
-# ai621 (A1111 webui fork)
+# ai621111 (A1111 webui fork)
 
 This is fork of ai621 (https://git.foxo.me/AI621/ai621) bot that contains some additional features/fixes.
 
@@ -17,21 +17,4 @@ This is only the "bot" part. The actual generation is done by AUTOMATIC1111 Stab
 - Copy example database and rename it to `ai621.db`.
 - Run the bot with `python3 bot.py`
 
-## User data
-
-Data is stored inside "ai621.db": three tables (user, prompt and pending_prompt) define all the data. Additionally, uploaded images (for the img2img mode) are stored inside the "userdata/" folder which is inside of the work folder.
-
-## Can you define multiple video cards / nodes to speed generation up?
-
-No. Or at least, not anymore. You will notice from the example configuration that three nodes were defined. This was working properly, until i accidentally overwrote the files that were responsible for that with an older version that didn't have that function anymore. I didn't bother.
-
-## What are the log and raw channels?
-
-ai621 posts all generated images to a channel called "ai621 raw", and then forwards them to the user at the end of the prompt processing. This is so that everybody can see and get inspired by other prompts. This is what the raw channel is.
-The log channel, instead, is where all prompts and stored along with buttons to be able to moderate users (delete prompts and ban users).
-
-## What are "cycles"?
-
-Every day each user has a defined number of cycles, also known as "steps". Since steps can be defined in a sorta stable amount of time, this is used to make sure that all users can fairly use the bot.
-
-Some specific prompts also ramp up the amount of cycles used as a "penalty", like using blacklisted tags or bad quality prompts.
+Additional info about the bot can be found in the upstream repo (https://git.foxo.me/AI621/ai621).