Timeline for Close reason for questions asking for code
Current License: CC BY-SA 4.0
10 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Dec 22, 2019 at 0:00 | history | tweeted | twitter.com/super_user/status/1208537769741561862 | ||
Dec 21, 2019 at 16:17 | comment | added | Tetsujin | @Ramhound - after I posted the above comment I decided to run it by Meta.SE … I'll see how the dust settles, but right now voting is only slightly over 50/50 - meta.stackexchange.com/questions/340788/… | |
Dec 21, 2019 at 11:10 | comment | added | Tetsujin | "Does this answer your question?" Reads as far more sarcastic than "Potential duplicate of…" Actually, the first time I saw it on a question of mine on SE Meta, where I'd failed to correctly search the dupe first, I just deleted the question in a huff. It was two weeks before I realised it was supposed to be the "new friendly" version. FAIL. | |
Dec 20, 2019 at 15:05 | vote | accept | Máté Juhász | ||
Dec 20, 2019 at 12:23 | answer | added | Tetsujin | timeline score: 9 | |
Dec 19, 2019 at 17:47 | comment | added | Ramhound | I absolutely hate the new “does this answers your question ...” comment for duplicates, these new “friendly” descriptions are absolutely horrible, nothing (blank text) would be more accurate then the new close reasons. | |
Dec 19, 2019 at 12:05 | comment | added | Máté Juhász | @Ramhound: you're right. In the past at least title was better, now neither that, neither description | |
Dec 19, 2019 at 9:20 | comment | added | Ramhound | The description of both those reasons have not actually changed. It’s just the “reason” that has changed. | |
Dec 19, 2019 at 8:17 | answer | added | Mureinik | timeline score: 16 | |
Dec 19, 2019 at 7:25 | history | asked | Máté Juhász | CC BY-SA 4.0 |