Build log: open-sourcing this Actor in 24 hours (dev.to series article 5)

[foxck016077]

Posted a 24-hour build log for this Actor:

📝 Open-sourcing an MIT Apify Actor in 24 hours — a build log

Topics covered:

• How I cut scope to ship a maintainable v1
• Why OAuth timing is the usability foundation, not a side feature
• Putting per-feature quota in the main flow from hour 10, not "later"
• The unglamorous async test + naming cleanup that prevents a bad first wave of issues
• Stranger's-eye review as the most-skipped, most-valuable last step

Part of the full design-notes series: https://dev.to/foxck016077/series/39719

If you've shipped something fast and would do the OAuth/quota split differently, would love to compare notes.

[foxck016077]

Hour 96 update — the post-launch funnel data

Four days in, dropping the actual numbers here for anyone curious how a small MIT Apify Actor launch resolves once you stop posting and let the channels settle:

• GitHub stars: 1 (organic, day 4 — kuerdy)
• GitHub forks: 0
• Apify Store runs: 2 (both my own)
• dev.to articles: 7 (now 8 with the transparency follow-up)
• dev.to cumulative reactions: 1
• HN: 2 submissions, both dead:true from the Firebase API within seconds (account-level shadow ban, not URL-level)
• Gumroad sales: 0

Full breakdown plus the 5 corrections I'd make if I were past-me at hour 0:
https://dev.to/foxck016077/7-articles-1-star-0-sales-4-days-what-an-mit-open-source-apify-actor-cold-start-actually-looks-j7l

The biggest takeaway: dev.to is a comment platform, not a publishing platform, for the first 14 days of an MIT utility actor launch. Comments on someone else's #apify post in the same week as your launch outreach a 7th solo article on your own profile.