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
{{ message }}
This repository has been archived by the owner on Aug 9, 2021. It is now read-only.
The ability load entries without verifying their signatures. This has two dimensions, one is to optimistically accept entries while loading and then verify after, the second is to not verify entires we already have seen and verified in the past.
The second already discussed a few months ago, the difficulty being from orbitdb/3boxs perspective you cant tell if ipfs just got a given block locally or from the network. It may be possible to tie these to together in some form, just no interfaces for that right now. It may be simpler to just have some "has seen" cache and it may be reasonable to use some space-efficient member test like a bloomfilter, although false positives less ideal here.
Need to specify further to breakdown in to separate issues. May need some interface hook from orbitdb or the identity provider may be enough.
The text was updated successfully, but these errors were encountered:
The ability load entries without verifying their signatures. This has two dimensions, one is to optimistically accept entries while loading and then verify after, the second is to not verify entires we already have seen and verified in the past.
The second already discussed a few months ago, the difficulty being from orbitdb/3boxs perspective you cant tell if ipfs just got a given block locally or from the network. It may be possible to tie these to together in some form, just no interfaces for that right now. It may be simpler to just have some "has seen" cache and it may be reasonable to use some space-efficient member test like a bloomfilter, although false positives less ideal here.
Need to specify further to breakdown in to separate issues. May need some interface hook from orbitdb or the identity provider may be enough.
The text was updated successfully, but these errors were encountered: