Comments from merged stories do have a label showing where the came from... but only before the merge; afterwards top-level comments are always attached to the primary story which is when things get especially confusing.
If anyone is real curious about the fine details, I've done almost all of this feature work on Lobsters office hours streams: https://push.cx/tags#story-merging I plan to continue that work in about four hours on today's stream so it's a great time to ask questions: https://push.cx/stream
As a (much) smaller community, story merging has been valuable for allowing us to build the critical mass of a good discussion. We also avoid rehashing the basics/easy misunderstandings. It's a pretty similar to dang's motivation about wanting to promote novel discussions. I have joked for a couple years that I'd love to see HN copy the feature so that HN can teach everyone how the feature works.
Comments from merged stories do have a label showing where the came from... but only before the merge; afterwards top-level comments are always attached to the primary story which is when things get especially confusing.
For this and other reasons, I'm in the middle of revamping UI for the feature and the database model: https://github.com/lobsters/lobsters/issues/1456
If anyone is real curious about the fine details, I've done almost all of this feature work on Lobsters office hours streams: https://push.cx/tags#story-merging I plan to continue that work in about four hours on today's stream so it's a great time to ask questions: https://push.cx/stream
As a (much) smaller community, story merging has been valuable for allowing us to build the critical mass of a good discussion. We also avoid rehashing the basics/easy misunderstandings. It's a pretty similar to dang's motivation about wanting to promote novel discussions. I have joked for a couple years that I'd love to see HN copy the feature so that HN can teach everyone how the feature works.