A peer-to-peer hypermedia protocol to make the web faster, safer, and more open.
We recommend running it on a machine with at least 2 GB of RAM (it’ll do fine with only one CPU core), but it should run fine with as little as 1 GB of RAM. On systems with less memory, it may not be completely stable.
ipfs command line added to NAS $PATH
on start qpkg try to start daemon if ipfs is correctly init ( [~] # ipfs init )
becarefull port 5001 is actually used on NAS and you may be need to modify this inside config file located in /OPT/IPFS/.ipfs
IPFS aims to replace HTTP and
build a better web for all of us.
HTTP is inefficient and expensive
HTTP downloads a file from a single computer at a time, instead of getting pieces from multiple computers simultaneously. With video delivery, a P2P approach could save 60% in bandwidth costs.
IPFS makes it possible to distribute high volumes of data with high efficiency. And zero duplication means savings in storage.
Humanity's history is deleted daily
The average lifespan of a web page is 100 days. Remember GeoCities? The web doesn't anymore. It's not good enough for the primary medium of our era to be so fragile.
IPFS provides historic versioning (like git) and makes it simple to set up resilient networks for mirroring of data.
The web's centralization limits opportunity
The Internet has been one of the great equalizers in human history and a real accelerator of innovation. But the increasing consolidation of control is a threat to that.
IPFS remains true to the original vision of the open and flat web, but delivers the technology which makes that vision a reality.
Our apps are addicted to the backbone
Developing world. Offline. Natural disasters. Intermittent connections. All trivial compared to interplanetary networking. The networks we're using are so 20th Century. We can do better.
IPFS powers the creation of diversely resilient networks which enable persistent availability with or without Internet backbone connectivity.
TS-NASX86 TS-X31 TS-NASX86 64bits TS-X41