May 27, 2025 1:12 pm
It is actively being discussed again, and many have missed in the past, so we can think about a way to implement this if it is not too much work:
A different site had a feature where each roleplay post could have comments added to it, these would appear 'behind' the post, clicking the Comments(n) button would 'flip' the post and one would see the comments instead of the post.
This had the upside that people could comment on posts and not disrupt the roleplay flow. Comments and RPs were tied together.
This also had some downsides, for instance one could not see the post that was being commented on while reading the comments, and it was very hard to find a comment later, since one needed to click on every post to search for if that was the rp the comment was on.
One potential solution, off the top of my head, and possible not for v1:
As a simple mechanism, when saving a post (1) the system can scan it for links (it is already scanning for illegal tags or javascript and such), if the link is to a post on GP, we can create an entry in a new database table...
... say `rp_comments`, which contains two indexed integer ids, one the post_id of this comment and the other the post_id of the 'rp thread' it links to. (For each link, in case they go to different 'rp posts'.)
When rendering a post, we can check for the post_id in the 'second' column, and if it exists in the table, we can create a 'Comments' section/button/spoiler that links to each comment. Maybe it can include the first x number of characters/lines so we don't need to go there for short-enough posts.
If the db join and lookup is too expensive on each post render, we could add a single-bit-field to the posts table that indicates if the post we are rendering has 'comments' and only process this if that is true. This would be NULL for everything at first, but new `has_comments` flags can be added with new posts.
Once this works it would not be onerous to do a one-time check of every post (starting at the most recent and working backwards), to see it they have internal links, and then adding them to the `rp_comments` table for future viewing.
As a side-note/second-step we could designate a 'Comments thread' when creating a 'game thread' (same place we do 'discord integration'?), this would just be the thread id (and we could automate creating that thread if it does not exist?). Then we could add a Comment Button that creates a post in the Comment thread that contains a link back to 'the RP' (this does 'force' a style, but many people don't like 'manual' work, doing it manually should still work fine since this just handles the copy/paste URL and posting to the 'right' thread, or even just 'opening that thread in a new tab').
Footnotes:
1. Possibly only in designated threads? (2)
2. But I see value in this 'list of back-links' for general posts if we can bring the cost down.
Let's discuss?
A different site had a feature where each roleplay post could have comments added to it, these would appear 'behind' the post, clicking the Comments(n) button would 'flip' the post and one would see the comments instead of the post.
This had the upside that people could comment on posts and not disrupt the roleplay flow. Comments and RPs were tied together.
This also had some downsides, for instance one could not see the post that was being commented on while reading the comments, and it was very hard to find a comment later, since one needed to click on every post to search for if that was the rp the comment was on.
One potential solution, off the top of my head, and possible not for v1:
As a simple mechanism, when saving a post (1) the system can scan it for links (it is already scanning for illegal tags or javascript and such), if the link is to a post on GP, we can create an entry in a new database table...
... say `rp_comments`, which contains two indexed integer ids, one the post_id of this comment and the other the post_id of the 'rp thread' it links to. (For each link, in case they go to different 'rp posts'.)
When rendering a post, we can check for the post_id in the 'second' column, and if it exists in the table, we can create a 'Comments' section/button/spoiler that links to each comment. Maybe it can include the first x number of characters/lines so we don't need to go there for short-enough posts.
If the db join and lookup is too expensive on each post render, we could add a single-bit-field to the posts table that indicates if the post we are rendering has 'comments' and only process this if that is true. This would be NULL for everything at first, but new `has_comments` flags can be added with new posts.
Once this works it would not be onerous to do a one-time check of every post (starting at the most recent and working backwards), to see it they have internal links, and then adding them to the `rp_comments` table for future viewing.
As a side-note/second-step we could designate a 'Comments thread' when creating a 'game thread' (same place we do 'discord integration'?), this would just be the thread id (and we could automate creating that thread if it does not exist?). Then we could add a Comment Button that creates a post in the Comment thread that contains a link back to 'the RP' (this does 'force' a style, but many people don't like 'manual' work, doing it manually should still work fine since this just handles the copy/paste URL and posting to the 'right' thread, or even just 'opening that thread in a new tab').
Footnotes:
1. Possibly only in designated threads? (2)
2. But I see value in this 'list of back-links' for general posts if we can bring the cost down.
Let's discuss?