# Should Discourse make an effort to become a viable comment platform?

**URL:** https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-a-viable-comment-platform/274455
**Category:** Community Building
**Created:** [August 9, 2023, 4:53am UTC](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-a-viable-comment-platform/274455 "2023-08-09T04:53:00Z")
**Posts on this page:** 1
**Showing post:** 50

<div class="post-metadata">

### Author: ![angus](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/angus/32/341715_2.png) [@angus](https://meta.discourse.org/u/angus)
#### Post date: [February 4, 2025, 5:45pm UTC](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-a-viable-comment-platform/274455/50 "2025-02-04T17:45:13Z")

</div>

Given my experience with ActivityPub and [WP Discourse](https://github.com/discourse/wp-discourse) I think two-way commenting via embedded javascript is achievable. The embed script would contain the following:

1. Unauthenticated “read” working in a similar fashion to current js embed (with some optimisations).
2. Remote client (i.e. the user’s browser) [registers a user api key client](https://meta.discourse.org/t/feasibility-of-allowing-a-user-api-key-client-to-register-a-valid-auth-redirect/312901), specific to the user’s session and stores relevant details in the browser’s local storage.
3. User is presented with “Login to comment”.
4. User authenticates (with Discourse) to retrieve a session user api key which is stored in the browser’s local storage.
5. Each activity (comment, like, etc) is directly posted to a dedicated endpoint with appropriate safeguards, handling and task management.

> [@sam](#):
>
> I think the only viable path forward would be for a third party to prototype / build a solution. With the correct scoping and team on it I would consider sponsoring at least some of this.

With the right budget I think I could get v1 production ready and integrated with `discourse/discourse` in 6-8 months. Following on from initial release I could do the following:

1. Add explicit support for Wordpress, Ghost and other select platforms.
2. Write the documentation.
3. Support it.

cc @pmusaraj @mcwumbly

---

_[View the full topic](https://meta.discourse.org/t/should-discourse-make-an-effort-to-become-a-viable-comment-platform/274455)._