Go ahead, I have 100$ waiting for your efforts upon completion. Write the whole code, as a Docker image, including the frontend (no CLI), plus IPNS listener, deployable as a remote node in a distributed system of hundreds of peers, in less than 10 hours. I’ll be waiting to stress-test it. Why the pseudo-code? Just write it
If you manage to do it, give the DAO a reasonable timeline for all their projects and the appropriate funding. I’ll hate to be wrong but if you indeed manage to do it, then perhaps we are severely over-funding developers around here.
This style of argumentation is demeaning, shortsighted, and unproductive.
I agree with @inplco, there are more that goes in the development of this tool than just deploying a single script. Besides the front-end components, you have to consider in your design how to scale the application for hundreds if not thousands of clients (IPFS nodes can easily pair with 1000+ peers on average), you have to design how to handle and prioritise request processing, you have to consider security features, consider smooth deployment procedures, consider resilient and secure data storage strategies, consider the implementation of the netcode to enable networking with other nodes. On top of that are the expense for careful auditing, testing, and documentation.
