- Include the post item in your subject line. That would be "42922647" for this particular story.
- Include some idea of what the problem is. For example, for a flagged story I'd have "vouch" as the first word of my subject, followed by the article title.
- I typically include the full article link (in body) and title (in subject) as insurance against my own fat-finger-fumbling.
- A brief description of the problem. E.g., "I'd like to vouch for this article".
My own typical emails are for titles (frequent), link indirection, preferred sources, and occasional mentions of flagrant violations of HN comment guidelines (flagging tends to pick those up most of the time).
For the latter, you can use the "replies" endpoint to see if a mod has previously responded to a given userID, e.g.:
Addition: Comments also have IDs (and are essentially the same as posts), and if you're referencing a specific comment or thread, that should similarly be highlighted in the email subject.
- Include the post item in your subject line. That would be "42922647" for this particular story.
- Include some idea of what the problem is. For example, for a flagged story I'd have "vouch" as the first word of my subject, followed by the article title.
- I typically include the full article link (in body) and title (in subject) as insurance against my own fat-finger-fumbling.
- A brief description of the problem. E.g., "I'd like to vouch for this article".
My own typical emails are for titles (frequent), link indirection, preferred sources, and occasional mentions of flagrant violations of HN comment guidelines (flagging tends to pick those up most of the time).
For the latter, you can use the "replies" endpoint to see if a mod has previously responded to a given userID, e.g.:
For dang replying to me: <https://news.ycombinator.com/replies?id=dredmorbius&by=dang>
(Yes, there's an admonishment in there if you dig back far enough, and I remember it.)