You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some commands should be always visible, and some commands should always be hidden, however, we should give the user the option to make their command usage private or public, without having to move to DMs.
There is no harm in commands being nonephemeral, for the most part, but it would be good if you didn't have to announce to the entirety of UQCS when you're getting pizza.
Below are some thoughts on what commands should be always visible, visible with the option to hide it, or hidden with the option to show it.
Command
Hidden
bgg
Default visible
binify, caesar, hexify, morse
Default hidden
cat
Always visible
coin
Default visible
conduct
Default visible
courseecp
Default hidden
cowsay, cowthink
Always visible
dominoscoupons
Default visible
events, allevents
Default visible
hackathon
Default visible
httpcat
Always visible
hoogle
Default hidden
latex
Default visible
membercount
Default hidden
mock
Default visible
pastexams
Default hidden
remindme
Always hidden
repo
Default visible
scare
Default visible
scry
Default visible
smoko
Always visible
snailrace
Always visible
syllables
Default hidden
uptime
Default visible
votey
Always visible
whatsdue
Default hidden
whatweekisit
Default visible
xkcd
Always visible
xsampa
Default hidden
zalgo
Always visible
Ephemeral commands can be implemented for commands that need to defer using await interaction.response.defer(ephemeral=True).
The text was updated successfully, but these errors were encountered:
I'll ask what the rest of infra thinks about it, but it feels a bit like pointless effort when DMs exist - if you're interacting with the bot in the server, the default presumption should be that you're interacting publicly.
I'm not fantastically interested in us breaking that default, for any command, because (yeah yeah slippery slope fallacy whatever) I feel like we shouldn't even pretend we'll maintain that guarantee. For example, remindmeisn't private, no matter whether you DM or not, because they go to the same DB and the debug commands will display your reminder no matter what. I don't think we should then enable people to mistakenly pretend it is private by hiding the message by default.
imo, I think almost all bot commands should remain default visible as is and if you really don't want them public, to consider dm'ing the bot. Mostly as commands like hooglecourseecp and pastexams for example, can add to the existing conversation about what is going on.
As a public server I don't necessarily want to hide cool interactions with the bot, as it encourages discussions around improving the bot. We also embrace the chaos of "testing in prod" on occasion, and it's kinda funny when things break in a spectacular fashion.
My exception to the rule here are commands that are tied to you in some way. iirc currently only mcwhitelist, as you may not want to broadcast your Minecraft username to the entire server.
Some commands should be always visible, and some commands should always be hidden, however, we should give the user the option to make their command usage private or public, without having to move to DMs.
There is no harm in commands being nonephemeral, for the most part, but it would be good if you didn't have to announce to the entirety of UQCS when you're getting pizza.
Below are some thoughts on what commands should be always visible, visible with the option to hide it, or hidden with the option to show it.
Ephemeral commands can be implemented for commands that need to defer using
await interaction.response.defer(ephemeral=True)
.The text was updated successfully, but these errors were encountered: