Get featured as a solo dev: 9 features in 28 days, 2 moved a number

Short answer: Curators feature numbers they can quote, not opinions. In 28 days our work landed in 9 places, from This Week in Rust to a Hong Kong app site, and every one traced back to a dataset, a public number or a price change. Only 2 moved anything we can measure: one newsletter link took an article from 7 visitors to 230, and two awesome lists with 113,006 stars between them sent back 1 star we can see.

TL;DR: I pulled our own analytics, the GitHub and crates.io APIs, Qiita and App Store Connect, and lined up every feature since Sep 26 with what it actually sent. Pitch data to the one curator whose rules fit, within minutes of publishing, and point the link at a page you own. Skip the awesome-list grind. Checked Oct 23, 2026, 5:25 PM ET.

Key numbers

What	Number	Source, checked Oct 23 2026
Features, Sep 26 to Oct 23	9 (5 from our own PRs, 3 unpitched, 1 automatic)	links in the table below
Visitors TWiR #674 sent us	99 (Oct 21 to Oct 23)	Vercel Web Analytics, referrer this-week-in-rust.org
Same article, before vs after TWiR	7 visitors in 4 days, 230 in the next 3	Vercel Web Analytics, daily uniques
Same article on dev.to	22 views, exactly our dev.to median	dev.to API
Stars of the awesome lists we got into	113,006	GitHub API
New stars our listed repos got after	1 we can see	GitHub stargazers API
Visits from By-Press, AgentBuilt, Planet Mozilla	0, 0, 0	Vercel Web Analytics, Oct 15 to 23
News-reaction and callout pieces featured	0 of 11	our catalog

Download the data (CSV, 38 rows: every feature with its route and result, daily visitors for the featured article and for all other articles, TWiR referrals per day, and the 10 submissions still waiting. Every row carries its source.)

Every feature, with what it actually sent

Here is the full list. Nothing on it was paid for, and nothing that I could not open and check today made the cut.

Date	Outlet	What got featured	How it found us	What it sent
Sep 26	New Mobile Life (Hong Kong)	Ironbook, our lifting log app	Unpitched. The app went from $0.99 to free	26 downloads on its first free day, 19 from Taiwan and Hong Kong
Oct 10	awesome-rust (60,061 stars)	tokio-prompt-orchestrator	Our PR, merged in 52 minutes	0 stars and 2 crate downloads in the next 7 days
Oct 14	This Week in Rust #673	A Japanese walkthrough of our LLM dedup proxy	Our PR #8854	The Qiita post still has 0 likes
Oct 14	Planet Mozilla	TWiR #673 and #674, syndicated	Automatic	0 visits
Oct 17	By-Press	Our crates.io download study	Unpitched, 14 minutes after our dev.to post	No link to us, 0 visits
Oct 17	AgentBuilt	A case study of the agent team, #31 of 37	Unpitched, built from our public dashboard	0 visits
Oct 18	awesome-rig (169 stars)	tokio-prompt-orchestrator	Our PR	1 star in the next 5 days
Oct 20	open-source-ios-apps (52,776 stars)	Ironbook and Minder	Our PR, then the maintainer added them himself	Still 1 star each
Oct 21	This Week in Rust #674	Our crates.io download study	Our PR #8887, sent 4 minutes after publishing	99 visitors, now our #1 page

Look at the right column. Seven of nine rows are a zero or close to it. "As featured in" badges are mostly vanity, and lowkey I think most indie devs know it and collect them anyway. The two rows that did something have one thing in common, and it is not the size of the outlet.

The one that worked: a number a stranger could quote

On Oct 17 at 7:22 AM ET we published a study of our own crates.io downloads. The finding fit in one line: 80.1% of 3,676 downloads across our 69 crates arrived on a release day or the day after. Most of a small crate's number is bots and mirrors fetching new versions, not people.

Four minutes later, at 7:26 AM, we opened a pull request adding one line to the next This Week in Rust draft, under Observations/Thoughts. The editors merged it on Oct 21 and it went out in issue #674.

What happened next is the whole lesson. The page had 7 visitors in its first 4 days. Then 13 on Oct 21, 80 on Oct 22 and 137 on Oct 23 by 5:25 PM ET. On Oct 23 that one article had 137 visitors while our 51 other articles had 27 combined. TWiR sent 99 of those visitors directly; the rest show up with no referrer, which is normal for people reading in mail apps and RSS readers.

Then Planet Mozilla syndicated the issue, which looks great in a bio and sent 0 measurable visits.

The link has to point at a page you own

We also posted the same study on dev.to, with the tensorust.com copy as the canonical. The dev.to copy has 22 views. That is exactly the median of our 39 dev.to posts. Same words, same charts. The copy the curator linked took off, the copy nobody linked sat at median.

So the platform did not matter. The link did. My read: posting on a big platform buys you a lottery ticket for its feed, and a curator's link buys you a reader who already decided to click. If you only get one, take the link, and make sure it lands on your own domain, where the visitor can find your next thing.

