Some stories are direct responses to others. For example, error codes is a direct response to not leaving python. Having an easy way to see this would be pretty neat. Not sure how it should look/feel though.
Some stories are direct responses to others. For example, error codes is a direct response to not leaving python. Having an easy way to see this would be pretty neat. Not sure how it should look/feel though.
Instead of submitting a story, make it a comment? Fewer stories mean the original cycles out slower, even with lots of responses, and I can choose to follow or ignore the topic easily enough.
Shouldn’t the blog post itself make the connection? For example, the “error codes” piece could link to “not leaving python” in the header or footer of the post.
It does, but I think that it would be useful to be able to see from Lobsters the graph of responses from an influential blog post. For articles like Jeff Atwood’s controversial, “Please Don’t Learn to Code,” there were many responses, and the only way you could find them was by individually looking at every post and checking whether they were responses to his article or not. I think there could be a better way, and that this is useful meta-information that we can add regardless of whether the original author specifically links to the post that they are replying to, or just refers to it.