lgierth

24 ms·

211.
by lgierth 10y ago
Also see the multicodec table for codes of ethereum/bitcoin/zcash/stellar https://github.com/multiformats/multicodec/blob/2725f3c5cd7b...
212.
by lgierth 10y ago
> Also, when interfacing with legacy systems like git repos, one needs to dereference a legacy hash without knowing what it points to, which is easiest done with custom schemas. The CID (address format) in IPLD doesn't represent typ
213.
by lgierth 10y ago
The HTTP gateway included in go-ipfs will try to use a Host header on requests for constructing an /ipns path. So e.g. http://ipfs.io/docs gets turned into /ipns/ipfs.io/docs -- this is actually how we h
214.
by lgierth 10y ago
Acknowledged -- the documentation around IPFS and libp2p is not exactly delighful yet :) A new community member as written up their notes on diving into the IPFS ecosystem here: https://github.com/ipfs/specs/issues
215.
by lgierth 10y ago
Use multihashes for hash algorithm agility :) https://github.com/multiformats/multihash
216.
by lgierth 10y ago
HTTP is centered around hosts being the authority over what content a certain URL maps to, while IPFS and other content-addressed systems don't have a notion of server/client, or central authority. The content itself is the author
217.
by lgierth 10y ago
Completely agree! Another comment has mentioned beakerbrowser.com, and at IPFS we're about to get js-ipfs in the browser to interoperate with go-ipfs. The goal with js-ipfs and the firefox addon is (1) seamless support for fs:/ipf
218.
by lgierth 10y ago
If you want to see Noise in action, applied to a real protocol, check out Wireguard: https://www.wireguard.io/protocol/
219.
by lgierth 10y ago
No problem: https://ipfs.io/ipfs/QmZdGfVQvmdKvuj1gJzmdKAifecSw5WQugA9CiG...
220.
Peer enhanced web acceleration service, powered by your website's visitors(edgemesh.com)
4 points by lgierth 10y ago|0 comments
221.
by lgierth 10y ago
Performance of adding to IPFS has improved in the past months, I recently added 3.7 TB of https://cdn.media.ccc.de and it took ~24h, admittedly these files are each pretty big, while Wikidata sounds like tons of tiny files. One
222.
by lgierth 10y ago
For Wikipedia it would probably be more useful to embed js-ipfs [0] into pages, and fetch additional pages and assets after first one from ipfs. js-ipfs can currently speak WebRTC to peer with other js-ipfs nodes, and websockets to peer wit
223.
How we provided WiFi at Maker Faire: a detailed explanation(metamesh.org)
2 points by lgierth 10y ago|0 comments
224.
by lgierth 10y ago
tl;dr "combine code written in Go 1.0 and a proposed Go 2.0 in one program using the package level as the boundary between language versions" Thumbs up from me.
225.
by lgierth 10y ago
Isn't Bitcoin a pretty integral part of ZeroNet though? (I haven't tried it out myself yet.)
226.
by lgierth 10y ago
Yes we haven't been very vocal about it yet because it's not yet part of a go-ipfs release -- it'll be in the next release, go-ipfs v0.4.5. Note on the name: floodsub is one specific implementation of pubsub. There are many w
227.
by lgierth 10y ago
You're very right about the weaknesses of DHTs. We're planning ahead for future mitigations by making every layer of IPFS pluggable. We also devide routing into Peer Routing and Content Routing, as well as soon Wire Routing once t
228.
by lgierth 10y ago
There's going to be support for private networks, and for various ways of encrypting data. We just haven't gotten to it yet :) You can of course already encrypt the data yourself before adding it to ipfs.
229.
by lgierth 10y ago
kefka's replies to this question are accurate (thanks!)
230.
by lgierth 10y ago
There is no blockchain in IPFS.
231.
by lgierth 10y ago
Yes there's an HTTP-to-IPFS gateway included in go-ipfs. It's what backs https://ipfs.io , for example.
232.
by lgierth 10y ago
Hah, I agree with your resentment about the recent wave of "serverless" :) By now redis has been replaced with native IPFS pubsub, which is provided by both go-ipfs and js-ipfs. The only remaining server-ish is some means of boots
233.
by lgierth 10y ago
You can avoid that by using single quotes
234.
by lgierth 10y ago
I should probably also mention that even if you implement the existing NAT traversal protocols correctly, these aren't satisfying solutions. We really need that damn time machine already, the End-to-End Principle should have been an En
235.
by lgierth 10y ago
IPFS dev here -- judging from a quick look, Scout uses NAT-PMP and UPnP for NAT traversal, so it basically has the same occasional NAT issues as everybody else in the P2P space. By the way, sometimes NAT issues are the fault of routers hand
236.
by lgierth 10y ago
Mentioned this in your other comment too, but this time with name and link :) We "invented" dnslink for that, which is a TXT record of the form `dnslink=/ipfs/<hash>` or `dnslink=/ipns/<hash>` -- h
237.
by lgierth 10y ago
Hey -- one of the IPFS devs here. You can actually already use DNS to point a human-readable name to an IPFS hash. Try out `dig +short TXT ipfs.io`, take the `/ipfs/<hash>` from that record, and go to https://ipfs
238.
by lgierth 10y ago
The ruby lib DataMapper is actually an implementation of the active record pattern too ;) That's one reason to why ROM exists.
239.
by lgierth 10y ago
Nitpicking here, solnic didn't reimplement ActiveRecord (he did, but that's long ago) -- ROM implements the DataMapper pattern.
240.
by lgierth 10y ago
Cjdns is a p2p IPv6 network and doesn't do DNS -- I see how the name can be confusing though :) (I'm one of the developers)

More ›