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
Currently, recovery goes after IPFS says that it can't find any more blocks on the network, but this is not convenient from UX standpoint. That pushes a user to wait minutes even if there are enough nodes for recovery.
Goal
We need to define the actual point where IPFS will fallback on to recovery without degrading UX.
Solutions
Recover every time we see there are enough nodes.
Recover at the end of a timeout started when a node found min amount of blocks.
Questions
Recover often abusing CPU but serve content to a user faster, or recover less but keep the user waiting for content on the network more?
The text was updated successfully, but these errors were encountered:
Background
Currently, recovery goes after IPFS says that it can't find any more blocks on the network, but this is not convenient from UX standpoint. That pushes a user to wait minutes even if there are enough nodes for recovery.
Goal
We need to define the actual point where IPFS will fallback on to recovery without degrading UX.
Solutions
Questions
Recover often abusing CPU but serve content to a user faster, or recover less but keep the user waiting for content on the network more?
The text was updated successfully, but these errors were encountered: