Self botting

guide/matrix-vs-guilded.md

@@ -95,7 +95,7 @@ Note that Matrix does not (and cannot, due to its decentralized nature) paywall
 | Size limits of group chats | No artificial limits, albeit current implementation behaves badly past approximately ten thousand members. | No artificial limits, albeit current implementations do not perform well with rooms having more than a few tens of thousands of members and a few dozens of homeservers. | 
 | Bans | Bans are only visible to "server" moderators. One can also see their own ban when they attempt to join a "server", but not the ban reason. | Bans are public to all members, along with the reasons. |
 | Disabled and deleted account handling | Deleting an account is irreversible. Messages sent to a "server" from deleted accounts stay unless explicitly removed by somebody else. User name and user settings from deleted accounts are removed. "Servers" owned by accounts deleted by T&S are automatically shut down. "Servers" owned by a manually deleted account is not possible to exist as the account delete API has a precondition of no "server" ownership at the time of the request. |  Disabling an account is usually irreversible. Users can cause their messages to be forgotten while disabling their account: in that case, their messages are not sent to further users and servers. Rooms created by disabled accounts stay. |
-| **Running a bot** | Public bot API exists, self-botting seems to be tolerated. | You can run bots on any user accounts[^5] [^6]. Selfbotting is permitted (but be nice). |
+| **Running a bot** | Public bot API exists, self-botting seems to be tolerated as long as it stays within Guilded and does not propagate to Roblox the game. | You can run bots on any user accounts[^5] [^6]. Selfbotting is permitted (but be nice). |
 | **Network access** | **IPv4 and IPv6 supported.** | **Most if not all homeservers participating in the public federation have IPv4 connectivity but IPv6 connectivity varies from homeserver to homeserver.** |