Feed aggregator

Show HN: Microphone – Talk out your side-project ideas, then test them with ads

Hacker News - Mon, 07/13/2026 - 8:25pm

If you are an aspiring founder, any VC will ask you this question: “why are you the only person who could solve this”. If you want to generate passive income with your side idea, get ready to enter a crowded market as everyone and their mother is shipping. Unless you have an active X account or you’re a TikTok sensation distribution is going to be tough.

I just launched the trie.dev microphone beta to help folks find their edge. You yap into your phone about your ideas; Trie turns the rambling into hypotheses, then prioritizes them based on your experience and your realistic ability to distribute in that idea space — surfacing the problems only you can solve. From there you can generate creative and run Meta ads against your hypotheses straight from your phone, with zero setup, to see how real people respond.

I built it initially for myself and friends as an “intake form” for running paid ads to help validate our side gig ideas.

Happy to chat about how it works or the stack. Joining the waitlist will send you an email to join via TestFlight.

Comments URL: https://news.ycombinator.com/item?id=48900788

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: I MitM'd Plex to make remote streaming suck less

Hacker News - Mon, 07/13/2026 - 8:25pm

I've been hoarding media for a long time. Longer than I care to think about honestly. At this point the collection is large enough that several of the friends and family members I've shared my Plex server with have cancelled their streaming service subscriptions.

After getting laid off a while back, I started working on a degree online. It seemed like a good opportunity to spend some time traveling too, so I signed up for Starlink and got a friend to host my Plex server in his basement for the duration. Surely that would be good enough to watch whatever from where-ever.

Turns out that no, it's not. Plex really doesn't like streaming over Starlink. It would top out at 8-9mbps in good conditions, often dropping down to 2 or 3, while other streams and downloads would happily hum along at 100mbps+.

I spent a little time looking into the issue early on. None of the remote or server network changes I could think of made a noticable difference. Customizing Plex's internal MPV configuration to increase the chunk size and buffer limit helped a bit, but it was still too slow to watch anything in realtime.

My best guess was that the problem largely boiled down to a combination of Starlink's fairly frequent latency spikes and Plex's short timeouts. With things at school winding down, I decided to finally put that to the test by building some kind of caching proxy.

Initially the plan was to MITM the client/server connections so it could serve everything out of a cache and set it up to proactively cache things in the background. Once the client and server were talking reliably through the proxy, I realised those features wouldn't really be necessary. All it needed was a bit of parallelism and patience.

With my particular setup, 5 workers can reliably pull down segments at ~35-40mbps, adding another 5 pushes that up to about 60mbps. Either is more than enough to stream anything 1080p in realtime and 60mbps can handle almost anything 4K HDR. Ended up building the prefetching features despite that, because at that point why not?

Fast-forward a few days and I'm willing to call this a Good Enough first version. There are plenty of significant limitations and rough edges. It's almost entirely vibecoded and far from my best work ever. There's enough spaghetti under the hood that I have to actively avoid thinking about it. It works well enough that I don't have to start buffering a TV show 2 hours before I plan to watch it though, and that's what matters.

This is a niche tool for a niche problem. I don't really expect this to be of much use to anyone. It was a fun project though and a satisfying solution to an irritating problem, so thought I'd share it anyway.

Comments URL: https://news.ycombinator.com/item?id=48900786

Points: 1

# Comments: 1

Categories: Hacker News

Space Mirror: The FCC Just Approved a Sun-Reflecting Satellite, and Astronomers Are Unimpressed

CNET Feed - Mon, 07/13/2026 - 8:25pm
For now, a single satellite has been cleared for a test demonstration, but the company making it hopes to eventually launch 50,000 of them into orbit.
Categories: CNET

Show HN: Made a Free LLM Router

Hacker News - Mon, 07/13/2026 - 8:18pm

Hey everyone! Been working on a router that works with OpenAI, Anthropic, and Google (Gemini not Vertex), and just launched it for free.

Let me know what you think.

Comments URL: https://news.ycombinator.com/item?id=48900735

Points: 2

# Comments: 0

Categories: Hacker News

Tachyon: An AI Screen-Aware Tutor

Hacker News - Mon, 07/13/2026 - 7:44pm

Article URL: https://heybraza.com

Comments URL: https://news.ycombinator.com/item?id=48900478

Points: 1

# Comments: 0

Categories: Hacker News

Show HN: FixBugs – Reproduce production bugs and verify fixes

Hacker News - Mon, 07/13/2026 - 7:42pm

I built FixBugs, an agent that ingests the rich context surrounding production bugs to reproduce them in a sandbox and generate verified fixes. It's available in the form of a self-hosted VSCode extension and as a Github app:

VSCode Extension: https://fixbugs.ai/go/vscode-extension

- full code and data privacy. - zero data retention models opted out of training. GitHub App: https://fixbugs.ai/go/github-app

- we do access your code temporarily. - pick a repo to install FixBugs on. What motivated me to build FixBugs were my years being on-call at Google and VMware. How many hours did I spend gathering logs, traces, reviewing metrics, and reading code only to find that,

* Some context was missing.

* The bug wasn't reproducible.

* The alert was caused by a transient infrastructure issue.

Too many. Inefficiency in investigating staging/production bugs has a real cost, and it's paid both by developers and customers.

Current capabilities:

- Reproduce the bug. - Identify the root cause. - Generate a fix. - Verify the fix. - Review the generated code using multiple AI models to help catch potential regressions. Do try it and let me know what you think!

I'd especially love feedback from engineers who work with distributed systems or handle high-volume production bug triage.

Comments URL: https://news.ycombinator.com/item?id=48900465

Points: 1

# Comments: 0

Categories: Hacker News

Pages