doryan
/
gluon
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
gluon/src/assets/unmute_command_help.html

8 lines
355 B
HTML
Raw Normal View History

assets: fix help messages (mute, unmute) There are quite some problems with the way commands are explained: * Interactivity - command arguments gets explained as if one is following a guide ("insert this, enter that"). Better explain them without any "guidance"; use present tense to describe commands. * Duplicity - the purpose of the command is explained over and over when arguments are being described. * Separation - there is no need to divide required and optional command arguments into their respective sections. Their amount did not grow up that much for this to make sense. * mute_command_help.html: i64 would be sufficient for developers, but not end users. It does not stop anyone from specifying overflowing integer, after all.
2024-06-07 01:50:05 +03:00
<code>/unmute [ID | UNMUTE]</code>
DELETED: useless function for HTML parsing
2024-06-05 13:13:24 +03:00
assets: fix help messages (mute, unmute) There are quite some problems with the way commands are explained: * Interactivity - command arguments gets explained as if one is following a guide ("insert this, enter that"). Better explain them without any "guidance"; use present tense to describe commands. * Duplicity - the purpose of the command is explained over and over when arguments are being described. * Separation - there is no need to divide required and optional command arguments into their respective sections. Their amount did not grow up that much for this to make sense. * mute_command_help.html: i64 would be sufficient for developers, but not end users. It does not stop anyone from specifying overflowing integer, after all.
2024-06-07 01:50:05 +03:00
<b>Снять мут с участника чата.</b>
DELETED: useless function for HTML parsing
2024-06-05 13:13:24 +03:00
assets: fix help messages (mute, unmute) There are quite some problems with the way commands are explained: * Interactivity - command arguments gets explained as if one is following a guide ("insert this, enter that"). Better explain them without any "guidance"; use present tense to describe commands. * Duplicity - the purpose of the command is explained over and over when arguments are being described. * Separation - there is no need to divide required and optional command arguments into their respective sections. Their amount did not grow up that much for this to make sense. * mute_command_help.html: i64 would be sufficient for developers, but not end users. It does not stop anyone from specifying overflowing integer, after all.
2024-06-07 01:50:05 +03:00
Использовать при ответе на сообщение или указать <code>ID</code> пользователя.
DELETED: useless function for HTML parsing
2024-06-05 13:13:24 +03:00
assets: fix help messages (mute, unmute) There are quite some problems with the way commands are explained: * Interactivity - command arguments gets explained as if one is following a guide ("insert this, enter that"). Better explain them without any "guidance"; use present tense to describe commands. * Duplicity - the purpose of the command is explained over and over when arguments are being described. * Separation - there is no need to divide required and optional command arguments into their respective sections. Their amount did not grow up that much for this to make sense. * mute_command_help.html: i64 would be sufficient for developers, but not end users. It does not stop anyone from specifying overflowing integer, after all.
2024-06-07 01:50:05 +03:00
Доступно для пользователей с административными привилегиями в чате.