Timeline for Anything to do when a good answer is provided but none accepted?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:36 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Mar 20, 2017 at 10:30 | history | edited | CommunityBot |
replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
|
|
| Apr 24, 2014 at 13:45 | history | edited | CommunityBot |
Migration of MSO links to MSE links
|
|
| Mar 27, 2013 at 4:26 | comment | added | Alan H. | Interesting. At first, I like the idea of a "community accepted" answer, because I have definitely seen accepted answers that are, in fact, not correct, or which become outdated (and the asker is not always still around to update the answer as required by the march of progress). | |
| Mar 27, 2013 at 1:02 | history | edited | ɥʇǝS | CC BY-SA 3.0 |
added 70 characters in body
|
| Mar 27, 2013 at 1:02 | comment | added | ɥʇǝS | @EliahKagan Ah, yes. Forgot to mention that part. I usually link to here: meta.askubuntu.com/questions/1137/how-do-i-accept-an-answer | |
| Mar 27, 2013 at 1:00 | comment | added | Eliah Kagan | Leaving a comment asking someone to accept is more likely to succeed if you tell them how to accept. When I leave such comments, I include something like "if this solved the problem for you" or "since this solved the problem for you" (even though I only post such comments when it's pretty clear the post did). That decreases the chance of accidentally asking the OP to accept an answer that they don't actually like. The other thing to keep in mind about these comments is that it's best to delete them not too long after posting them, regardless of whether or not the answer was accepted. | |
| Mar 27, 2013 at 0:50 | history | answered | ɥʇǝS | CC BY-SA 3.0 |