-
Notifications
You must be signed in to change notification settings - Fork 105
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
@biglep 202305 feedback on Migration Guide and FAQ #120
Comments
I've seen mostly only "js-ipfs", but ipfs is supposed to be "IPFS" so i've personally written "js-IPFS" myself a few times
We should also link to benchmarks source and results
I agree that we shouldn't promote use of helia->kuboRPC. |
@achingbrain : a few things here:
|
Addressing some of the items in #120
It's IPFS in the logo so I think it was supposed to be js-IPFS but js-ipfs crept in because it's slightly easier to type. |
I have updated this section to be more specific about using |
This is a module used for internal compatibility testing, it's not something used by Helia/js-IPFS users so this may confuse people? We already have a general FAQ about interop, maybe this is enough? |
Do you mean this one? It was quite general, but I've linked to the section on garbage collection & pinning, hopefully that's better now. |
All items in the issue description have been completed. I'm closing this issue. |
Below is some feedback on recent new wiki pages. (Thanks for putting these together.)
Cross-cutting:
https://github.com/ipfs/helia/wiki/Migrating-from-js-IPFS
https://github.com/ipfs/helia/wiki/FAQ
The text was updated successfully, but these errors were encountered: