You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
About 3 months ago, the console project was updated to use client.capability.blob.get(shard.multihash) from the @storacha/client.
As a result, the w3ui was also updated to use @storacha/client instead of w3up-client.
Additionally, a fallback strategy was added to the Console App to call client.capability.store.get(shard) if blob.get fails for any reason.
However, I recently released a new version of the @storacha/client and noticed that the store capability is no longer present in it — meaning the fallback strategy in the Console App won’t work anymore.
If we decide to use the @storacha/client in the Console App, we need to make sure it handles the store.get somehow, otherwise, we won't be able to fetch old content (uploaded before the blob protocol).
The text was updated successfully, but these errors were encountered:
@fforbeck we agreed to use w3up-client in w3ui until the store protocol was officially deprecated and removed. I think we can close?
I will add a task in the Store Protocol deprecation plan to handle migrating items stored using the store protocol to blob protocol. i.e. allowing folks to still list/remove items added via store protocol.
About 3 months ago, the console project was updated to use
client.capability.blob.get(shard.multihash)
from the@storacha/client
.As a result, the
w3ui
was also updated to use@storacha/client
instead ofw3up-client
.Additionally, a fallback strategy was added to the Console App to call
client.capability.store.get(shard)
ifblob.get
fails for any reason.However, I recently released a new version of the
@storacha/client
and noticed that thestore
capability is no longer present in it — meaning the fallback strategy in the Console App won’t work anymore.If we decide to use the
@storacha/client
in the Console App, we need to make sure it handles thestore.get
somehow, otherwise, we won't be able to fetch old content (uploaded before the blob protocol).The text was updated successfully, but these errors were encountered: