Closed jbenet closed 5 years ago
I wish that the protocol didnt appear to have two layers of msgio wrapping.
I want to be able to pin files in the webui. In combination with this, I want to be able to start a download in the background easily.
I wish the IPNS<->DNS mapping felt more finalized, so I could start relying on it.
I wish all the log messages didnt say <autogenerated>
I wish that there were more tutorials, like step by step way to create a simple js app.
I wish the daemon shut down quickly when i press ctrl + c
I wish there would be an HTTP-API documentation one can play around with (like on apiary or similar)
I wish there would be a way to see what mime-type the content of a hash has / which name it would be called by before downloading.
I wish there would be an HTTP-API documentation one can play around with (like on apiary or similar)
:+1: but I'd like to have a clean cut go client package for interfacing with the JSON API.
I feel like core/commands
already is that but it is only consumed by the cli tool from which it is hard to grasp how to use the commands on it's own. Maybe pkg commands
just lacks documentation and usage examples.
I wish ipfs had support for microtransactions.
Pretty old thread heh.
But I wish IPNS was less buggy/faster I guess.
Continues on https://github.com/ipfs/notes/issues/318
Hey all, would be great to get some feedback of the things you'd like IPFS to do better right now. This includes the go-ipfs repo, the ipfs protocol, the webui, all our codebases, our community channels-- really, anything. There's of course a lot well known and planned-- i'm merely prioritizing where we spend our efforts in the coming weeks.
Some questions to get you thinking:
Thanks, Juan