lgierth

18 ms·

121.
by lgierth 9y ago
@jbenet has discussed funding for open source infrastructure in-depth in a YC podcast back in June: https://blog.ycombinator.com/ipfs-coinlist-and-the-filecoin-... (transcript included)
122.
by lgierth 9y ago
There's only so many different ways of funding open source software development, and we selected one that wouldn't have us struggle for grants or VC money every other year. The funding of open source infrastructure is a huge probl
123.
by lgierth 9y ago
PeerPad, which evolved from the data structure in this tutorial, can totally fine be run from any location: - https://peerpad.net - https://ipfs.io/ipns/peerpad.net - https://ipfs.io/ipfs&#x
124.
by lgierth 9y ago
Oops, the URL in the video is outdated, the repo now lives at https://github.com/ipfs-shipyard/shared-editing-demo This is also the tech that PeerPad is built on: https://peerpad.net && https:&#x2F
125.
by lgierth 9y ago
CRDTs! https://ipfs.io/blog/30-js-ipfs-crdts.md
126.
by lgierth 9y ago
So, my colleague just started a discussion in one of our teams, it showed up in my email inbox with a subject indistinguishable from an issue comment, and with its own number counting (#1). That's kind of a deal breaker for me unfortun
127.
by lgierth 9y ago
Very interesting concerns about URLs! I've looked into better ways of addressing recently too, but coming from different problem spaces: 1. how to decouple content from location, i.e. location-addressing vs. content-addressing 2. how t
128.
by lgierth 9y ago
> Does anyone know any mainstream browserd planning to implement, I dunno, IPFS? 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 c
129.
by lgierth 9y ago
Note that https://peerpad.net is hosted right out of a go-ipfs gateway. You can instead also use https://ipfs.io/ipns/peerpad.net or http://localhost:8080/ipns/peerpad.net , or use a sp
130.
by lgierth 9y ago
These websockets node you see aren't servers. They're nodes like any other node, except they have a well-known domain name. They don't do any work that a browser js-ipfs node wouldn't be capable of.
131.
by lgierth 9y ago
The build system is written in nodejs -- it turned out way faster than both CMake and classic Makefiles.
132.
by lgierth 9y ago
Caleb James Delisle's Networking Suite
133.
by lgierth 9y ago
You're not giving me much to work with :) It's all about the data, how you write/read it, and how you structure it. IPFS gives you a networked database for immutable graphs, IPNS for mutable links, and PubSub plus CRDTs for m
134.
by lgierth 9y ago
And thanks for the feedback! :) We're actually thinking through the documentation overhaul right now (today and tomorrow) and large datasets are a top priority use case, so your post is really valuable. I'd say at this point priva
135.
by lgierth 9y ago
Hey, IPFS dev here, happy to help :) I promise we'll improve our documentation around storing and providing large datasets. 1) You can have individual files automatically be wrapped in a directory: `ipfs add -w dog.jpg` will result in
136.
by lgierth 9y ago
There's no such limitation in IPFS -- currently the largest known dataset is about 3.8 TB, a mirror of https://cdn.media.ccc.de
137.
by lgierth 9y ago
You got it the wrong way around - Filecoin will be built on top of IPFS, but IPFS itself works fine without Filecoin.
138.
by lgierth 9y ago
See PubSub: https://ipfs.io/blog/29-js-ipfs-pubsub/ You can use it as the base for CRDT structures: https://ipfs.io/blog/30-js-ipfs-crdts.md
139.
by lgierth 9y ago
We are working on extensions/addons for all major browsers -- you can see an early version here: https://github.com/ipfs/ipfs-companion
140.
by lgierth 9y ago
You're likely missing gx, the package manager used by IPFS and many projects in its community. Try: go get github.com/whyrusleeping/gx go get github.com/whyrusleeping/gx-go cd your-project&#x
141.
by lgierth 9y ago
Thanks for mentioning domain fronting! It's also been used by Signal to circumvent communications censorship in Egypt [1]. We want to bring domain fronting to IPFS by making libp2p's websockets transport capable of it. [2] Fun fac
142.
by lgierth 9y ago
One very important vector for adoption that often gets overlooked is interoperability. The cost of adoption can be significantly reduced by making sure the new thing nicely interoperates with the existing deployments. We're attempting
143.
by lgierth 9y ago
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. You don't need c
144.
by lgierth 9y ago
> Last I checked IPFS will not tolerate minute long latencies and requires a bandwidth above several kilobits per second which would immediately disqualify it for anything farther than the moon. > >And I'm not sure it would wo
145.
by lgierth 9y ago
I agree that HTTP doesn't have to die -- for many use cases it has serious flaws though, the most important being its coupling to location-addressing. You always need a domain name and path to construct a URL. If the host decides to ch
146.
by lgierth 9y ago
The one huge advantage of content-addressing over location-addressing (= URL with domain name and path) is that the original source isn't solely responsible for keeping the content online and the link working. Anyone can help out by ke
147.
by lgierth 9y ago
Noms is also a great example of a peer-to-peer database: https://noms.io
148.
by lgierth 9y ago
You're right - you can model any data as append-only though. Granted, in many cases it will require you to seriously sit down and remodel your data. Nobody's claiming it's going to be SQL and ACID transactions :) It's m
149.
by lgierth 9y ago
Ask any non-technical person whether they've ever been bitten by link-rot! :) 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
150.
by lgierth 9y ago
Another important factor for adoption/adoptability is how well the new system integrates with existing deployments of older systems. Ideally it completely interoperates with the older systems, while providing you with additional value

More ›