Comment by theturtletalks

1 day ago

Turning a paid sub like WisprFlow into your own weekend build (Jabber) is a great move, but you can take it further by finding open-source alternatives that already implement the features you're replicating. For dictation and speech-to-text like what WisprFlow does, there's Handy[0], a free, open-source, offline speech-to-text app that runs locally with Whisper models.

Once you identify something like Handy, instruct Claude to study how that OSS project actually builds the feature and adapt the logic to your stack. AI is really good at finding the "seams" (those connection points where a feature ties into the tech stack) and understanding the full implementation.

The trick is knowing precisely where the feature lives in the code (files, functions, modules), because AIs often miss scattered pieces and don't capture everything otherwise. That's what I'm working on at opensource.builders[1]: turning OSS repos into a modular cookbook of features you can remix across stacks, with structured "skills" that point to the exact details so the porting works reliably.

[0] https://github.com/cjpais/Handy

[1] https://github.com/junaid33/opensource.builders

4 comments

theturtletalks

Reply
altmanaltman  1 day ago

So basically steal code from OSS, oh no I meant "get inspired by" OSS code without actually contributing anything. This is just gross as a developer imo.

  • theturtletalks  1 day ago

    We're big believers in personal software: even with OSS alts existing, building your own in your stack is valuable. Before AI, you'd read code from other apps, understand the implementation, and reimplement it yourself. This just makes that easier and faster.

    My projects (Openship/Openfront[0]) are the first on the chopping block. We're creating modular OSS alts for every vertical (barbershops, hotels, etc.) for folks to take, remix, adapt, or fork into their tools. Chances are your AI model is already trained on similar OSS and building from it anyway. We make finding the exact code reliable. Check out our ethos to learn more [1].

    [0] https://openship.org

    [1] https://opensource.builders/ethos

  • pixl97  18 hours ago

    For most OSS code there is no responsibility to share your changes when you're not distributing them to other people. More so there are plenty of OSS licences that simply allow other people to do just this.