Skip to content
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

Comments: Replacing Disqus with Github Comments #1

Open
dwilliamson opened this issue Apr 18, 2017 · 226 comments
Open

Comments: Replacing Disqus with Github Comments #1

dwilliamson opened this issue Apr 18, 2017 · 226 comments

Comments

@dwilliamson
Copy link
Owner

dwilliamson commented Apr 18, 2017

Comments for Replacing Disqus with Github Comments

@dwilliamson
Copy link
Owner Author

This is a comment

@dwilliamson
Copy link
Owner Author

This is another comment

@dwilliamson
Copy link
Owner Author

dwilliamson commented Apr 18, 2017

This is a comment with some markdown...

  • Listy
  • Listo
  1. Jumble
  2. Sale

Boldit or Italicit or strikeit

header

hashtag

something something

int x = 3;

@jasminpatry
Copy link

This is great. Thanks for sharing this!

@olafleur
Copy link

Awesome ! I think I will try this on my website. :)

@vielmetti
Copy link

Nicely done.

@vyp
Copy link

vyp commented Apr 22, 2017

Neat!

@olalonde
Copy link

You are on HN, congrats :) https://news.ycombinator.com/item?id=14170041

@mannuscript
Copy link

mannuscript commented Apr 22, 2017

I agree that what Disqus is doing is an overkill.
However, we should not forget that nothing comes for free...
Apart from this, getting redirected to GitHub for comment is very inconvenient...
Update: So I am automatically subscribed to comments thread via email...
Getting emails not only for replies on my comment but for every new comment.
Well, this is another overkill...
Don't forget User experience is more valued than user's data nowadays :D

Edit:
@dwilliamson forget about the free-ness argument, the bigger issue is of user experience, I got resubscribed to email updates after you mentioned me in one of the comment. This is a serious poor user experience.

@rattrayalex
Copy link

rattrayalex commented Apr 22, 2017

Interesting, thanks for sharing!

You might consider changing the link to include #new_comment_field (like so) so that users do not have to scroll. I believe this also focuses the field by default, which may make intent more clear.

Adding a button at the bottom of the comments section that opens the link might be helpful. Using about: _blank could be nice too.

A git hook might be useful to automatically generate the issues, though I'm not sure that'd be a good idea.

EDIT: Looks like their api supports POSTing comments; you'd have to set up user auth of course. https://developer.github.com/v3/issues/comments/#create-a-comment

@ghost
Copy link

ghost commented Apr 22, 2017

A test of comment with image and link.

img_4698

@globalcitizen
Copy link

globalcitizen commented Apr 22, 2017

Good work. In summary, to improve the solution further, add a button to add a new comment. Only when that button is pushed (in order to preserve privacy, remove drive-by viewer tracking potential, and reduce unnecessary server load on Github), somehow determine whether the user is already logged in to Github.

  • If not, then give them a chance to do so or sign up
  • If so, then display an add comment form on the page
    This could be a modal window, in a similar style to Stripe. If the user posts a comment successfully, the comment stream could be refreshed.

@citrusui
Copy link

I'm impressed by this! I'm going to see what happens when you post a comment from the @ghost account (another name for a deleted account)

@ghost
Copy link

ghost commented Apr 22, 2017

Hello world! This is a comment from the @ghost account.

@segiddins
Copy link

This is awesome!

@olalonde
Copy link

You might want to

  1. Add rel="nofollow" to your anchor tags to deter spam

  2. Link back to the blog post in the GH issue (you could do that in the first comment and not display it on your website). That way when I go back here due to :octocat: GH notifications, I can go back to the post easily instead of wondering what this is all about 😸

@ElijahLynn
Copy link

Great writeup, I was really hoping there was a way to comment without visiting Github.

@asciimo
Copy link

asciimo commented Apr 22, 2017

Very slick! I came to propose something similar to @globalcitizen's proposal, but they put it more succinctly.

@bexelbie
Copy link

Did you consider https://staticman.net ? This gets you comments as PRs and comments from the page.

