teekay/jcomments

A headless commenting platform for publishers. Usable with any CMS that is capable of custom integrations using REST APIs. Suitable for integration with statically built websites (JAM stack).

jcomments's Issues

Add a setting to require moderation

Give a grace period before an old API key stops working

Once a key is revoked, the API calls to the comments API will start failing. If a client wants a new key, maybe the old one should keep working for a while longer?

Or, let clients issue more than 1 key, and then they can get a new token, integrate it, and revoke the old token later.

Don't send email notifications for spam :)

Implement closing of account

Store dates in UTC, display in local

I want to see a page title, not just url, in the dashboard

The API app shall not mount the /account endpoints

Filter out any markup from name, email

We have content filtering for the comment text. Currently, commenter's name and email are not filtered at all, leaving the door open to a XSS attack.

Support for different formatting

I think we have to care about how the comments might be formatted.

The easy way out would be to allow arbitrary content and leave it up to the API client to apply any content filtering, if only to prevent XSS attacks.

The clients still are ultimately responsible for enforcing sane & safe markup on their website. Still, could we help them?

Session expires immediately when lifetime not set in .env

A reasonable default should be applied instead. README claims it's 30 days but that turns out not to have worked IRL.