TomCasavant
commented
3 months ago I was messing around with this since I am routinely receiving comments that wouldn't show up on the bookmark because they're replies to me or to others and not directly on the bookmark this is what I ended up with:
Essentially I just added another column in the comments table for in_reply_to_url, so if a comment comes in with an inReplyToId that matches one of my existing stored comments then I add that to the table referencing the original bookmark ID and the replied to comment URL. I'm open to creating a PR for this but I'm planning on waiting until #138 gets merged in as I'm not sure what kind of database changes that introduces
as of Feb 2023 if someone replies to a Fedimarks post on Mastodon it gets queued as a comment in Fedimarks, but if someone replies to that Mastodon reply, it doesn't.
To fix this, we'll need to index all existing replies and look those up as reply-to ids to check when determining what bookmark to file a comment under. We could retain this specific reply-to information and build threaded comments on the fedimarks side, or experiment with flattening it all, but we should at least keep enough information to try some things out on the frontend.