Timeline for Should we close questions which ask for feedback to go elsewhere?
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 18, 2020 at 8:33 | history | edited | CommunityBot |
Commonmark migration
|
|
| Sep 5, 2018 at 11:00 | history | edited | ᔕᖺᘎᕊ | CC BY-SA 4.0 |
add another idea
|
| Sep 4, 2018 at 19:56 | history | edited | ᔕᖺᘎᕊ | CC BY-SA 4.0 |
added 34 characters in body; added 1 character in body
|
| Sep 4, 2018 at 19:20 | comment | added | Brock Adams | Notices are possible that don't lock the post. There is currently no notice here that's appropriate. But, if we can show a CM that several posts merit a new/custom notice, one can be added. | |
| Sep 4, 2018 at 19:16 | comment | added | ᔕᖺᘎᕊ | I completely agree. I didn't really mean lock the post, just adding the notice if it was possible! | |
| Sep 4, 2018 at 19:15 | comment | added | EKons | Locks also make the question unable to receive votes, which, I believe, app developers do deserve even if they otherwise want feedback to go elsewhere (you may want to weigh in on this). | |
| Sep 4, 2018 at 19:14 | comment | added | ᔕᖺᘎᕊ | Ah, you're right. I'm not sure if it'd be possible/high enough priority to get it done specifically for stack apps. But that feature request linked is basically what I'm thinking of :/ | |
| Sep 4, 2018 at 19:08 | comment | added | EKons | Ah, the dilemma. Note that the "moderator note" in the screenshot is actually a lock, and such notes can't have arbitrary content, only one of (three, IIRC) select snippets of text. | |
| Sep 4, 2018 at 18:59 | history | edited | ᔕᖺᘎᕊ | CC BY-SA 4.0 |
added 8 characters in body
|
| Sep 4, 2018 at 18:54 | history | answered | ᔕᖺᘎᕊ | CC BY-SA 4.0 |