Skip to content

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

Closed
jbenet opened this issue Mar 3, 2015 · 12 comments
Closed

IPFS Feedback #849

jbenet opened this issue Mar 3, 2015 · 12 comments
Labels
need/community-input Needs input from the wider community

Comments

@jbenet
Copy link
Member

jbenet commented Mar 3, 2015

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:

  • I'd love it if it were easier to ....
  • I wish that ...
  • I really hate when ...
  • It is very cumbersome to ...
  • ... is very annoying
  • ... is very broken

Thanks,
Juan

@whyrusleeping
Copy link
Member

I wish that the protocol didnt appear to have two layers of msgio wrapping.

@BrendanBenshoof
Copy link

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.

@kevinwallace
Copy link
Contributor

I wish the IPNS<->DNS mapping felt more finalized, so I could start relying on it.

@whyrusleeping
Copy link
Member

I wish all the log messages didnt say <autogenerated>

@chriscool
Copy link
Contributor

I wish that there were more tutorials, like step by step way to create a simple js app.

@whyrusleeping
Copy link
Member

I wish the daemon shut down quickly when i press ctrl + c

@Luzifer
Copy link
Member

Luzifer commented Mar 5, 2015

I wish there would be an HTTP-API documentation one can play around with (like on apiary or similar)

@Luzifer
Copy link
Member

Luzifer commented Mar 5, 2015

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.

@cryptix
Copy link
Contributor

cryptix commented Mar 6, 2015

I wish there would be an HTTP-API documentation one can play around with (like on apiary or similar)

👍 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.

@whyrusleeping
Copy link
Member

I wish ipfs had support for microtransactions.

@em-ly em-ly added the need/community-input Needs input from the wider community label Aug 25, 2016
@Powersource
Copy link

Pretty old thread heh.

But I wish IPNS was less buggy/faster I guess.

@daviddias
Copy link
Member

Continues on ipfs/notes#318

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
need/community-input Needs input from the wider community
Projects
None yet
Development

No branches or pull requests

10 participants