Allow setting/clearing the "don't autoformat" default outside the posting form
Provide a way, outside the entry posting form, to set the preferred (default, initial) value of the "don't autoformat" checkbox in that form.
When you post an entry, the state (checked/unchecked) of the "Don't autoformat" checkbox is saved and used as the default for the next time you post an entry. I never use that feature, always ignore the checkbox and start filling important information (like "which EFW stereotypical character am I going to be this time?") and once I'm done with the entry, I post it without giving that checkbox another thought. That approach works on LiveJournal, where the default (always unchecked) is what I expect. It doesn't, however, work on Dreamwidth.
I must have used that feature once on Dreamwidth, however (maybe by accident), because the checkbox is always checked, not unchecked as I expect it to be. However, because of the above, I never notice that until I check the entry or see it in my reading page. When I do, I can fix it easily for that entry by editing the entry, but that still leaves the wrong default for the next entry. I suppose I could post a dummy entry just to reset that (and in fact I'm going to do that as soon as I submit this suggestion), but I think I shouldn't need that trick, and besides it's inconsistent with the account settings option for the entry editor ("always RTE, "always HTML editor", and "whatever was used last" which is in effect the only option available for that dratted checkbox).
So I would like to have an equivalent setting for this checkbox, with the default option for this setting "whatever was used last" (for compatibility with current Dreamwidth behavior). The update page should only change the remembered default/initial setting if the user kept the option set to "whatever was used last", so the user-visible behavior won't change unless the user changes the setting from its initial value.
What should happen when posting from a client (including an external service - crossposting, reposting, daily Twitter digest, etc.) that doesn't specify a value for the "don't autoformat" parameter when sending entry data is less clear, and should probably be discussed with client developers on dw_dev. (This doesn't apply to clients, if any, who have their own user-configurable default for that option, only to those who don't supply any value for that field, perhaps because they don't know about it or because the protocol or API used doesn't make it possible or easy for them to - like clients using the Atom API.)
Should be implemented as-is.
Should be implemented with changes. (please comment)
Shouldn't be implemented.
(I have no opinion)
(Other: please comment)