One of the reasons for this is that curated posts get emailed out to a few thousand people and that email doesn’t include any comments, and frequently others have asked us for context on why we curated something when they get the email. So this way the curation notice gets to be included in the email.
A minor change might make this more perspicuous (although this suggestion should be viewed in the light of the OP and the thread from Said Achmiz’s comment on UX design): Begin the curation notice at the top of the OP with “Curated by (username)”.
How hard is it to make the Curation admin tooling include a text field for curation reason, that both gets posted as a comment, and included in the email? This really seems like a nice-to-have software feature request, rather than something that merits the grotesque violence of editing the OP!
As mentioned elsethread, I checked with authors the first couple of times. Having met no objections, I applied induction and tested whether maybe the overhead wasn’t necessary.
Shouldn’t be too hard, but seemed worth testing whether it was working in a low-tech solution before we build a thing. My guess is we will add this more properly relatively soon, if we keep doing it.
One of the reasons for this is that curated posts get emailed out to a few thousand people and that email doesn’t include any comments, and frequently others have asked us for context on why we curated something when they get the email. So this way the curation notice gets to be included in the email.
A minor change might make this more perspicuous (although this suggestion should be viewed in the light of the OP and the thread from Said Achmiz’s comment on UX design): Begin the curation notice at the top of the OP with “Curated by (username)”.
Could definitely do that. I felt more weird about putting my own name right at the top.
How hard is it to make the Curation admin tooling include a text field for curation reason, that both gets posted as a comment, and included in the email? This really seems like a nice-to-have software feature request, rather than something that merits the grotesque violence of editing the OP!
As mentioned elsethread, I checked with authors the first couple of times. Having met no objections, I applied induction and tested whether maybe the overhead wasn’t necessary.
Shouldn’t be too hard, but seemed worth testing whether it was working in a low-tech solution before we build a thing. My guess is we will add this more properly relatively soon, if we keep doing it.