Churn & reliability: Peers come and go, making stable streaming tricky. Latency: BitTorrent-style protocols aren’t built for real-time delivery. Incentives: Without rewards, too many users just leech. WebRTC: It hits limits fast and often relies on centralized relays. Legal risks: Media companies don’t play nice with decentralized distribution.

Bram Cohen tried with BitTorrent Live, but it fizzled out. Would love to see someone revive this with modern tech — still feels like untapped potential.

gofiber/fiber – not container-specific, but useful for building lightweight async schedulers if you're rolling your own orchestration logic.

dockertest – primarily for testing, but you can adapt its logic for simplified lifecycle management.

hashicorp/go-plugin – good for decoupling workloads, especially if you're considering container-based isolation per plugin/command.

That said, most teams I’ve seen build their own lightweight layer on top of the Docker SDK with Redis or internal queues for tracking load/health. Curious if you're doing multi-host management or keeping this local? Also, make sure to aggressively timeout and clean up zombie exec sessions — they sneak up fast when you're doing docker exec a lot.

Would love to hear more if you open source anything from this!

2. As someone who works across frontend and backend development, I still find bookmarklets incredibly useful for quick debugging and automation. While browser restrictions have tightened, tools like Tampermonkey or custom browser extensions can still help power users retain control. What are some creative ways you've found to keep bookmarklets alive?

Bounties & Sponsored Issues – Platforms like GitHub Sponsors, Bountysource, and Gitcoin offer paid opportunities to fix issues, build features, or improve security in open-source projects. Prioritize projects with active communities and funding.

Donations & Sponsorships – Set up GitHub Sponsors, Open Collective, or Patreon. This requires consistently contributing to high-impact projects and building a personal brand around your work.

Hackathons & Grants – Many OSS-focused hackathons and grants (like those from Mozilla, Linux Foundation, or NLnet) provide funding for impactful contributions. Target projects that align with grant programs.

Freelance Consulting & Custom Features – Companies often use open-source software but need custom solutions. If you’re an active contributor, businesses may pay for enhancements, bug fixes, or integration support.

Crowdfunding Specific OSS Projects – If you build something valuable (like a plugin, CLI tool, or framework extension), you can crowdfund its development via Kickstarter or similar platforms.

Merge-First Mindset – The key to sustaining this lifestyle is ensuring your PRs actually get merged. Engage with maintainers, follow their contribution guidelines, and build a reputation for delivering high-quality, non-disruptive code.

Content & Community Engagement – Write blogs, create tutorials, or host livestreams showcasing your contributions. Visibility brings opportunities.

It’s not the easiest path, but if you have the skills and discipline, you can make a living while staying independent.

Build a simple AI-powered resume screener to filter candidates based on key skills or an internal chatbot to answer common applicant questions.

Once you’ve tested and refined it within your own business, you can expand the tool’s capabilities or offer it to other companies facing similar recruitment challenges.

Start small, solve a real problem, and grow from there.

For me, LinkedIn is useful primarily for job opportunities, but outside of that, it feels like a platform full of noise with not much else to offer. The real support system seems lacking, and I’ve found that engagement can be difficult to generate unless you're already in those top circles. So, I agree—there’s definitely a lot of room for improvement.

After that, I received a solid offer from another company with a decent salary. However, during that time, I was traveling to the USA to visit my sister, and I was truly inspired by my brother-in-law, who was building products for his Silicon Valley startup. It opened my eyes to the reality of the startup world—a high-risk, high-reward environment where "no" isn’t really an option. I am here by my choice now, but a lot of things are new, and the work is overloaded, so I’m actively finding ways to simplify things. That said, balancing everything is still tough. Exploring discussions like this is helping me. How do you manage?

You mentioned grinding on marketing early on—what actually moved the needle? Was it pure consistency, or were there specific channels or strategies that made the biggest impact?

Prioritization helps, but in a high-growth environment, trade-offs aren’t always straightforward. You mentioned setting a ceiling on your work hours—how do you enforce that when leadership keeps shifting priorities?

One thing that helps me a bit: I try to prioritize based on impact—if something doesn’t directly contribute to growth, engagement, or key goals, I push it down the list. But still, balancing everything is tough. How do you manage?