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
index file (is the cache flushed? if files are not pinned, will we drop them? if so this may stay small and possible advantage of human readable, otherwise probably no good)
datastore query (with something like index/<tree#>)
Further update:
I want to have every ipfs add make an entry in the files api space, maybe under /pins or something. With that implemented, we could almost (except for the advent of direct pins) remove pinning entirely, and replace it with 'copying to your local filesystem' which is an idea i really like.
Reacted by Jakub Sztandera, Kevin Atkinson and maartyl
Activity
ebuchman commentedon Nov 3, 2014
How best to track cached (non pinned) objects?
index/<tree#>)jbenet commentedon Jan 8, 2015
To go along with the fuse files, we should also have a command. maybe it's just an extension of
refsjbenet commentedon Jan 15, 2015
Update: this is possible to implement now. the blockstore has
{AllKeys, AllKeysChan}functionswhyrusleeping commentedon Jan 1, 2016
Further update:
I want to have every
ipfs addmake an entry in the files api space, maybe under/pinsor something. With that implemented, we could almost (except for the advent of direct pins) remove pinning entirely, and replace it with 'copying to your local filesystem' which is an idea i really like.daviddias commentedon Jan 1, 2016
π to this idea (and also making
files adda thing)whyrusleeping commentedon Jan 1, 2016
in the future, we may even move
ipfs addtoipfs files add. This would help with separating the ideas of DAG and unixfs better than we are now.Upgrade go.mod yamux to 1.1.5 (ipfs#257)