kmenta.js.org / kmta.kmenta.js.org

[Kang0234]

• There is reasonable content on the page (see: No Content)
• I have read and accepted the Terms and Conditions
• The site content can be seen at https://kc.kang0234.top

The site content is a documentation and live-demo site for kmenta, an MIT-licensed, privacy-first comment system for JavaScript-powered sites (blogs built with Hexo/Vite/Next, docs of open-source JS projects, community pages), and is relevant to JavaScript developers specifically because the entire content teaches and demonstrates JavaScript integration: copy-paste embed snippets for static blogs and SPAs, kcomment.init() usage examples for React/Vue routing, and deployment walkthroughs for the JS stack it ships with (Node.js/Express, Cloudflare Pages Functions on the Workers runtime with D1/R2, Vercel + MongoDB). The comment widget embedded at the bottom of the page is the very vanilla-JS artifact the project distributes — every visitor interacts with a live, working demo rather than a landing page.

---

Project: Kang0234/KComment · MIT
Requested subdomain: kmenta → "kmenta": "kc.kang0234.top" (CNAME entry already committed on branch kmenta)

Thanks for reviewing! Happy to adjust anything. 🙏

[github-actions]

✅ All validations passed! Please wait for the JS.org maintainers to process your subdomain request.

[MattIPv4]

We do not offer NS delegation, you only offer CNAME records.

Please could you explain how your site's content (not the code) is related directly to the JavaScript ecosystem/community? Why is this something a JavaScript developer specifically would use more-so than anyone else?

[Kang0234]

Thanks a lot for the quick review and for pointing out that NS delegation is not supported — I've switched the entry to a plain CNAME ("kmenta": "kc.kang0234.top"), exactly as requested. 🙏

Regarding your question — how the website content (not the code) relates to the JavaScript ecosystem:

kmenta is a drop-in comment system aimed squarely at the kind of sites JavaScript developers actually run:

1. The live site is a working demo of the JS stack it ships with. The page visitors see at kmenta.js.org is served by Cloudflare Pages running the project's own JavaScript backend (Pages Functions on the Workers V8 runtime, with D1 for storage and R2 for image uploads). The comment widget embedded at the bottom is the vanilla-JS comment-widget.js that users copy-paste into their own sites — every visitor is interacting with the exact artifact the project distributes.

2. The content teaches JS integration, not general marketing. The /docs page is mostly practical JavaScript: one-script embedding for static blogs (Hexo etc.), kcomment.init() usage for SPAs (React/Vue routing examples), and deployment walkthroughs for Node.js/Express self-hosting, Vercel + MongoDB, and Cloudflare Pages. Nothing on the site is about a non-JS topic — the product only exists inside JS workflows.

3. Why JS developers specifically? Because the two things kmenta replaces are classic JS-community pain points: (a) third-party comment iframes (Disqus-style) that leak privacy and slow down static blogs, and (b) self-hosting barrier — kmenta deploys entirely on free JS-friendly platforms (Cloudflare Workers, Vercel) with npm install or a fork-and-click flow. Hexo/static-blog authors, open-source maintainers who need feedback threads on their docs, and indie JS tooling authors are the primary audience.

Happy to adjust the site content further if the maintainers feel anything is missing — for example I can highlight a Hexo/Vue integration showcase on the landing page. Thanks again! 🙏

[indus]

I think it is fine and already added your requested subdomain to JS.ORGs zonefile. But I get a Error 1014 - so the setup is not yet correct. You may want to add // noCF in the line of the subdomain you have requested. Or you have to configure your host to accept the custom domain (search for infos about "CNAME" custom domains in the documentation of your host)
I'll merge after we have "contact". Please keep this PR open.

[indus]

What do you mean with "CNAME entry already committed on branch kmenta"? Is this is a GitHub page? Then you are doing it wrong. Please check this documentation: https://help.github.com/articles/configuring-a-publishing-source-for-github-pages

[Kang0234]

Thanks for adding the subdomain to the zonefile so quickly, and sorry for the confusion — to clarify for both reviewers:

The site is hosted on Cloudflare Pages, not GitHub Pages. My earlier "CNAME committed to branch" wording was just referring to the cnames_active.js entry in this PR — poor phrasing on my part.

Root cause of error 1014: the original target kc.kang0234.top is itself a Cloudflare-proxied domain in my own account, so the js.org proxy was hitting a cross-user Cloudflare CNAME — hence the 1014.

Fixed in this PR:

• Target changed to kcomment.pages.dev (the canonical custom-domain endpoint of the Cloudflare Pages project)
• Added // noCF so the subdomain stays DNS-only on the js.org side
• On the hosting side, kmenta.js.org is now registered as a custom domain on the Pages project, so the host accepts the hostname and will auto-issue the certificate once the CNAME resolves

Should be all set once the zonefile change deploys. Thanks!

[Kang0234]

Hi, I'd like to add one more subdomain to this PR, and I want to be upfront about it.

kmenta.js.org is the public comment widget + landing page of my comment system. The comment system also needs a moderation / admin panel (approve/reject comments, handle reports, delete spam). I planned to give that admin panel its own subdomain: kmta.kmenta.js.org.

Why it's in the same PR: the admin panel is part of the same project and runs on the same Cloudflare Pages project (kcomment) backed by the same D1 database — it's just a different route of the same deployment (the admin API lives under /api/admin/*). So it also CNAMEs to kcomment.pages.dev with // noCF, exactly like the main subdomain.

To be completely honest: the admin UI is currently under development (the API spec already exists, but the Pages Functions for /api/admin/* are still being migrated from my self-hosted version). Adding the subdomain now is to reserve it in advance — please let me know if it's better to wait until the admin panel is live before merging this entry. I'm happy to split it into a separate PR if you prefer.

Thanks for your patience!

[indus]

@Kang0234 Is this kmta.kmenta some public admin panel or just for you? I just tried to add it and it returned a Error Code: SSL_ERROR_NO_CYPHER_OVERLAP

[indus]

@Kang0234 any updates on this? I'll have to close this PR and remove the subdomains if the error can't be resolved...

[indus]

No Progress - closing.