Restrict Giscus Origins

[timothystewart6]

Checklist

• I have read and accepted the contributing guidelines.

Is your feature request related to a problem? Please describe

Currently, anyone with your gisscuss.repo_id can post to your discussion board. This can lead to others spamming your discussion board (un)intentionally.

Describe the solution you'd like

Please expose the origins attribute in _config.yml so we restrict which origins can load giscus.

Describe alternatives you've considered

None, no known alternatives exist.

Additional context

No response

[cotes2020]

The situation is a bit awkward, this feature requires a file giscus.json to be created in the repo root directory.

Currently I have no way to decide whether to generate this file based on the site config. If a user doesn't use giscus, then his/her repository will have a useless giscus.json.

Perhaps you can create this file in your own repo and configure it as needed.

[timothystewart6]

I see. Couldn't you just generate the file if the key giscus.repo is defined in _config.yml? Otherwise I agree, I can just create a giscuss.json

[timothystewart6]

Ah, nevermind. This would always be undefined when the site is generated.

[cotes2020]

I see. Couldn't you just generate the file if the key giscus.repo is defined in _config.yml? Otherwise I agree, I can just create a giscuss.json

To the best of my knowledge, this is not achievable, as expressed in my comment above.

[timothystewart6]

I will close it then, I totally understand why this would be confusing for some and there is a workaround if using giscus.