I believe this is currently mostly manual (ie, Oli created a new post, did a database operation to move comments over, then posted a comment in the old place). Given that it seems to have worked out well in this case, if it comes up a few more times, we’ll look into automating it (and making small details like old-post comment permalinks work).
I’d have to read the LW 2 source to confirm, but from my experience with the API and relevant data models I’d imagine it’s just a matter of changing the “post” field on a comment and all its children. Then making that a button which lets you write a new post and append the comment tree to it.
So it’s a useful feature, but probably not a particularly difficult one.
Right, I agree that it doesn’t sound difficult from a web-development perspective, but I also think that only praising difficult-to-implement features would create the wrong incentives.
Wow, it’s neat that the LW 2 codebase gives you tools to move a derailed thread to its own post! Good job, whoever wrote that feature!
I believe this is currently mostly manual (ie, Oli created a new post, did a database operation to move comments over, then posted a comment in the old place). Given that it seems to have worked out well in this case, if it comes up a few more times, we’ll look into automating it (and making small details like old-post comment permalinks work).
I’d have to read the LW 2 source to confirm, but from my experience with the API and relevant data models I’d imagine it’s just a matter of changing the “post” field on a comment and all its children. Then making that a button which lets you write a new post and append the comment tree to it.
So it’s a useful feature, but probably not a particularly difficult one.
Right, I agree that it doesn’t sound difficult from a web-development perspective, but I also think that only praising difficult-to-implement features would create the wrong incentives.