4 ms·

As an aside, I’m very impressed by the comments widget that uses Github issues. I think I might adopt it for my blog. I never cared much for comment sections, b

As an aside, I’m very impressed by the comments widget that uses Github issues. I think I might adopt it for my blog. I never cared much for comment sections, but my blog is a Github repository anyways, so I might as well use it. Thanks!

modeless 4y ago
I just added Giscus to my site which is the same thing but using GitHub Discussions instead of Issues as the backend which makes more sense. It's almost perfect except for one almost deal breaker thing (which applies to both Giscus and utterance.es): to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. I expect that it really cuts down on the number of people willing to leave a comment. And I doubt it will be fixed because Github probably doesn't really care to support this use of their API.
- PcChip 4y ago
  Yeah I certainly wouldn't click agree on that
- Kaze404 4y ago
  That does sound like a scary prompt, but it might also work as a filter of sorts. I certainly don't care enough about comments that scaring someone away will be a concern, especially as they can always just e-mail me, so I get to pay extra attention when someone does go through it.
- codetrotter 4y ago
  > to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. I expect that it really cuts down on the number of people willing to leave a comment. Since it’s powered by GitHub discussions, and the discussion itself needs to be public, anyone wanting to comment but not wanting to authorise Giscus to act on their behalf could go to the discussion on GitHub and leave the comment there directly I assume
  - modeless 4y ago
    True, but not if they're the first comment because Giscus doesn't create the discussion until someone comments.
    - whatsdoom 4y ago
      As a hack you could make a comment yourself on all of your posts. You may even be able to remove the comment after the discussion was created...
- bmacho 4y ago
  > to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. What should the "act on your behalf" mean? Is it safe to provide my readers Giscus?

modeless 4y ago

I just added Giscus to my site which is the same thing but using GitHub Discussions instead of Issues as the backend which makes more sense. It's almost perfect except for one almost deal breaker thing (which applies to both Giscus and utterance.es): to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. I expect that it really cuts down on the number of people willing to leave a comment. And I doubt it will be fixed because Github probably doesn't really care to support this use of their API.

PcChip 4y ago
Yeah I certainly wouldn't click agree on that
Kaze404 4y ago
That does sound like a scary prompt, but it might also work as a filter of sorts. I certainly don't care enough about comments that scaring someone away will be a concern, especially as they can always just e-mail me, so I get to pay extra attention when someone does go through it.
codetrotter 4y ago
> to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. I expect that it really cuts down on the number of people willing to leave a comment. Since it’s powered by GitHub discussions, and the discussion itself needs to be public, anyone wanting to comment but not wanting to authorise Giscus to act on their behalf could go to the discussion on GitHub and leave the comment there directly I assume
- modeless 4y ago
  True, but not if they're the first comment because Giscus doesn't create the discussion until someone comments.
  - whatsdoom 4y ago
    As a hack you could make a comment yourself on all of your posts. You may even be able to remove the comment after the discussion was created...
bmacho 4y ago
> to comment you have to click through a very scary permissions dialog that claims it can "Act on your behalf" in your Github account, without any qualification. I'm pretty sure the permissions dialog is misleading, but it sucks. What should the "act on your behalf" mean? Is it safe to provide my readers Giscus?