Skip to content
This repository was archived by the owner on Apr 16, 2020. It is now read-only.

Synthesize existing pinning ux research #14

Closed
meiqimichelle opened this issue Oct 2, 2019 · 6 comments
Closed

Synthesize existing pinning ux research #14

meiqimichelle opened this issue Oct 2, 2019 · 6 comments
Assignees

Comments

@meiqimichelle
Copy link
Contributor

meiqimichelle commented Oct 2, 2019

What do we already know about the most common user journeys for configuring and interacting with pins in IPFS across various entrypoints?

This is related to #15 re documenting what those entrypoints actually are, to start with.

@meiqimichelle
Copy link
Contributor Author

Pinning service API proposal by @lanzafame: ipfs/notes#378

@meiqimichelle
Copy link
Contributor Author

I've been putting links to existing documentation directly in the entry point list (then they're categorized and organized nicely). That list is here: https://gist.github.com/meiqimichelle/879a9b7ba89f441880dac656a43d2c61 .

@meiqimichelle
Copy link
Contributor Author

Outline the Various Applications of IPFS, with Use Cases and Dependencies https://github.com/ipfs/ipfs/issues/230

@lanzafame
Copy link

Just want to clarify that the Pinning Service API is slightly different to the general pinning concept, in that the pinning service api is about how I tell someone else that I am paying to pin a file for me and that is all. Obviously, the Pinning Service API is affected if we change what pinning actually means 🙃

@meiqimichelle
Copy link
Contributor Author

IPFS pinning 'current state / background' summarized here: https://gist.github.com/meiqimichelle/25d2221c08807841be7764b22f4a5bb5

@meiqimichelle
Copy link
Contributor Author

Closing this issue for now because there's no active work on this right now. Plz re-open as needed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants