Timeline for How to tell an editor they are doing something consistently wrong?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 15, 2014 at 1:11 | comment | added | Seth Mod | @AibaraIduas No, it will only ping the user if he/she meets the bullet-ed points above. | |
| Jul 14, 2014 at 20:51 | comment | added | Fern Moss |
@Seth Just to clarify, if you include @username in a comment, will it ping the user even if they haven't responded/interacted with a specific post?
|
|
| Jul 14, 2014 at 16:53 | vote | accept | Fern Moss | ||
| Jul 14, 2014 at 13:51 | comment | added | Seth Mod | @Jos No, that only works in comments. The only way they will see custom reject reasons is if they check it manually. | |
| Jul 14, 2014 at 12:27 | comment | added | Jos | I just did that: a custom reject reason with @username. A bit of a shame because the edit was otherwise OK. But will the reject reason end up as a message in this user's inbox then? If not, how to reach the user? | |
| Jul 14, 2014 at 3:27 | history | answered | SethMod | CC BY-SA 3.0 |