Skip to content
This repository has been archived by the owner on Feb 12, 2024. It is now read-only.

Document the state of IPFS in the browser #2231

Closed
alanshaw opened this issue Jul 10, 2019 · 2 comments · Fixed by #2392
Closed

Document the state of IPFS in the browser #2231

alanshaw opened this issue Jul 10, 2019 · 2 comments · Fixed by #2392
Assignees
Labels
exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/docs Documentation

Comments

@alanshaw
Copy link
Member

alanshaw commented Jul 10, 2019

People are trying to use JS IPFS in the browser and are not always able to get it working the way they want.

A lot of the time it's because people don't understand the limitations of P2P networking in the browser or the limitations of the current JS implementation or sometimes it's just that they need to configure their node to use webrtc or websocket-star or something.

Having a resource to be able to point people at would be greatly beneficial to them and would save us having to write the same things down on every issue.

Perhaps this is a blog post?

@alanshaw alanshaw added exp/novice Someone with a little familiarity can pick up status/ready Ready to be worked P1 High: Likely tackled by core team if no one steps up topic/docs Documentation labels Jul 10, 2019
@alanshaw alanshaw self-assigned this Jul 16, 2019
@tapaswenipathak
Copy link
Contributor

tapaswenipathak commented Jul 31, 2019

Hi @alanshaw: Can I work on the ticket? or is the ticket internal?

@alanshaw alanshaw changed the title Document the state IPFS in the browser Document the state of IPFS in the browser Aug 1, 2019
@alanshaw
Copy link
Member Author

alanshaw commented Aug 1, 2019

@tapaswenipathak you're welcome to have a go at this! I think the document should live in https://github.com/ipfs/js-ipfs/tree/master/doc

@daviddias daviddias added exp/expert Having worked on the specific codebase is important and removed exp/novice Someone with a little familiarity can pick up labels Nov 5, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
exp/expert Having worked on the specific codebase is important P1 High: Likely tackled by core team if no one steps up status/ready Ready to be worked topic/docs Documentation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants