Yes, this is unintuitive and a bug, you have to start writing articles from the main site to have an option of saving to Drafts, there is no such option in discussion area. But not working around this bug results in spurious articles appearing in the feed, hence it’s a posting “by mistake”, but the kind that can be avoided, and should be. This is the same kind of mistake as using HTML markup in comments—something that can be reasonably expected to work, but actually doesn’t, so has to be taken into account before posting.
It doesn’t seem the same as the HTML markup issue since there’s no obvious way of finding this out unless one triggers the problem. Is there any documentation anywhere that this bug exists?
So you are advocating downvoting people because they have acted like the minimal documentation is accurate and haven’t read every single post including a single post where a specific bug is mentioned?
Indication of bad consequences shouldn’t take into account difficulty of avoiding them, indeed it should calibrate the expended effort (and as I wrote, it’s possible to notice by comparing with article editor on the main site, or just by checking if the article got published after pressing a button, just in case).
You seem to be engaging in massive hindsight bias. You are expecting a large amount of effort be made to deal with an unlikely situation. Do you engage in that level of investigation in looking for bugs whenever you join a website you haven’t previously been involved in?
If I post globally, I would, at least would prefer to. I don’t post enough on popular sites to have a track record for this particular reference class, but I do make an effort to take seriously unlikely risks with nontrivial consequences that are trivial to avoid.
Replied here:
It doesn’t seem the same as the HTML markup issue since there’s no obvious way of finding this out unless one triggers the problem. Is there any documentation anywhere that this bug exists?
It was mentioned before, and if you posted to main area, you can notice the difference.
So you are advocating downvoting people because they have acted like the minimal documentation is accurate and haven’t read every single post including a single post where a specific bug is mentioned?
Indication of bad consequences shouldn’t take into account difficulty of avoiding them, indeed it should calibrate the expended effort (and as I wrote, it’s possible to notice by comparing with article editor on the main site, or just by checking if the article got published after pressing a button, just in case).
You seem to be engaging in massive hindsight bias. You are expecting a large amount of effort be made to deal with an unlikely situation. Do you engage in that level of investigation in looking for bugs whenever you join a website you haven’t previously been involved in?
If I post globally, I would, at least would prefer to. I don’t post enough on popular sites to have a track record for this particular reference class, but I do make an effort to take seriously unlikely risks with nontrivial consequences that are trivial to avoid.