Isolation

Summary

Use /isolate to send a user to their own channel, where they can still receive messages from #general via. the bot. Any messages they send will be relayed to a verification channel where admins can allow or deny the message with the click of a button.

The bot supports using the GPT-3 AI to automatically allow or deny messages*. Admins can also block any isolated user from sending messages, to prevent spamming the verification channel.
If isolated users start spamming the verification channel, use /lockdown-isolated to mute all isolated members. Beware though to undo this an admin must unblock each, one by one.
To set which channel is used as the general channel (default #general), use /set-general <channel>.

If you have any questions or issues, please message me, I'm generally online daily and will try to help / resolve issues asap.

* currently uses my API key. If demand improves, a system may be set up for servers to use their own API key.
Note: if ai support is turned on, all messages from isolated users will be sent to GPT-3 for reviewal. There is no guarantee that this is 100% effective and it may produce false positives or false negatives. I give no warranty that this system will work and that they messages will be secure. In testing, it has worked very well, so it should be ok.

Commands

To setup the bot: /setup then /setup-role must be run when the bot is first added, to create the verification channel, isolation category, and isolated role.
Note: commands marked as administrator require the user to have the Administrator permission
The bot supports both discord slash commands, and the prefix iso
Key: [permission] - Permission required to use the command
/isolate <user> [timeout] - Isolate a user from the server
/unisolate <user> [timeout] - Remove a user from isolation
/block-isolated <user> [timeout] - Block a user from sending messages in their isolated channel
/unblock-isolated <user> [timeout] - Unblock a user from sending messages in their isolated channel
/lockdown-isolated [administrator] - Block all isolated users from sending messages. Caution: to undo this, you must manually unblock each isolated user
/enable-ai [administrator] - Enable AI for this server
/disable-ai [administrator] - Disable AI for this server
/set-general <channel> [administrator] - Set the general channel used by the bot for this server (default #general)
/ping - Get the bot’s latency
/info - Get info about the bot
/help - Show commands reference

Donate!

If you want to help pay the server fees, top.gg advertising fees, and support me with my development, please donate at Stripe! It helps a lot and will be very encouraging :)
If you don't have the money to donate, please rate / upvote the bot to help people find the bot.

Bugs

As with any program and bot, Isolation will have it's issues from time to time. Please report any glitches, unexpected downtime, issues, etc. to me (preferably via discord DM or in the lonely server below), and I'll try and sort them asap at the next available opportunity (I'm a busy person). Thanks for helping keep the bot bug-free.
If you receive a message from the bot that breaks the discord community guidelines, doxxes me or someone else, advertises something, or worse, my bot's token or openai token may have been leaked (very unlikely because it's nice and secure). If this happens, contact me asap through all means of communication and I'll reset my bot token. Check first that it's actually the bot sending it, not someone's message through the bot (which is a feature; it's literally the point of the bot).

Privacy

If /enable-ai or /set-general is run, the ID of your server will be stored in a file on the bot’s server. This will (unless in the case of an error) be deleted if you run /disable-ai.
Apart from that collected by GPT-3 when AI is turned on, I do not knowingly store any other personal information or infomation in your server.

Troubleshooting

Some aspects of my bot haven't been completely fool-proofed. If the bot is being pesky or something is odd, follow these steps:

1. Check the bot is online and responding with iso ping.
2. If you are running a command that requires admin privileges, make sure you have the Administrator permission in the server (not just a role called 'admin').
3. Check the bot has all the required permissions and it hasn't been restricted.
4. Make sure /setup and /setup-role have been run (if you add a new channel, isolated users will have access to it until you re-run /setup-role). /setup-role will take a while if you have a lot of channels.
5. Check that the bot is using your general channel (it will use #general, but if you rename the channel or want to use it in a different channel, you will need to use /set-general <channel>.
6. If there's an issue with a / command, try using the iso prefix
7. If the bot doesn't respond, try running the command again, it might just be a temporary glitch in the fabric of reality.
8. If there are any syntax errors or other exceptions that aren't fixed by running the command again, please report them to me if the above steps are not solving the issue!