post: add JS IPFS 0.36 release post #244
Conversation
alanshaw
requested review from
achingbrain,
daviddias,
hugomrdias,
jacobheun,
lidel,
vasco-santos and
dirkmc
content/post/88-js-ipfs-0.36.md
Outdated
|
|
||
| # 🔦 Highlights | ||
|
|
||
| ## 🧬 Base32 encoding for v1 CIDs |
There was a problem hiding this comment.
When will the default of a ipfs add be v1 CIDs?
There was a problem hiding this comment.
Could be as soon as next quarter - it'll be a lot easier now
There was a problem hiding this comment.
Can it be before IPFS Camp?
There was a problem hiding this comment.
❤️ I would like that...
It makes sense to get base32-able Peer IDs in before though. We can't really shout about being able to use CIDs in domains until we have that.
We should also orchestrate a release with go-ipfs for interop. I don't know how feasible it is to get this in from the Go side. I know this is a big breaking change for them (ahem, 0.5.0?). Personally, I'm feeling pretty stacked atm and I know it isn't the current plan.
cc @Stebalien @lidel
There was a problem hiding this comment.
We were discussing base32-able Peer IDs on Go Weekly, and we are on route to ship support for https://{libp2p-key-in-cidv1b32}.ipns.dweb.link as opt-in (requiring ipfs cid base32 conversion step) before IPFS Camp. Progress is tracked in ipfs/kubo#5287
content/post/88-js-ipfs-0.36.md
Outdated
|
|
||
| ## 🚤 28% faster stream multiplexing | ||
|
|
||
| We switched the multiplexing implementation to one that's simpler, smaller and faster. We're estimating it to be [around 28% faster than the old implementation](https://github.com/libp2p/pull-mplex/pull/8#issue-254730751). |
License: MIT Signed-off-by: Alan Shaw <alan.shaw@protocol.ai>
Co-Authored-By: Jacob Heun <jacobheun@gmail.com>
alanshaw
force-pushed
the
post/js-ipfs-0.36
branch
from
bb2b55d to
176851a
Compare
TODO: