Synopsis
The motivation for this addition is the problem of users changing the intended view of the shown command. When a user wants to show information about a word in chat, chances are they intend to show a particular definition, and other users interfering with that is predictably not very desired.
Approach
There are several approaches that could be taken to add this functionality, so I'll note some ideas of my own down for how it could work:
- One idea would to use a command parameter
lock that locks the view before it is even shown. It's safe to assume that this 'lock' ought to apply to everybody except the person running the command, since the command runner would need time to navigate to the right page they want to show.
- Another possibility is using a button 'Lock', which would lock the view on-demand. This approach is predictably quite shaky as it still permits some degree of interference from other users before the button is pressed to lock it.
- What if the view was always implicitly locked for other users, and instead of locking the view, we would instead rather think about unlocking the view?
Synopsis
The motivation for this addition is the problem of users changing the intended view of the shown command. When a user wants to show information about a word in chat, chances are they intend to show a particular definition, and other users interfering with that is predictably not very desired.
Approach
There are several approaches that could be taken to add this functionality, so I'll note some ideas of my own down for how it could work:
lockthat locks the view before it is even shown. It's safe to assume that this 'lock' ought to apply to everybody except the person running the command, since the command runner would need time to navigate to the right page they want to show.