You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 6, 2023. It is now read-only.
Assuming this isn't a priority, but I'm still using this gem and thought I'd share that token and secret are incorrect in the docs, and instead it should be access_token and access_token_secret
In a separate YAML config file. Create a file named botname.yaml – the botname part must match your bot’s username EXACTLY. Put the following contents, pasting the credential values that you just generated:
---
:consumer_secret: Consumer Secret (API Secret) GOES HERE
:consumer_key: Consumer Key (API Key) GOES HERE
:access_token: Access Token GOES HERE
:access_token_secret: Access Token Secret GOES HERE
```
The text was updated successfully, but these errors were encountered:
On Sat, May 21, 2022, 21:24 Ryan TG ***@***.***> wrote:
Assuming this isn't a priority, but I'm still using this gem and thought
I'd share that token and secret are incorrect in the docs
<http://muffinista.github.io/chatterbot/setup.html>, and instead it
should be access_token and access_token_secret
In a separate YAML config file. Create a file named botname.yaml – the botname part must match your bot’s username EXACTLY. Put the following contents, pasting the credential values that you just generated:
---
:consumer_secret: Consumer Secret (API Secret) GOES HERE
:consumer_key: Consumer Key (API Key) GOES HERE
:access_token: Access Token GOES HERE
:access_token_secret: Access Token Secret GOES HERE
```
—
Reply to this email directly, view it on GitHub
<#66>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMAFC2ZSZFHBVQRBRZTRTVLGZIDANCNFSM5WSZFTIQ>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
Assuming this isn't a priority, but I'm still using this gem and thought I'd share that
token
andsecret
are incorrect in the docs, and instead it should beaccess_token
andaccess_token_secret
The text was updated successfully, but these errors were encountered: