This is dispiriting. It implies that if I want to practice writing blog posts without spending too much time on them I should write about topics that aren’t too important to me so I don’t waste the opportunity to explain something I actually care about in a way that inoculates people against better explanations in the future.
Maybe multiple tabs open and you accidentally posted it in into the wrong one? I haven’t experienced anything in this domain, so I will be In the lookout for similar things happening, and see whether it might be some hidden bug.
Just happened to me again and I didn’t have multiple tabs open, so I think it’s a bug. Both times the page I saw after submitting was the post I’d intended to comment on, but my comment wasn’t there.
I think this may be a thing where LW stores your comment in local memory (so if your computer crashes or the site reloads due to a new version deploy, you don’t lose your comment). I think comments that are parented under a comment get stored properly as a reply to that comment, but maybe global comments get stored as “truly global” rather than parented under a post.
And then maybe when you go to a new post, it keeps the old half-written comment, making it easier to accidentally po?
(Except that I just tried to replicate this on purpose and couldn’t get anything to happen, so maybe this is just wrong. But maybe points in a useful direction?)
I am actually just debugging a similar problem for private messages. Will try to replicate it for comments.
(Basic idea is that we persist the new-comment form between page transitions, and there is a bug where some of the properties of the form don’t properly propagate, and this might sometimes result in you being on a new page, with a form that still has the properties of the old page)
Hmm. I’d frame it more as “be aware of the cost of doing so” than “don’t do it.” My takeaway is more like “if you expect the piece you are writing to be controversial, it’s probably better to put it in a place where people who are the right inferential steps away will run into it.”
(On FB, this would mean maybe filtering it to particular friend groups. On LW2.0, it might mean making it a personal blog or feed post until it’s been through a round of comments to iron out the kinks)
Bear in mind there’s a whole different set of concerns like “value of you having the opportunity to improve as a writer” and “value of one set of people learning from the ideas even if another set of people get innoculated against them.” It does involve judgment calls, though.
This is dispiriting. It implies that if I want to practice writing blog posts without spending too much time on them I should write about topics that aren’t too important to me so I don’t waste the opportunity to explain something I actually care about in a way that inoculates people against better explanations in the future.
Huh, I don’t know what happened, this was supposed to be a comment on Idea Inoculation and Inferential Distance and I don’t know how it ended up here.
Maybe multiple tabs open and you accidentally posted it in into the wrong one? I haven’t experienced anything in this domain, so I will be In the lookout for similar things happening, and see whether it might be some hidden bug.
Just happened to me again and I didn’t have multiple tabs open, so I think it’s a bug. Both times the page I saw after submitting was the post I’d intended to comment on, but my comment wasn’t there.
I think this may be a thing where LW stores your comment in local memory (so if your computer crashes or the site reloads due to a new version deploy, you don’t lose your comment). I think comments that are parented under a comment get stored properly as a reply to that comment, but maybe global comments get stored as “truly global” rather than parented under a post.
And then maybe when you go to a new post, it keeps the old half-written comment, making it easier to accidentally po?
(Except that I just tried to replicate this on purpose and couldn’t get anything to happen, so maybe this is just wrong. But maybe points in a useful direction?)
I am actually just debugging a similar problem for private messages. Will try to replicate it for comments.
(Basic idea is that we persist the new-comment form between page transitions, and there is a bug where some of the properties of the form don’t properly propagate, and this might sometimes result in you being on a new page, with a form that still has the properties of the old page)
Yep, replicated it. Fixing it right now. Sorry for that happening.
Hmm. I’d frame it more as “be aware of the cost of doing so” than “don’t do it.” My takeaway is more like “if you expect the piece you are writing to be controversial, it’s probably better to put it in a place where people who are the right inferential steps away will run into it.”
(On FB, this would mean maybe filtering it to particular friend groups. On LW2.0, it might mean making it a personal blog or feed post until it’s been through a round of comments to iron out the kinks)
Bear in mind there’s a whole different set of concerns like “value of you having the opportunity to improve as a writer” and “value of one set of people learning from the ideas even if another set of people get innoculated against them.” It does involve judgment calls, though.