This repository has been archived by the owner on Feb 12, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Shared Core API (standardise across js-ipfs and js-ipfs-api) #110
Labels
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
Comments
daviddias
added
enhancement
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
labels
Apr 4, 2016
The work as started https://github.com/ipfs/interface-ipfs-core :D (really excited about it cause now we have tests!) |
This work has solidified and continues to grow in https://github.com/ipfs/interface-ipfs-core For notifications on API changes, see: ipfs-inactive/interface-js-ipfs-core#55 |
This was referenced Jan 20, 2022
This was referenced Mar 21, 2022
This was referenced Apr 7, 2022
This was referenced Nov 27, 2023
This was referenced Nov 28, 2023
This was referenced Feb 11, 2024
This was referenced Feb 11, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
exp/novice
Someone with a little familiarity can pick up
help wanted
Seeking public contribution on this issue
Once
js-ipfs
milestone 1 is reached, we will start seeing more applications that will use IPFS and perhaps even depend fully on it in order to work. It is very important that we standardise as most as possible the core-API, so that we save our users from countless upgrading hurdles.This will also help us identify how IPFS should be used directly. While we are at it, we must update
js-ipfs-api
to expose the same interface, so that apps can exchange between a full node and one accessible through an http-api without a problem.TODO list:
The text was updated successfully, but these errors were encountered: