TL;DR: Craig had issues connecting to twitch with a oauth token.

Tasks completed

  • Updated node to the latest LTS which is node 16 with nvm
  • Created an application on the Twitch developer console
  • Obtained a Twitch access token
  • Tried out Twitch chat bot API
  • Installed Hugo with brew
  • Tried out Hugo to start our dev journal using markdown

Details

Following along in the Twitch authentication, we should read the instructions. It clearly said to replace <OAUTH_TOKEN> using the string format is oauth:token where token is a user access token.

I got the token with:

https://id.twitch.tv/oauth2/authorize?response_type=token&client_id=<your client id>&redirect_uri=http://localhost:3000&scope=chat%3Aread+chat%3Aedit

It responded with a redirect url:

http://localhost:3000/#access_token=<access_token>&scope=chat%3Aread+chat%3Aedit&token_type=bearer

After Craig sent a message on Twitch with the “!hi” command, the “Twitch bot” responded with “You are drunk Craig, go to bed.” However, it sent it from Craig’s account. Lesson learned: don’t use your twitch account to make the bot. If you do, you are the bot.

What we saw

bedtimebear_808: !hi

bedtimebear_808: You are drunk Craig, go to bed.

bedtimebear_808: I am the bot.

Future work

  • Save Twitch chat code to a private repo on Github
  • Research what to save on GitHub for a Hugo site
  • Save Hugo site to a private repo on GitHub
  • Fix Hugo theming
  • Add a picture to the Hugo journal.
  • Research Hugo multiple directories: ‘posts’ and ‘journal’
  • Figure out where to stage Hugo site