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
Hey, first off thanks for the work on this neat script, it's an interesting way to do things and has enabled more collaboration between members. We are trying to use this script with Slack, and the hubot-slack adapter.
There is an issue in the 'my public key' method, where it will only respond to the user.id, not name. Therefore, it will only respond natively if you use the ID as your identifier. On Slack at least, this is not the case, and a username is used instead. It is required to change the script to respond with the name associated to an ID. Calling 'hubot what is public key' works as expected.
Additionally, the version defined as 'latest' in NPM is different to the version that is live here.
Furthermore, there is a current issue affecting the storage of the keys, and for some reason it users the ID explicitly. To get around this, we downgraded the slack adapter for now.
The text was updated successfully, but these errors were encountered:
triwats
pushed a commit
to triwats/hubot-keys
that referenced
this issue
Nov 14, 2016
Hey, first off thanks for the work on this neat script, it's an interesting way to do things and has enabled more collaboration between members. We are trying to use this script with Slack, and the hubot-slack adapter.
There is an issue in the 'my public key' method, where it will only respond to the user.id, not name. Therefore, it will only respond natively if you use the ID as your identifier. On Slack at least, this is not the case, and a username is used instead. It is required to change the script to respond with the name associated to an ID. Calling 'hubot what is public key' works as expected.
Additionally, the version defined as 'latest' in NPM is different to the version that is live here.
Furthermore, there is a current issue affecting the storage of the keys, and for some reason it users the ID explicitly. To get around this, we downgraded the slack adapter for now.
The text was updated successfully, but these errors were encountered: