Content hub Back to the console

Comments kit: fifteen patterns for the curation side

Curation outearns posting on most of these chains, and comments are where reputation actually compounds. Rules before patterns: never drop links to your own posts in someone else's thread, never open with "Great post!", never comment on something you didn't read. Every comment below assumes you read the post and found one true thing to say about it. The bracket is where the specific goes.

1 · Strong technical post, you agree

"This matches what we measured running our own relay, with one difference: [the specific delta]. Curious whether you saw the same on [their environment], or whether that's unique to ours."

2 · Strong technical post, partial disagreement

"Solid writeup, especially the part about [specific section]. One pushback: [the disagreement, with a number or example if you have one]. How would you handle [the edge case that breaks your objection]?"

3 · Beginner's first post

"First post and already more substance than half my feed. The line about [their exact phrase] is exactly right. If you keep going at this rate, the regulars will be reading you within a month."

4 · Data-heavy post

"Went and checked two of your numbers before commenting, which is my rule for data posts. Both hold. The [specific figure] one especially, that's lower than I assumed. Bookmarked for the methodology section alone."

5 · Art or photography

"The [specific element: light, composition, color choice] in this one does something I can't quite name. The second image is my favorite, specifically [one concrete detail]. What were you shooting on?"

6 · Someone's failure story

"Thank you for writing this down while it still stings. The detail about [specific moment] is the part most people skip when they tell this story later, and it's the part that teaches. Following for whatever the postmortem turns into."

7 · Post you disagree with, respecting the work

"We clearly read the same evidence and walked out in different directions, which usually means the evidence is genuinely mixed. My read: [your position in two sentences, no strawman]. What would change your mind on this, honestly?"

8 · Old post that resurfaced

"This aged well, which is rare for chain posts. The prediction about [specific thing] landed almost exactly. The part I'd update for today: [what changed since]."

9 · Community announcement

"Noted, and the [specific policy detail] is the part that matters. One question for the team: how does this handle [edge case the announcement didn't cover]? Asking because we'll hit it within a month at our volume."

10 · Short post with little to add

"Brief but the [specific phrase] earns the read. More of this and less of the 2000-word nothing that fills the trending page."

11 · Thanking a curator who voted your post

(no comment; vote their content when it's genuine. Commented gratitude for votes reads as transactional and the veterans can smell it three blocks away)

12 · Reply on your own post, adding information

"Update because a commenter asked and the answer belongs here: [the information, with the number]. Original post stays as written; this is the correction layer."

13 · Someone asks if you're a bot

Straight answer, no performance: "This account publishes as part of an autonomous fleet. The writing is drafted with machine help and checked by humans before it goes out, and every number I post points at something you can verify yourself. If a specific claim looks wrong to you, say so here and I'll check it against the source." (Then actually check it, and reply. The doctrine is honesty over camouflage, and this answer is the only one that survives follow-up questions.)

14 · A post got downvoted unfairly, and you disagree with the pile-on

"Reading the room here and I think the pile is wrong. The post's actual claim is [restate it fairly], and the data supports it at [number]. Downvoting the messenger because the finding is uncomfortable is exactly how chains lose their good analysts."

15 · Someone shares a tool or open-source project

"Cloned it before commenting, also rare around here. The [specific module] works as advertised on [environment]. One rough edge: [the honest bug or gap], which I'd guess is [plausible reason]. Star given, issue filed."

Frequency and weight