This docs describes the method to puppet yourself with the bridge, so you can interact with the bridge as if you were using the real Discord client. This has the benefits of (not all of these may be implemented):
- Talking as yourself, rather than as the bot.
- DM channels
- Able to use your Discord permissions, as well as joining rooms limited to your roles as on Discord.
Discord is currently not offering any way to authenticate on behalf of a user and interact on their behalf. The OAuth system does not allow remote access beyond reading information about the users. While developers have expressed a wish for this, it is my opinion that Discord are unlikely to support this any time soon. With all this said, Discord will not be banning users or the bridge itself for acting on the behalf of the user.
Therefore while I loathe to do it, we have to store login tokens for full permissions on the user's account (excluding things such as changing passwords and e-mail which require re-authenication, thankfully).
The tokens will be stored by the bridge and are valid until the user changes their password, so please be careful not to give the token to anything that you wouldn't trust with your password.
I accept no responsibility if Discord ban your IP, Account or even your details on their system. They have never given official support on custom clients (and by extension, puppeting bridges). If you are in any doubt, stick to the bot which is within the rules.
2FA does not work with bridging, please do not try it.
You should be able to puppet with 2FA enabled on your account
You must also be a bridge admin to add or remove puppets at the moment
- Follow https://discordhelp.net/discord-token to find your discord token.
- Stop the bridge, if it is running.
- Run
npm run usertool -- --addand follow the instructions. - If all is well, you can start the bridge.