My learnings from building Blaze as a FOSS project
summary
Built a web peer-to-peer file sharing app called blaze that starts as a websocket prototype, moves to WebRTC for direct chunked transfers and later re-architects around WebTorrent to distribute to multiple devices; the live demo hits Product Hunt #1, crashes a free server, then stabilizes under DigitalOcean sponsorship and reaches 1,400+ GitHub stars. Key takeaways: most contributors open issues not code, sole maintenance consumes time, open source rarely reaches non‑tech users, and sponsorships/donations materially sustain projects.
AI-written summary · about
chapters (18)
- 0:00Blaze introduction
- 1:54Building peer-to-peer file sharing
- 4:02Prototyping Blaze challenges
- 6:32WebRTC for peer-to-peer
- 8:36Product Hunt launch feedback
- 10:45Rebuilding with WebTorrent PWA
- 12:52FOSS learnings from Blaze
- 13:14Contributors in open source
- 15:21Sole maintainer challenges
- 16:03Making FOSS accessible
- 19:11Open source licenses ethics
- 20:14Why not all software open
- 21:19Sponsorships donations FOSS
- 22:44Blaze roadmap future
- 23:08Q&A: Open source fun
- 24:12Q&A: Long-term contributors
- 25:36Q&A: User experience inspiration
- 26:18Q&A: Contributor expectations
related talks
44mFireside chat
44mBUILD A COMMUNITY, NOT A FRAMEWORK
15mLessons learned: Guidance on how to make open source development a success
26mBuilding Open Source Communities
40mTightrope Walking: Best Practices & Lessons Learned on Community and Business Buildi...
23mConsumption Is Fractal: Open Source...
22mLessons from HasGeek's FOSS Journey
31mSharing is Caring… At Scale!
