Thanks for the feedback, it's something I'll have to think about. If there is enough demand for a lower tier, I'll add it.

Seconded.

Have a look here, another embedded comments alternative. I'm looking to charge $2, + it's open source. Scroll down to the bottom, https://www.kajmagnus.blog/new-embedded-comments/

(The underlying discussion platform: https://www.effectivediscussions.org/ )

It has some cool features that people at HN might like: https://www.effectivediscussions.org/-32/how-hacker-news-can... (but I haven't ported all that to embedded-comments yet)

I really love how the embedded comments look, but I'm a bit concerned by your other sites. I want my content to be at the forefront, not the commenting system. Is that going to be an issue if I use your system, or are the extra features configurable?

Also, is there any possibility I could use my own users with your site? I don't want to have to make people sign up with another provider just to post comments.

EDIT: Your onboarding is really poor. I tried to create an account and it gave me some odd comments about an email "I specified in the config", and I have no idea what to do now. It seems I have half-created an account where my email is already used but I don't have a password to log in with. Neither can I reset my password or find documentation on how to embed comments.

EDIT 2: It looks like all the permalinks in your embedded comments point to the forum site? That's not something I want for my content, hmm.

Thanks, that was helpful feedback/info :- )

1) I'd like the blog post & content to be at the forefront too. What extra features do you have in mind that you would want to disable/configure? Were you referring to the sidebar with the most-recent-comments list maybe?

2) Use your own users: In the future, I would want to support that. Hmm. How would it work. Maybe your website could send a message to the iframe that "the current user is logged in, with username @Someone, real name Some-One, and (optionally) email@exmalple.com?" — Or it could set some name-and-email cookie.

3) Onboarding: Ok really good to know that it's really poor. The email in the config — I should probably rephrase that, then, or maybe auto-pre-fill the email. It's the email one typed on the very first page, when one also picked a website name...

...What has happened is that you've specified which email the admin is going to have ... and later on you need to create the admin account. Maybe I could merge these steps into one. (They make more sense as 2 steps, when installing on a stand-alone server oneself — then, one first specifies the admin's email in a text config file.)

4) Permalinks are supposed to link back to the blog. However, for the blog to be able to scroll down & focus on the linked comment, I need to implement some message passing between the Javascript code running directly in the blog, and the iframe with embedded comments (so the main frame gets to know how far down to scroll). I haven't done that yet, and was thinking that for now maybe it makes more sense to link to the comments over at *.ed.community (where scrolling works, no iframe).

If you got the impression that all this isn't super ready yet, then yes that's correct, it isn't. Hopefully a beta version at the end of october. One can use everything already but ... might be a bit frustrating sometimes right now. I'm about to deploy a new server, this weekend I would think, with instructions about how one configures embedded comments.

Thanks for your reply! Please feel free to email me if you want to talk about this more (email is in profile). To reply to your points:

1) I mainly noticed the permalink leading to the "forum" domain instead of the page the user is currently on (like Disqus does).

2) The easiest way would be for me to receive an API key from you beforehand, and send you the user's email if you need that (e.g. to email them), or just a random-looking user ID, along with HMAC((email/id, timestamp), API key). This way you can replay the HMAC and prove that I know the API key I'm authenticating this user with. The timestamp is there to prevent replay attacks later on (e.g. to expire the signature after X minutes).

3) Ah, I got confused because I closed the page at some point and came back, and was getting some errors I don't remember now but that were confusing me at the time. When I realized I can just continue the flow, it worked, but yes, I would have liked it to be a bit more straightforward. I tried to log in with Twitter but you wanted write permissions, so I didn't.

4) Hmm, the way Disqus does it is by linking to https://<theblog>.com/<post>#commentid and then using JS to scroll to the element pointed to by the hash. I don't think message passing is required?

In any case, your system was the most visually pleasing and easy to compose with of the five I've tried, so I'd be quite eager to implement it in a side-project I'm working now. It's at a very early stage, but I'd be glad to give you feedback and pay for the product down the line (although I don't anticipate the project ever making any money or having many users, so I probably won't be able to pay much).

Ok, email sent :-) (& permalinks fixed, now they point to the blog ... but I haven't yet deployed the changes.)