@tbodt
Copy link

tbodt commented Apr 22, 2017

@bexelbie but staticman isn't as FUCKING AWESOME as this

@dipakc
Copy link

dipakc commented Apr 22, 2017

This is amazing! Thanks for sharing.

@aleman
Copy link

aleman commented Apr 22, 2017

Great!
I can already think of a few use cases for this in my team

@colinmegill
Copy link

Great idea. Thank you for this.

@crohr
Copy link

crohr commented Apr 22, 2017

I agree this is a great idea. But why not write your post directly into the issue as well? You might want to checkout my post Turn your GitHub issues into blog posts, which implements the same idea but also let you publish right from your GitHub issue as well.

@bkaradzic
Copy link

Love it! 👍

@lrzedzicki
Copy link

Very useful!

@andreis
Copy link

andreis commented Apr 22, 2017

Great technique that I'll definitely steal. Thanks!

@ghost
Copy link

ghost commented Apr 22, 2017

Brilliant idea!

@EddieOne
Copy link

EddieOne commented Apr 22, 2017

test = {
  something: 'monkey',
  function: function(arg) { return arg + 'YAY!'  }
}

Edit: We need pagination!

@cerisara
Copy link

Great ! I'll try this out... is it doable with a gitlab instance ?

@md2perpe
Copy link

md2perpe commented Jul 21, 2019

Code test:

let test = "Just a string";
another(line);
yet.another(line);

Edit: It seems like some extra CSS is needed for the code colorization.

@magicxavi
Copy link

haha

@adriansinger87
Copy link

adriansinger87 commented Aug 13, 2019

This is a cool way to use GH for both, as a host for static jekyll-blogs and for its comments. I will try this out!

So thank you for your work, here is my implementation: https://www.adrian-singer.de

@cphthomas
Copy link

Very nice post :O)

@yabozdar
Copy link

It's interesting. Cheers!

@gIsForGravity
Copy link

This is very cool

@ldoublewood
Copy link

this is my comment

@p4ttch
Copy link

p4ttch commented Nov 16, 2019

this is pretty neet!

@resthyphen
Copy link

this is pretty neet!

agree

@benstaf
Copy link

benstaf commented Feb 13, 2020

i am trying this github comment feature

@dollardhingra
Copy link

amazing man

@pedroth
Copy link

pedroth commented May 28, 2020

Great idea maybe will do the same

@Feelcame
Copy link

fdfdfdfd

@hadooper01
Copy link

chcking if live comment

@hadooper01
Copy link

will try to add this on my tech blog https://geekysoul.com/ . Thanks a ton!

@rioastamal
Copy link

test markdown for h1

@liuteriadautore
Copy link

Well, so you mean that I can post a "comment like that" right here?

@vuhanova
Copy link

comment

@BK1031
Copy link

BK1031 commented Aug 25, 2021

cool comment

@rezazsouilah
Copy link

good!

@x2v0
Copy link

x2v0 commented Dec 5, 2021

Test

eee

@jonathanvanderhout
Copy link

Test.

That's rad.

@sbrooker3
Copy link

this is another comment

@latenightly
Copy link

what a funny idea, i just wanted to try it out. I might use it myself. Thank you for making me randomly find you somewhere in the internet. that's why i love it.

@latenightly
Copy link

what a funny idea, i just wanted to try it out. I might use it myself. Thank you for making me randomly find you somewhere in the internet. that's why i love it.

@latenightly well i am self-referencing, but just trying out. Maybe i should tag someone else like @sbrooker3 just for this test. Lol?

@melbis
Copy link

melbis commented Jan 21, 2022

testing

@bloggrammer
Copy link

This is great to know. How about nontechie without a GitHub account?

@dwilliamson
Copy link
Owner Author

@Blogrammer I answered that one here #1 (comment)

@neshant
Copy link

neshant commented Aug 24, 2022

good stuff! thanks for a detailed blog post

@jscreatordev
Copy link

comment

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests