Convert any API into a ChatGPT plugin
langdock.com
langdock.com
We identified, that apart from the creation of the manifest and openapi files, developers will need support with versioning, monitoring their plugin and most importantly (automated) testing.
So we started to built a tool around this, and we're going to open source it soon, so that everyone can host it individually and doesn't need to give us access to potentially private data.
Would love to get your thoughts and feedback.
Moreover, the fact that you've conveniently launched on Product Hunt today raises my eyebrows. It feels like a calculated marketing stunt, rather than a genuine desire to contribute to the development community.
We started building this product with some non open source tools such as Firebase to get off the ground and be able to launch so quickly.
Now that we have the core functionality built, we are working on removing all non-open source services from our product to then release a version than can be run without external services. This version is launching in a few weeks.
Open-source is important to us, so that our code be audited by everyone and evolve around community feedback.
The intention to "remove all non-open source services" sounds like lots retrofitting and will likely introduce unnecessary instability and tech debt. It's almost like building a house, then deciding to replace the foundation while still expecting people to live in it.
Your statement about wanting your code to "be audited by everyone and evolve around community feedback" feels like a euphemism for offloading QA responsibility to your users. An open-source community is not your unpaid labor force.
All in all your justification doesn't exactly inspire confidence.
Besides, seeing these overtly positive and eerily similar comments popping up around your post is a bit too convenient. It's almost as if you've rallied a small army of supporters ready to sing your praises. But even if that were true, I'd like to remind you that astroturfing isn't a sustainable growth strategy, nor is it a decent substitute for genuine community engagement and a quality product.
But then again, if you're already comfortable with retroactively stripping non-open-source services out of your product, who's to say you wouldn't resort to a bit of artificial comment cultivation to make the grass look greener? It kind of feels like your project is less about 'open source' and more about 'being open to whatever tactics necessary to look successful.'
In the end, remember this: Even a thousand echoes can't make a single voice sound any more convincing. The value of your product will be judged by its actual usefulness to users, not by the number of friends you can enlist to say nice things about it.
Just food for thought.