HNHacker News
TopNewBestAskShowJobs

lgierth

796 karma · joined January 7, 2012

I work on libp2p and IPFS -- https://github.com/lgierth

[ my public key: https://keybase.io/lgierth; my proof: https://keybase.io/lgierth/sigs/96UTewVcgE6mn2Hh1Tg3WCHUDRP_jWSFookoCcfruAg ]

submissionscomments
lgierth··on Dat – Distributed Dataset Synchronization and Versioning
Actually there's been some movement regarding URLs :) You can check out the reasoning and plan here: [1]

IPFS still has the long-term goal of path addressing (NURI), we just hadn't yet completely figured out what the upgrade path should look like. The discussion linked above is turning into a spec and into actions, i.e. IPFS will be trying to get as much as possible of Electron's protocol API [2] into WebExtensions, [3] and make us of that in the browser addons. [4]

[1] https://github.com/ipfs/specs/pull/152#issuecomment-28462886...

[2] https://electron.atom.io/docs/api/protocol/

[3] https://bugzilla.mozilla.org/show_bug.cgi?id=1271553

[4] https://github.com/ipfs/in-web-browsers

lgierth··on The case against blockchain for identity
IPFS is an immutable store. You add something to it, and put the resulting hash into a transaction.
lgierth··on Viper: a new programming language from Ethereum
Whenever I read this argument being made, I cannot help but think "didn't you read the fineprint?" :)
lgierth··on Uncensorable Wikipedia on IPFS
There's a circuit switching relay protocol [1] in the works which will allow multi-hop connections. This is generally useful for situations where two nodes can't directly connect to each other, be it because of NAT, censorship, or simply because they don't have a transport protocol in common (e.g. js-ipfs in the browser).

That means nodes can soon use the Websockets transport to connect to a domain-fronted node (this part already works), which then acts as a relay.

[1] https://github.com/libp2p/specs/tree/master/relay

lgierth··on Uncensorable Wikipedia on IPFS
Right now it's just a static list of addresses, but there's definitely more planned. One of the current discussions: https://github.com/ipfs/go-ipfs/issues/3908
lgierth··on Uncensorable Wikipedia on IPFS
Anything you access, you also provide (until it gets garbage collected), unless you turn on the `--routing=dhtclient` or `--routing=none` options.

Pinning prevents garbage collection, and is opt-in per piece of content.

lgierth··on Uncensorable Wikipedia on IPFS
Connections over the libp2p-tcp transport are trivial to spot, but there's more transports available (Websockets, WebRTC, UTP), and even more in the works (Onion, QUIC, FlyWeb).
lgierth··on Uncensorable Wikipedia on IPFS
Through IPFS yes -- the blog post describes how to, among other things.
lgierth··on Uncensorable Wikipedia on IPFS
IPFS can work just fine peer-to-peer over Websockets though, which pretty much look like a regular HTTPS connection. Other applications can make use of this too thanks to go-libp2p and js-libp2p.
lgierth··on Uncensorable Wikipedia on IPFS
You can also find an experimental PubSub system in IPFS [1]. One example use is peer-to-peer chat, Orbit [2].

[1] https://github.com/ipfs/go-ipfs/issues/3397#issuecomment-261... [2] https://github.com/orbitdb/orbit

lgierth··on Uncensorable Wikipedia on IPFS
Currently I'd advice against directly running IPFS over Tor or I2P, because it'll likely leak your IP addresess. OpenBazaar have successfully made it work as an Onion service, and their work is going to be upstreamed into go-ipfs soon.
lgierth··on Uncensorable Wikipedia on IPFS
English is coming in the next few days, along with Kurdish and Arabic
lgierth··on Uncensorable Wikipedia on IPFS
It's just simple relative links. If you're in /ipfs/QmPage/wiki/Page.html, then a link to './OtherPage.html' will result in /ipfs/QmPage/wiki/OtherPage.html.
lgierth··on Uncensorable Wikipedia on IPFS
Currently I'd advice against directly running IPFS over Tor or I2P, because it'll likely leak your IP addresess. OpenBazaar have successfully made it work as an Onion service, and their work is going to be upstreamed into go-ipfs soon.
lgierth··on Uncensorable Wikipedia on IPFS
@whyrusleeping is right, and adding to that, there's a work-in-progress Onion transport which is already being used by OpenBazaar in their fork of go-ipfs.

The respective work on making IPFS's routing work safely in an anonymous use case will be upstreamed soon.

