Skip to content

Instantly share code, notes, and snippets.

View voiding's full-sized avatar

Ryan voiding

  • 11:13 (UTC +08:00)
View GitHub Profile

Keybase proof

I hereby claim:

  • I am voiduwu on github.
  • I am voiddd (https://keybase.io/voiddd) on keybase.
  • I have a public key whose fingerprint is BD25 99C3 9F10 33CA 619A A757 34D1 03DA B00F B256

To claim this, I am signing this object:

Keybase proof

I hereby claim:

  • I am missingbinaries on github.
  • I am voiddd (https://keybase.io/voiddd) on keybase.
  • I have a public key ASBIoMJhrg7pz9qtMQaOqr_RPdXqPjIIh3UV1KWS9MuIWgo

To claim this, I am signing this object:

@voiding
voiding / how_to_use_a_gitignore_for_protecting_bot_tokens.md
Last active June 21, 2024 16:07
Some people just don't know how to keep their bot's token private, smh people. Here's a guide that'll hopefully help.

Okay so you've probably considered making your bot open-source and that's fine but there's one thing EVERYONE should note before pushing their current progress to GitHub:

HIDE YOUR TOKENS. THESE ARE A KEY TO LOGGING IN AND INTERACTING WITH THE DISCORD API. DON'T GIVE IT TO ANYONE YOU DON'T TRUST, LET ALONE GITHUB.

  1. Create a config file (JSON is frequently used for bot configs, YAML also works) in the root (root meaning the base of the folder) of your bot folder.
    I'll use JSON to demonstrate: