CSP (content-security-policy) errors prevent test on local Hugo install

I suppose this gets to the heart of the matter. What I don't understand is where I can access that very setting unless I have signed up already. I realize the answer will probably make me feel as foolish as these questions are proving me to be :-) --- but I really would like to give this a try, if only I could understand how to get to that setting without having signed up. Or is this code excerpt something that (while only testing and not yet having signed up) I need to include somewhere in a Hugo template page, much as I put the embedding code in one in a so-far-vain attempt to get it to work?

Would you like to copy paste the code you pasted in the Hugo template?
And the name of the template you're using, and which file in the template you have edited?
And the talkyardServerUrl = "..." value from the Hugo config file?
(If your code is in a GitHub repo, I could have a look, there.)

is this code excerpt something that [...] I need to include somewhere in a Hugo template page

Hmm what code excerpt do you have in mind? (fairly many code snippets are mentioned above :- )) Yes you do need to copy the comments HTML code into a Hugo theme file. On my Hugo demo blog, I placed the following (from the Hugo instructions) in file themes/pickles/layouts/_default/single.html:

    <script>talkyardServerUrl='{{ .Site.Params.talkyardServerUrl }}';</script>
    <script async defer src="{{ .Site.Params.talkyardScriptUrl | default "https://c1.ty-cdn.net/-/talkyard-comments.min.js" }}"></script>
    <!-- You can specify a per page discussion id on the next line, if your URLs might change. -->
    <div class="talkyard-comments" data-discussion-id="{{ .Params.discussionId }}" style="margin-top: 45px;">
    <noscript>Please enable Javascript to view comments.</noscript>
    <p style="margin-top: 25px; opacity: 0.9">Comments powered by
    <a href="https://www.talkyard.io">Talkyard</a>.</p>
    </div>

and for me (with Chrome Version 73.0.3683.75) that works fine when combined with:

[params]
talkyardServerUrl = "https://comments-demo.talkyard.io"

in config.toml.

Here's the GitHub repo for the demo b.t.w.:
https://github.com/debiki/hugo-talkyard-demo.git
and the Hugo theme file in wich I've inserted the comments code:
https://github.com/debiki/hugo-talkyard-demo-theme/blob/master/layouts/_default/single.html

Ok, maybe I can edit the instructions and point out that the conf value should be in the [params] section. I place config values in the wrong sections myself too every now and then ... and then I make myself really confused :- P

About the login problem. You don't happen to have 3rd party cookies disabled? The error looks similar to the error here:
https://www.talkyard.io/-217/disabling-3rd-party-cookies-in-ones-browser-breaks-blog-comments-login

Actually, I didn't. I have now gotten it to work in Chrome, Firefox, and iOS Safari but macOS Safari --- while it now will display the Talkyard widget --- is throwing errors when I try to reply with my GitHub credentials. It gives me a message as follows:

Error 403 forbidden
Not logged in [TyE0LGDIN_]

...and this persists even if I open GitHub, logged in as myself, in another tab. So I'm guessing there is some macOS Safari authentication weirdness going on, here. Nonetheless, I now can see it and use it in Chrome, Firefox, and iOS Safari, so at least I can test satisfactorily. Thanks again! [And, just to see whether it matters, I logged into this page from macOS Safari, again via GitHub, and will try to post the reply here. If you see this, it worked.]

Edit: It did. And, BTW: no need to edit your instructions. They're very clear. I just copied/pasted that line into the wrong area. I do know better. :-D

Ok. Just to see, if I understand this correctly — you can login, to the comments, with GitHub, in all of Chrome, FF, iOS Safari — and not in macOS Safari?

And, since I can see your reply above — you're able to login with macOS Safari, to this forum (right). However not to the embedded comments <iframe>. I'm thinking this might be related to Safari's Intelligent Tracking Prevention (apparently added to macOS Mojave), which I think can block friendly login cookies in an iframe (so, can break blog comments login, but not login to this forum). I would think if I make Talkyard login work in an <ifram> also without cookies, this macOS login problem will be gone.

Can I ask what iOS and macOS versions are you on?

You're correct; that's the situation, exactly. Versions are: macOS 10.14.4; and iOS 12.2 --- all current versions.

Ok, thanks for the info. I marked the post above about [params] as the answer to this question (and b.t.w. I updated the Hugo instructions so hopefully others won't run into this issue too).

I did some progress yesterday with enabling cookieless login, for macOS Safari with ITP, and browsers with 3rd party cookiest disabled. I'd think i'll have released something in about two weeks. I'll post updates in the other topic, about that:
https://www.talkyard.io/-217/disabling-3rd-party-cookies-in-ones-browser-breaks-blog-comments-login

Greatly appreciated, sir.