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.