I find myself looking up commands/options in manpages or examples in cheat.sh, but that should no longer be the case, with how things are moving so rapdily. With wizaskdo you can generate/execute commands based on natural language instructions.
Right now this works against openrouter, but any contributions to support other providers are more than welcome.
Your feedback is very appreciated, and definitely we don't want to be seen as a crypto project. While in this current iteration we have that utilization token, I understand cryptocurrencies doesn't resonate well with too many scams. We are seeking a way out of that situation to be honest.
> We are seeking a way out of that situation to be honest.
You can fold the current company, start a new, cryptoless one, and then share a post about it on HN. I'd bet all of my coins that will get a lot more love here and in the wild
Thank you! glad you're liking it. It's definitely a concern
the incentives to provide a stable, secure service are certainly greater than incentives to steal your application's data. That being considered, you can choose the capacity provider you trust, or even run your own nodes to host your workloads (or plan the system with services like https://github.com/threefoldtech/0-stor_v2)
I see. Having to vet and pick a provider seems to diminish the decentralization aspect somewhat. The upside is of course no provider lock in.
At first glance I had the impression of a decentralized crypto funded cloud and my mind goes directly to a homogeneous cloud of crypto miner like entities that are providing the capacity. But this system isn't trust free so that Idea can't work.
Now I understand the core aspect of the product to be a open framework that horizontally scalable cloud infrastructure can be built on.
I'm not sure what the best path is but judging by this comment section, the crypto funded capacity seems to be a somewhat unhappy marriage with the core product, at least in the current post crypto boom landscape.
In any case, I wish you the best of luck with this project.
The reliability varies, given that not all hosts are the same, but we provide statistics on the nodes and depend on the workload you should use the provider with the best SLA conditions for you
Right now this works against openrouter, but any contributions to support other providers are more than welcome.
reply