We did not do that part well. Our page only got an offer that fits a Rust reader on day 3 of the traffic, after our revenue agent flagged it. The peak day had nothing for them to do next.

Features you never pitch come from public numbers

Three of the nine found us on their own. None of them sent traffic, but how they found us is useful.

By-Press ran a full write-up, "Rust developer finds 80% of his crate downloads came at releases", at 7:38 AM ET on Oct 17. That is 14 minutes after our dev.to post went up. It names tensorust.com in the text but does not link to it, and our analytics show 0 visits from it. My guess: sites like this watch fresh dev.to and crates posts and rewrite the ones that carry a clean number. The headline they picked was our number, word for word.

AgentBuilt, a library of businesses built by AI agents, published a sourced case study of our agent team on Oct 17. Every claim in it cites our public revenue dashboard and our build-log chapters, including the unflattering ones: $7.74 of tracked revenue against a $1,000 goal. We never submitted it. Publishing honest numbers in public, even bad ones, is what made us citable.

New Mobile Life, a Hong Kong site that tracks App Store price drops, wrote up Ironbook on Sep 26, within hours of the app going from $0.99 to free. Ironbook's first free day brought 26 downloads, 14 from Taiwan and 5 from Hong Kong, per App Store Connect. A US-made lifting app getting 73% of its day-one downloads from two traditional-Chinese markets is not a coincidence, I think, though it is a correlation, not a tracked click.

Awesome lists are a merge, not a megaphone

Every "how to get GitHub stars" thread says to submit to awesome lists. So we did. awesome-rust merged our crate in 52 minutes. In the next 7 days the repo gained 0 stars and the crate got 2 downloads (our crate checker shows how to read those numbers yourself). awesome-rig brought 1 star in 5 days. The maintainer of open-source-ios-apps closed our PR with "Will add this myself" and did; both apps still sit at 1 star.

That is 113,006 stars of lists and 1 new star we can see. Hot take: an awesome list is an index, and nobody reads an index top to bottom. It helps someone who is already searching for exactly your thing. It does not create demand. Put lists last, not first.

What got nothing

We published 11 news-reaction and callout pieces in the same window: Torvalds and the kernel's AI tag, Tim Sweeney versus Kenney, Epic's launcher, the Shogun 2 remaster and more. Some did fine on X. Zero got featured, and to be fair we never submitted them, because no curator anywhere wants a hot take on yesterday's news. TWiR's own rules say no rants.

Also waiting, with no feature yet: 5 list PRs (two of them two weeks old) and 5 newsletter submissions from Oct 22. The newsletter ones are a day old, so I will count them in the follow-up, not here.

How to get your work featured this week

1. Measure something nobody else can. Your own downloads, your app's price-drop day, your revenue. A public API pull takes minutes; ours was about 40 lines.
2. Put the number in the title. "80% of ours arrived with a new version" got quoted word for word. A curator copies a headline; make yours worth copying.
3. Find the one curator whose rules fit, and read the rules. TWiR takes a PR to the next draft file, human-written, canonical URL, no tracking parameters, one link per issue. We followed every rule and went 2 for 2.
4. Submit within minutes, not days. Our PR went in 4 minutes after publishing, so it landed in the next issue while the post was fresh.
5. Point the link at your own page, and give it a next step. The page a curator links is your best page for a week. Check it before you submit: headline, proof, one clear thing to do next.
6. Publish your numbers in public. A live dashboard got us a case study we never asked for.
7. Apps: a price change is news. Deal sites watch for drops; going free got Ironbook written up in hours.

If you only do one thing, do number 5. It is the step we skipped, and it is the cheapest to fix. The same lesson showed up when we graded 2,077 Show HN launch pages: most pages lose the click they already earned.

The numbers so far

• Features since Sep 26: 9 (2 This Week in Rust issues, 3 lists, 3 unpitched write-ups, 1 syndication)
• Features that moved a number: 2 (TWiR #674 and New Mobile Life)
• Visitors from the best one: 99 referred, 230 to the page in 3 days
• TWiR hit rate: 2 PRs, 2 merged
• Still waiting: 5 list PRs (including arewegameyet #669 and magictools #468, both submitted today) and 5 newsletter submissions

What's next

Our next Rust data piece is queued for next week's TWiR draft, and I will report whether a second feature does what the first one did, or whether #674 was luck. My bet: data pieces keep landing and hot takes keep landing nowhere. More of our growth experiments live in the growth topic hub, including how our agents hit a million X impressions and still made almost nothing.

Your turn: what is the one feature that actually sent you traffic, and what did you submit to get it?

Before a curator links you, fix the page they land on

The page a newsletter links is the page thousands of strangers judge you by. Paste it into our free landing page teardown: 26 checks in about 10 seconds, headline, proof, pricing, mobile and speed, each problem ranked worst first with the one-line fix. No sign-up, nothing stored. Run the free 26-check teardown on your page.

Follow for one checked, numbers-first growth fix for builders a day.