MSC4295: Rephrase Background with a clearer description of "amphibious bots"

Signed-off-by: Star Brilliant <coder@poorlab.com>

Author: m13253

proposals/4295-bot-bounce-limit.md

@@ -12,7 +12,7 @@ Here are some examples of bot-to-bot interactions and their needs for loop preve
 4. In a high-volume room, a summary bot may provide daily recaps for people to catch up with discussions they missed. Such a bot consumes outputs of other bots, but does not want to trigger other bots.
 5. The room operator runs a "UTD notification bot" that notifies room members that their messages can't be decrypted by others. However, it is very important to prevent it from replying to another bot's message.
 6. When bridging rooms across three or more platforms (e.g., Matrix ⇌ Telegram ⇌ IRC ⇌ Matrix), it is necessary to make sure each bridge doesn't pick up another bridge's messages.
-7. If the same bot provides native versions for multiple platforms, the room operator may want to let the bot itself provide native experiences on different platforms (e.g., `!bot help` on Matrix and IRC, `/help@bot` on Telegram, `/help` on Discord, etc.). This bot needs to bridge its outputs by itself to make command palettes work, thus it needs to inform any existing bridges to ignore its output to prevent double bridging.
+7. An "amphibious" bot operates separate instances on each platform of a bridged room, utilizing platform-native command palettes (e.g., `!bot help` on Matrix and IRC, `/help@bot` on Telegram, `/help` on Discord, etc.), but sharing internal state and chat logs across platforms. This bot needs to inform any existing bridges to ignore its output to prevent double bridging.
 
 Currently, it is usually a room operator's responsibility to prevent bot loops, for example, by carefully configuring each bot's ignore list, ensuring all possible outputs of one bot don't contain trigger words of another bot, and removing unauthorized bots invited by some random member. Nonetheless, a well-maintained configuration can be very fragile, and the room operator may not be able to monitor the room at all times.