Reviewed at
2026-06-22 08:48:46 UTC
Reviewer
system
Comment / reason
honest take: this gets rejected as it stands, and i'd rather tell you exactly why so the next one lands. the topic is fine — airdrops got messy, a tracker helps. but the whole thing reads like a chatgpt export that never opened the app once. polished on the surface, nobody home underneath. it's the sndct landing page reworded, and that's the exact profile the program throws out on sight. where it reads like a machine wrote it: 1. one line per paragraph, the whole way down. "But there is a problem." / "Today, things are different." / "The challenge is managing them." every thought sits alone with a blank line around it. that staccato, drop-the-mic rhythm is the canonical ai-thread shape. people on x can smell it, that's why it's sitting at 2 likes. 2. zero contractions anywhere. "there is a problem", "things are different", "the challenge is no longer". humans contract. start writing there's / things're different / it isn't and a chunk of the ai smell goes away by itself. 3. the "not X, the Y" swing. "the challenge is no longer finding opportunities. the challenge is managing them." that mirrored pivot is the model's single favorite move. one per article max, ideally zero. 4. mckinsey vocabulary. "control center", "organization and execution", "the next phase of crypto participation", a heading literally titled "Why This Matters for Web3 Adoption". these are quarterly-report words, not words you'd say to a friend. say it plainer and it reads more confident, not less. 5. the feature dump. the bullet list — guides, curated opportunities, calendars, alerts, insights — is the app's menu pasted in. when you sell everything, you sell nothing. pick the ONE thing that actually saved you once and build around that. the real fix — and this is the whole game: there's not one specific thing in the entire article. no project you farmed, no night a deadline was closing and the calendar caught it, no figure. the standard here is "one real story beats five feature paragraphs", and right now you've got five feature paragraphs and no story. better wording won't save this. one true moment from your own farming will. that's the part a model literally cannot copy off you — it's where you win, so it's where you start. shape example, start inside a real scene and let the features show up because they happened to you: "two weeks ago i was farming [project] and the task window closed at 2am my time. i'd seen it on X days earlier and forgotten. the only reason i made it: sndct pinged me the deadline in my own timezone. opened the app, followed the steps, finished with an hour to spare. that's the gap between hearing about an airdrop and actually not missing it." one paragraph like that does more than the whole "Why This Matters for Web3 Adoption" section. on visuals: right now the only images are sndct's own app embeds — the campaign card and the events widget. that's the product's UI, not a visual you made. you're listed as a web designer / content creator, so this is where you should be eating. i want original work made for this piece: your real dashboard screenshots, a custom cover with proper typography, an infographic breaking down one feature. and give it a style — i'm tired of the default look web3 ships. brutalism, y2k chrome, risograph, pixel art, editorial, glitch, whatever's yours. since everyone's got AI now, your taste is the only real edge. last thing, the part that matters most: this is the article task, one per 14 days. that long window IS the reason the bar is this high — you have the time to sit down and make something that actually counts. right now it reads like 15 minutes and a paste, and the view count agrees. take the full two weeks: one real airdrop you farmed, in your own words, with your own visual. do that and i'll review it again gladly.