New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Switching to Utterances Comments | Aaron Meurer's Blog #18
Comments
To comment on this post, click on "Sign in with GitHub" below. If you don't want to authorize the Utterances bot, you can go to the GitHub issues page for this post and comment there. |
utter brilliance
|
It requires a permission "Act on your behalf". What does that mean exactly? The good news is that one can also just comment on github directly. I like that idea a lot. |
or by email ?
…On Thu, Jun 3, 2021 at 2:03 PM Ondřej Čertík wrote:
It requires a permission "Act on your behalf". What does that mean exactly?
|
Yeah, it needs permissions to be able to comment on the issue from my site. If you look at my comment on the GitHub issue page for this post, you'll see it says "@asmeurer with utterances". That means that my comment was actually posted using the GitHub API by the utterances app. Basically, when you type text into the comment box on my site, the Javascript on the site sends that text to the utterances app, which you have authorized with on GitHub, and it uses that authorization to post a comment as you on the issue. But it's only if you want to convenience of typing the comment on my site. You can also just comment directly on the issue, and it will still show up as a comment on the post. You can also edit your comment on the issue, and it will be updated on the post. |
My main concern is: what else can it do on my behalf if it gets hacked? |
Yeah, I actually don't know what "act on your behalf" means. GitHub is very unclear about that. Maybe @jdanyow, who created Utterances, can comment. |
That looks painless. |
Switching to Utterances Comments | Aaron Meurer's Blog
https://asmeurer.com/blog/posts/switching-to-utterances-comments/
The text was updated successfully, but these errors were encountered: