3 ms·

> Really looks interesting Thanks! > I like that there went some thought into integrating with the existing web, lowering the barrier of entry compared to oth

> Really looks interesting Thanks! > I like that there went some thought into integrating with the existing web, lowering the barrier of entry compared to other projects. Yeah-- we already have THE web, let's just upgrade it :) > when can we start to deliver fonts and jquery content-addressed from this? ;) Already: http://gateway.ipfs.io/ipfs/QmeWFWdyJo8hLnSEJNpEbKNnMHmFKS87DiZiYVbFJ5efhz/jquery.2.1.3.min.js http://gateway.ipfs.io/ipfs/QmeWFWdyJo8hLnSEJNpEbKNnMHmFKS87... Though if you want something to stick around, you have to seed it yourself for now. We'll write super simple "seed form S3" nodes soon :)

detaro 12y ago
> Though if you want something to stick around, you have to seed it yourself for now. Question: Do all nodes act as peers, serving from their local cache once they requested a piece of data (basically, does it feel like normal bittorrent in that regard)? Or are there differences?
- sillysauce 12y ago
  Yes, files (or blocks) you request stick around on your computer. There is a garbage collection command that will remove unpinned files. There is also going to be (not sure if it's implemented yet) the bitswap. More information about the bitswap can be found in the paper.
  - whyrusleeping 12y ago
    Yeap! bitswap is currently pretty dumb, but I have a branch that will watch the network for popular blocks and cache them for a short period (until GC). When I get more time, Im going to implement some more interesting AI into it, its currently pretty dumb. (code: https://github.com/jbenet/go-ipfs/compare/feat/smartswap https://github.com/jbenet/go-ipfs/compare/feat/smartswap)