As we no longer have access to the message contents privileged intent (see #153, #146), we should instead provide pinning functionality via Application Commands. More specifically in this case we should use a message command, which allows users to initiate a Pin via a message's context menu.
We should also remove any functionality that is dependent on fetching the message contents via the API (e.g. the import command, and the trigger for importing pins when using native pins). This sadly significantly reduces Pinbot's functionality, however it allows it to continue existing at all without the privileged intent.
As a bonus, we should also consider how to inform users of this change, as the emoji react method will no longer function. The bot should now show other users the message is already pinned, and keep track of already pinned messages, by reacting to the message with the 📌 emoji
As we no longer have access to the message contents privileged intent (see #153, #146), we should instead provide pinning functionality via Application Commands. More specifically in this case we should use a message command, which allows users to initiate a Pin via a message's context menu.
We should also remove any functionality that is dependent on fetching the message contents via the API (e.g. the import command, and the trigger for importing pins when using native pins). This sadly significantly reduces Pinbot's functionality, however it allows it to continue existing at all without the privileged intent.
As a bonus, we should also consider how to inform users of this change, as the emoji react method will no longer function. The bot should now show other users the message is already pinned, and keep track of already pinned messages, by reacting to the message with the 📌 emoji
Related Issues
Requirements
Pinmessage command which replicates the existing pinning behaviourReplace with a reply notifying users of the change in behaviourimportcommandimportis triggeredAcceptance Criteria