# New blog comments for Ghost (Talkyard)

**URL:** <https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303>\
**Category:** Marketplace\
**Created:** [March 18, 2019, 2:22am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303 "2019-03-18T02:22:53Z")\
**Posts on this page:** 16\
**Page:** 1

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [March 18, 2019, 2:22am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/1 "2019-03-18T02:22:53Z")

</div>

I wrote a blog commenting system, a Disqus alternative. It works with Ghost.  
I only had to update the embedding code with `{{comment_id}}: data-discussion-id="ghost-{{comment_id}}"`, and insert into `content/themes/casper/post.hbs`.

It gives people who use Ghost, more options to choose among, than Disqus. Some people don’t like Disqus, because of ads and tracking — well apparently you know already, since you mention that, on the Disqus integration page.

And, does it make the Ghost blogs out there, look better, than with Disqus?

Here’s how it looks. It’s called Talkyard.

 ![2019-02-21--blog-comments-ex-anon](https://us1.discourse-cdn.com/flex015/uploads/ghost2/original/2X/7/75b19de0f7bf547f7e516e16b0f14671775da616.png)

  
Could it make sense to add Talkyard to the integrations page? Or what's required for a "plugin" to qualify for the integrations page?

This is open source. There’s also serverless hosting, with privacy, no ads no tracking. If you’d like to read more: [https://www.talkyard.io/blog-comments](https://www.talkyard.io/blog-comments). Feedback = welcome.

---

<div class="post-metadata">

**Author:** ![Kym](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kym/32/1136_2.png) [@Kym](https://forum.ghost.org/u/Kym)\
**Post date:** [March 18, 2019, 12:06pm UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/2 "2019-03-18T12:06:24Z")

</div>

Looks really neat - I’ve sent you a message to discuss integrations 👍

---

<div class="post-metadata">

**Author:** ![moreoo\_hizmetleri](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/moreoo_hizmetleri/32/2940_2.png) [@moreoo\_hizmetleri](https://forum.ghost.org/u/moreoo_hizmetleri)\
**Post date:** [March 18, 2019, 1:47pm UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/3 "2019-03-18T13:47:37Z")

</div>

Looks so good, I hope it works with Ghost nearly days.👍👍👍

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [August 15, 2019, 2:53am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/4 "2019-08-15T02:53:06Z")

</div>

@moreoo_hizmetleri (sorry for the late reply). There is an integration now (since some time in April), here: [Official Ghost + Talkyard Integration](https://ghost.org/integrations/talkyard/) — if you try it out, any feedback would be appreciated :- )

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [December 13, 2019, 7:41am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/5 "2019-12-13T07:41:28Z")

</div>

Anyone trying to host talkyard on the server? I only get blank pages :-/

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [December 13, 2019, 9:26am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/6 "2019-12-13T09:26:51Z")

</div>

@Happyfeet01 what blog software do you use? [**Edit:** I’m being silly. It’s Ghost, I suppose, I mean, we’re at Ghost .org. **/Edit.**] Would you maybe like to post your config?

You need to configure a certain `Allow embedding from` config value, here: `https://your-talkyard-server/-/admin/settings/embedded-comments`. Type the address to your blog, e.g. `https://your-blog.example.com`.

What operating system do you use? There’ve been problems (I’ve been fixing the last week) with Safari ITP (“intelligent tracking prevention”) that breaks cookies in iframes — but that shouldn’t result in completely blank pages.

If your blog is online somewhere feel free to send a link? (Or you’re testing on localhost?)

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [December 13, 2019, 10:35am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/7 "2019-12-13T10:35:32Z")

</div>

I use Ghost as Platform and add the embed Code to my themes post.hbs.

But that works with the hosting Variant from Talkyard. But selfhosted is the issue.

```auto
Attaching to talkyard_web_1

web_1 | nginx: [warn] duplicate MIME type "text/html" in /etc/nginx/nginx.conf:44web_1 | nginx: [alert] detected a LuaJIT version which is not OpenResty's; many optimizations will be disabled and performance will be compromised (see https://github.com/openresty/luajit2 for OpenResty's LuaJIT or, even better, consider using the OpenResty releases from https://openresty.org/en/download.html)

web_1 | nginx: [error] lua_load_resty_core failed to load the resty.core module from https://github.com/openresty/lua-resty-core; ensure you are using an OpenResty release from https://openresty.org/en/download.html (rc: 2, reason: module 'resty.core' not found:

web_1 | no field package.preload['resty.core']

web_1 | no file '/opt/talkyard/lua/lua-limit-bandwidth/resty/core.lua'

web_1 | no file './resty/core.lua'

web_1 | no file '/opt/luajit/share/luajit-2.1.0-beta3/resty/core.lua'

web_1 | no file '/usr/local/share/lua/5.1/resty/core.lua'

web_1 | no file '/usr/local/share/lua/5.1/resty/core/init.lua'

web_1 | no file '/opt/luajit/share/lua/5.1/resty/core.lua'

web_1 | no file '/opt/luajit/share/lua/5.1/resty/core/init.lua'

web_1 | no file './resty/core.so'

web_1 | no file '/usr/local/lib/lua/5.1/resty/core.so'

web_1 | no file '/opt/luajit/lib/lua/5.1/resty/core.so'

web_1 | no file '/usr/local/lib/lua/5.1/loadall.so'

web_1 | no file './resty.so'

web_1 | no file '/usr/local/lib/lua/5.1/resty.so'

web_1 | no file '/opt/luajit/lib/lua/5.1/resty.so'

web_1 | no file '/usr/local/lib/lua/5.1/loadall.so')

```

Maybe an problem?

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [December 13, 2019, 12:05pm UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/8 "2019-12-13T12:05:27Z")

</div>

Here is the Link to my Blog. [https://dasnetzundich.de](https://dasnetzundich.de) The comments are available under each post, but not Page.

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [December 15, 2019, 6:55am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/9 "2019-12-15T06:55:43Z")

</div>

Hi @Happyfeet01, Did you configure HTTPS? If not, that could have been the problem.

Thanks for posting the log messages — actually, those errors should be harmless. I’m seeing them on my own servers too, although those servers work fine. The errors are about bandwidth rate limiting, and apparently Lua script links that are now incorrect. I should fix that.

When embedding the comments at your blog, then, all you got is a blank `<iframe>`? No comments appearing below your blog post? But you could open the Talkyard site in your browser and login as admin? (when not embedded in an `<iframe>`)

I’m thinking maybe you didn’t add HTTPS to the Talkyard site?

Then, Chrome is going to block the Talkyard `<iframe>`, because your blog uses HTTPS and then any iframes need to be HTTPS too (not HTTP) otherwise Chrome refuses to load the iframe, and logs errors about insecure contents blocked.

I could make this more user friendly, and clearly inform the admin that the Talkyard server needs to use HTTPS, otherwise Chrome (and other browsers?) blocks the iframe and comments. … And it’d be nice with automatic HTTPS, e.g. sth like Traefik some time in the future.

(Or if you _did_ config HTTPS, … if you have any Chrome/Firefox/… Dev Tools messages I can look at, that’d be interesting)

Actually, maybe the comments script could show an error, above the comments, if there’s a blog website HTTPS, but iframe HTTP, mismatch. Hmm.

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [December 15, 2019, 7:38am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/10 "2019-12-15T07:38:20Z")

</div>

Good morning,

Sure https is configured. When I at my PC today, I show you my docker-compose file and the logs from Firefox. Maybe there is an mistake.

Best regards

Lars

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [March 24, 2020, 5:42am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/11 "2020-03-24T05:42:37Z")

</div>

Just adding a note that we (@Happyfeet01 and I) got this working eventually: There was a port conflict, both Talkyard and Ghost wanted to listen on ports 80 & 443, and in this case this was handled by moving Talkyard to a separate Virtual Private Server. Another approach would have been to add a reverse proxy in front of Ghost and the commenting system (whichever it is).

(Actually @Happyfeet01 I’ll send you a message over at Ty .io about OpenAuth, I think OpenAuth settings haven’t been configured for your self hosted instance yet)

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [March 24, 2020, 6:10am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/12 "2020-03-24T06:10:12Z")

</div>

Hi and good morning.

I get your message. I enable anonymous login and disable social login. Maybe I fix that this evening.

I can’t save the settings when i would enable anonymous comments.

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [March 24, 2020, 7:36am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/13 "2020-03-24T07:36:20Z")

</div>

(@Happyfeet01 I replied over at Ty .io — I think the Anonymous Comments thing is no longer related to Ghost)

---

<div class="post-metadata">

**Author:** ![Happyfeet01](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/happyfeet01/32/5283_2.png) [@Happyfeet01](https://forum.ghost.org/u/Happyfeet01)\
**Post date:** [March 24, 2020, 11:12am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/14 "2020-03-24T11:12:19Z")

</div>

Yes.

---

<div class="post-metadata">

**Author:** ![andy01](https://avatars.discourse-cdn.com/v4/letter/a/cdc98d/32.png) [@andy01](https://forum.ghost.org/u/andy01)\
**Post date:** [February 5, 2022, 10:54am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/15 "2022-02-05T10:54:50Z")

</div>

Does Talkyard auto-login with ghost members account? As the member should not have to login twice: one for the blog and the other for comments.

---

<div class="post-metadata">

**Author:** ![KajMagnus](https://sea1.discourse-cdn.com/flex015/user_avatar/forum.ghost.org/kajmagnus/32/2868_2.png) [@KajMagnus](https://forum.ghost.org/u/KajMagnus)\
**Post date:** [February 8, 2022, 7:16am UTC](https://forum.ghost.org/t/new-blog-comments-for-ghost-talkyard/6303/16 "2022-02-08T07:16:03Z")

</div>

@andy01, It does not. Agreed that it would be nice if it did.

It seems there is no way to securely add membership login to any type of blog comments, currently, (without editing the Ghost source code and self-hosting), see:

> [@Third party Single Sign On (SSO)](https://forum.ghost.org/t/third-party-single-sign-on-sso/3321/17):
>
> There’s an open invite for enterprise-plan customers to work with us on a beta implementation but so far none have needed it. Any work that is done would be in the open source version because there’s no “enterprise version”, there’s only the open source version slight_smile

(That’s about working on an implementation of Single Sign-On. That was December 2020, doesn’t seem as if anything has changed since then?)
