-
Notifications
You must be signed in to change notification settings - Fork 0
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 for dc25/myBlog #1
Comments
this is a comment |
this is another comment |
This is a comment with some markdown...
Boldit or Italicit or header// c++ syntax
int x = 3; |
I like! 🙂👍 |
Nice! ;) |
Very nice! A wonderful solution for Jekyll site. Very helpful. |
this is a test. good job |
Testing on new page. |
Great solution! |
Nice |
Interesting solution! |
Testing |
Testing ... Thanks for the solution. |
more testing --haskell syntax
main :: IO ()
main = do
print "Hello World"
print "Hello Again" // c++ syntax
int x = 3;
|
fadfadfadsfds |
Hi, did you ever manage to "migrate" the disqus comments over to github or did you just not bother with them? |
Hi @davidobrien1985, I didn't bother. Given that I could keep using disqus comments for old posts and switch to using github comments for new posts, it didn't seem that important.
|
@dc25 that's what I ended up doing on my blog now as well. |
Is it possible to allow users to comment without creating a GitHub account? |
I can't think of a way, not as a variant of this technique. |
I wonder if a comment form can be implemented which will post comments using the github account of the article author (in this case, @dc25). The form will have a field for a special linked identifier (github account, email address, etc.) which would serve as a way to uniquely identify the author of the comment. This "metadata" could be rendered as desired to make it clear as to who the author of the comment is. This would be one (inelegant) way to accomplish the goal of comments from users regardless of whether they own a github account or not. |
Testing |
awesome |
awesome! thanks! |
Cleaver Idea! |
) |
test |
does it still work |
It still works. Every now and then I rebase the reference implementation ( see the blog post for details ) to the latest minima and rebuild with the current jekyll to make sure. So far there have been no problems. I went through this process today (2020-08-30) and a few months ago ( 2020-05-29 ). After doing this exercise, I always re-publish the reference implementation on github. |
Test |
It's funny that people are still testing the comments. main(){
println("Ok working")
} |
Aloha!
|
testing |
testing comment |
Wow how cool is this |
cooomento |
Nice solution! |
Testing |
How does quote reply work? |
does this reaaly work? |
why is it sorted from oldest to newest |
No clue
On 31 Oct 2021, at 3:38 pm, ***@***.*** wrote:
why is it sorted from oldest to newest
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub<#1 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARLXQCFB72E6BR22PSBTYXTUJTB4NANCNFSM4DQRSDMQ>.
|
The comments are sorted from oldest to newest because that's how they were sorted in the original reference implementation. I started with that and never changed it. It seems like the right choice. Most platforms that I have seen that allow comments display them from oldest to newest. I think that's what most people are used to. That said, anyone who wants to use this system with sorting from newest to oldest can edit the following lines in github-comments.js : // choose one of the next two lines to determine display order (newest or oldest first).
const commentsHtml = comments.join(''); // oldest first
// const commentsHtml = comments.reverse().join(''); // newest first |
comment |
Test |
work like a charm! |
wow |
1 similar comment
wow |
Hey there! |
Love this as a solution! |
Very cool. I gutta try this! |
great, i was looking for how to do comments in jekyll ☺ |
This is a great idea |
Testing! |
Testing in 2024 |
Comments for blog post : Using github comments in a Jekyll blog
The text was updated successfully, but these errors were encountered: