-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
IPFS Feedback #849
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
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. |
I wish the IPNS<->DNS mapping felt more finalized, so I could start relying on it. |
I wish all the log messages didnt say |
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. |
👍 but I'd like to have a clean cut go client package for interfacing with the JSON API. I feel like |
I wish ipfs had support for microtransactions. |
Pretty old thread heh. But I wish IPNS was less buggy/faster I guess. |
Continues on ipfs/notes#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
The text was updated successfully, but these errors were encountered: