I'll give it some more time to mature before considering it :)
796 karma · joined January 7, 2012
[ my public key: https://keybase.io/lgierth; my proof: https://keybase.io/lgierth/sigs/96UTewVcgE6mn2Hh1Tg3WCHUDRP_jWSFookoCcfruAg ]
I'll give it some more time to mature before considering it :)
1. how to decouple content from location, i.e. location-addressing vs. content-addressing 2. how to accept more network connection constructions than what URLs permit (proxying, domain fronting, tunnels, etc.)
> We could also imagine a new URL syntax, with fewer and less ambiguous syntactic meta-characters.
That's part of what we're attempting for network addressing with the multiaddr format: https://github.com/multiformats/multiaddr - If the author of the article is reading here, I'd love to hear your thoughts!
We're going with encapsulation and a posix filesystem compatible plan9-ish syntax and approach there. multiaddr describes the semantics of networking namespaces, and then various content systems bring their own namespaces. IPFS brings the /ipfs and /ipns namespaces for its content.
It's actually not too far off - IPFS is already capable of running a full js-ipfs node in a WebExtension's background page and expose its API to content pages. What's missing is minor things like streaming to/from the background page, and WebRTC in the background page.
For proper ipfs:// protocol support in the address bar and in links, a better protocol handlers API in WebExtensions is required though, which will take some more time. Basically right now with the ipfs-companion extension, ipfs:// URLs get rewritten to http://.
> open https://ipfs.io$(ipfs resolve /ipns/peerpad.net)I'd say at this point private networks and the filestore are unlikely to change significantly, but we're not 100% satisfied with the respective test suites (and the docs, oh my) so it'll be a bit longer until they'll be elevated out of experimental status.
About the object patch command, you can also call it through the HTTP API if that makes it easier. The CLI is essentially a 1:1 mapping of the HTTP API to a console command.
1) You can have individual files automatically be wrapped in a directory: `ipfs add -w dog.jpg` will result in `/ipfs/QmSomeHash/dog.jpg`
2) There's commands for modifying objects: e.g. `ipfs object patch add-link QmDirHash the-link-name QmLinkHash`
3) You can host multiple IPNS names from the same node since 0.4.9 or so -- see `ipfs key` and `ipfs name publish -k`. You can also publish updates for the same IPNS name from multiple nodes, although admittedly that's a bit hacky right now, since it involves an additional tool: https://github.com/whyrusleeping/ipns-pub
4) What kind of directory structure are you looking for here? We've successfully and repeatedly used IPFS with large datasets of different kinds so I'm curious how we can improve this.
You can use it as the base for CRDT structures: https://ipfs.io/blog/30-js-ipfs-crdts.md
go get github.com/whyrusleeping/gx
go get github.com/whyrusleeping/gx-go
cd your-project/
gx install
go build // or whatever you were doing :)Fun fact: advanced networking setups like domain fronting are impossible to address in a URL/URI scheme. Check out multiaddr :) [3] A domain-fronted service could be addressed as something like `/dns4/google.com/tcp/443/tls/sni/google.com/http/example.com/ws`
[1] https://signal.org/blog/doodles-stickers-censorship/
My colleague Matt addressed this beautifully in a recent talk at the NSDR Symposium: https://archive.org/download/ndsr-dc-2017/04_Speaker_3_Matt_...
// edited to fix URL
Fair points :) We'll be addressing this in the coming months with increased work on the network stack (libp2p).
Fun fact: when URLs were being defined, some people expressed the opinion that location-addressing is a huge mistake to begin with. Almost all of the links and references in the respective mailing list archives are now: broken.
Anyone can help out by keeping a copy. With location-addressing additional copies of the content aren't just largely hidden, they also get into a weird mode of competition with the original URL. With content-addressing, additional copies instead forge stronger resilience.
There are examples of the use cases you mention being built with decentralized technologies. [1][2]
[1] The various cryptocurrency wallets and exchanges
Content-addressing doesn't alleviate the problem 100%, since content can still fall off the network - but it improves the structure of the network in a way that makes it tremendously easier to keep content around. It's not up the original source of the content (owner of the domain name) to keep the content around - anyone can help out by keeping a copy.
My colleague Matt addressed this beautifully in a recent talk at the NSDR Symposium: https://archive.org/download/ndsr-dc-2017/04_Speaker_3_Matt_...
Combine this with the recent work on PubSub [1] and CRDTs [2] and you can make many applications work locally, that are otherwise annoyingly strongly coupled to internet services (thing Etherpad, Google Docs, Skype, Github, etc.)
> For a truly distributed network we should look into ways to make internet work more like a mesh.
Yes! We'll be putting more work into the network stack (libp2p) in the coming months. IPFS itself has done a ton to rework how content is defined and moved around, and libp2p will do the same for the network connections underneath. Think overlay networks, cryptokey routing, packet switching.