aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--README.txt7
-rw-r--r--articles/published/9999-v5-release.html2
-rwxr-xr-xsupport/bot_up2
3 files changed, 8 insertions, 3 deletions
diff --git a/README.txt b/README.txt
index 208851a..b31eed3 100644
--- a/README.txt
+++ b/README.txt
@@ -1 +1,6 @@
1The CGI source and content for libot.eu.org. Assumes you're using systemd-networkd and a virtual ethernet adapter for LiBot (I use systemd-machined for that but you can probably use others). Include nginx.conf in your setup and make sure to set $network_interface (to the virtual ethernet adapter's name in networkd) and $network_host (to LiBot's IP) to set up. 1The CGI source and content for libot.eu.org. Assumes you're using
2systemd-networkd and a virtual ethernet adapter for LiBot (I use
3systemd-machined for that but you can probably use others). Include
4nginx.conf in your setup and make sure to set $network_interface (to
5the virtual ethernet adapter's name in networkd) and $network_host
6(to LiBot's IP) to set up.
diff --git a/articles/published/9999-v5-release.html b/articles/published/9999-v5-release.html
index f962015..7345f68 100644
--- a/articles/published/9999-v5-release.html
+++ b/articles/published/9999-v5-release.html
@@ -23,7 +23,7 @@
23 Unfortunately, this also comes at a cost - since the legacy LiBot instance is already present in more than 100 guilds, I will not be able to add it to the system without first removing the excess (600 or so) guilds. This will be necessary after August 31, 2022, as this is the deadline for the message content intent. This effectively means that discord will no longer supply LiBot with the content of sent messages, which is required for commands to work. An alternative to that would be migrating to discord's "slash commands", but I have reservations about doing that (primarily the poor state of the slash commands UI in the client, and that it would not address the verification issue). 23 Unfortunately, this also comes at a cost - since the legacy LiBot instance is already present in more than 100 guilds, I will not be able to add it to the system without first removing the excess (600 or so) guilds. This will be necessary after August 31, 2022, as this is the deadline for the message content intent. This effectively means that discord will no longer supply LiBot with the content of sent messages, which is required for commands to work. An alternative to that would be migrating to discord's "slash commands", but I have reservations about doing that (primarily the poor state of the slash commands UI in the client, and that it would not address the verification issue).
24 </p> 24 </p>
25 <p> 25 <p>
26 <b>This means you will be required to readd LiBot to your guild!</b> Fortunately, doing so is easy (as long as you have the 'Manage Server' permission. All you have to do is click <a href='/get'>here</a>, and follow the authorization prompt's instructions. 26 <b>This means you will be required to <a href='/get'>readd LiBot to your guild</a>!</b> Fortunately, doing so is easy (as long as you have the 'Manage Server' permission. All you have to do is click the link, and follow the authorization prompt's instructions.
27 </p> 27 </p>
28 <p> 28 <p>
29 An unintended side-effect of shredding is a much faster start-up time for LiBot. Discord limits the number of guilds that can be loaded to about 100 per minute, and because I load all of them on startup, it ended up taking some 7 minutes to load all of them. As all shreds are limited to 100 guilds, they never hit the ratelimit, and load all of the guilds instantly. 29 An unintended side-effect of shredding is a much faster start-up time for LiBot. Discord limits the number of guilds that can be loaded to about 100 per minute, and because I load all of them on startup, it ended up taking some 7 minutes to load all of them. As all shreds are limited to 100 guilds, they never hit the ratelimit, and load all of the guilds instantly.
diff --git a/support/bot_up b/support/bot_up
index 2cac615..91b791e 100755
--- a/support/bot_up
+++ b/support/bot_up
@@ -1,2 +1,2 @@
1#!/bin/bash 1#!/bin/bash
2networkctl list --no-pager --no-legend "$NETWORK_INTERFACE" > '/dev/null' 2>&1; \ No newline at end of file 2networkctl list --no-pager --no-legend "$NETWORK_INTERFACE" > '/dev/null' 2>&1;