lgierth··on Uncensorable Wikipedia on IPFS
One important anti-censorship measure employed by IPFS is that it doesn't have to rely on the Internet backbone to exchange data. Well, it's not so much an active measure, it's part of the core design.

You can be in the same room with no internet connection whatsoever and still exchange data.

Network transports get added kinda regularly, so far there's TCP, UTP, Websockets, WebRTC, and a couple of work-in-progress transports: Onion, QUIC, FlyWeb

lgierth··on Uncensorable Wikipedia on IPFS
What client and error? Works here and ssllabs.com has always turned up good results.

Maybe it's the fact it's (still) a StartSSL cert?

lgierth··on Next Generation MITnet
There's stuff like http://www.ipv4auctions.com/

We recently bought a /24 for ~$4k and now use it with Vultr's BGP support.

lgierth··on Vultr introduces $2.50/month plan
Best thing about Vultr is that you can bring your own IP blocks and have their BGP servers announce them.

The bandwidth overage is also pretty okay. ($10/TB in NA/EU, $25/TB in AS, and $50/TB in AU.)

lgierth··on Filecoin – A Cryptocurrency Operated File Storage Network
The latest news on Filecoin is that it's being built on top of Ethereum: https://www.youtube.com/watch?v=Itb_2EMgBUI

While Filecoin isn't available yet, IPFS and libp2p have been functional for more than two years, and can be used independently of Filecoin: https://github.com/ipfs/ipfs && https://github.com/libp2p/libp2p

(IPFS dev here)

lgierth··on Time to Encrypt the Cloud
I love ansuz's and cjd's work on CryptPad! I use it daily as my personal notes wiki synced between 3 computers, and occasionally for collaborative notes taking in video calls with ~15 people. My happiness levels have increased with every new iteration of features and fixes.

I recently suggested to add a frontend for collaborative agile retrospective boards, similar to Retrium. CryptPad seems pretty pluggable in that regard, and actually TIL it can even edit presentation slides now :)

lgierth··on WireGuard: Next Generation Secure Kernel Network Tunnel
I'm less worried about that because it's so small. WireGuard is ~4k LOC -- thus measurably less complicated than OpenVPN (~100k LOC + OpenSSL), StrongSwan (~410k), or SoftEther (~330k).

Numbers taken from slide 5 of https://www.wireguard.io/talks/codeblue2016-slides-en.pdf

Moving to kernelspace brings it up to par with plain IP networking, minus a bit of overhead for the cryptographic operations. Userspace networking has overhead which is hard to overcome: context switching and CPU cache invalidation, copying packets between kernelspace and userspace, etc.

lgierth··on Online migrations at scale
In addition, in replicated setups, the more important reason for throttling the migration is avoiding slave lag.

Disclaimer: I worked on LHM a few years ago, still one of my favorite projects :)

lgierth··on Site Reliability Engineering
Added it to IPFS: https://ipfs.io/ipfs/QmTfeaEwMSKzoA4TFS6G7Qz2p6XZ9pP89VVod42...

Command: wget --mirror --convert-links --no-parent --no-verbose https://landing.google.com/sre/book/

lgierth··on Distributing NixOS with IPFS
Also see the multicodec table for codes of ethereum/bitcoin/zcash/stellar

https://github.com/multiformats/multicodec/blob/2725f3c5cd7b...

lgierth··on Distributing NixOS with IPFS
> 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 types of systems, but it represents types of data structures. E.g. in the case of git, it's not "git,$thehash", but instead "git-tree,$thehash" or "git-commit,$thehash".

That way you know which code you'll need to run once you have the object's payload, or you could have datastores that simply pull blocks out of a git repo.

Is this getting closer to what you mean?

lgierth··on Distributing NixOS with IPFS
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 host all webpages within the ipfs project.

edit: And the part which turns /ipns/ipfs.io into an /ipfs path is called dnslink: https://github.com/ipfs/go-dnslink -- it resolves to what's in TXT _dnslink.ipfs.io.

> (on a random note: what's up with /blog returning the IPFS blog, instead of my own content? did i misconfigure something?)

I'm so sorry, that's a bug I put into the nginx configuration -- will fix it!

lgierth··on Distributing NixOS with IPFS
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/145
lgierth··on Distributing NixOS with IPFS
Use multihashes for hash algorithm agility :) https://github.com/multiformats/multihash
lgierth··on Distributing NixOS with IPFS
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 authority, as its name is derived from the content itself.
← PreviousPage 7 of 10Next →