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 Paper review: IPFS – Content addressed, versioned, P2P file system
Both js-ipfs and go-ipfs have the circuit relay which effectively makes you dialable in the browser: https://github.com/libp2p/specs/tree/master/relay
lgierth··on Tiny Core Linux
I've regularly fit OpenWrt into 3 MiB, including an HTTP server and web UI.
lgierth··on Ask HN: What is your company's maximum vacation (at one time) policy?
> ps. I have a tool to help workers get the longest possible vacation. Am I allowed to publish the link here?

I don't see why that'd not be allowed -- please do go ahead!

lgierth··on Patchwork – Decentralized messaging and sharing app built on Secure Scuttlebutt
And here's a doc covering only the secure network transport: https://github.com/auditdrivencrypto/secret-handshake
lgierth··on Why I find IOTA alarming
I value the MIT Media Lab and its DCI group pretty highly. There is nothing about the Media Lab or the DCI in that first link of yours. [1]

So what were you trying to say?

What I did find in that first link of yours [1] is this gem though:

> The IOTA hash function, Curl-P, was designed to allow for practical collisions. The IOTA protocol’s security depends solely upon the one-wayness of the function, not its collision resistance. The rationale behind the design of Curl-P is a much more complicated question which we explain in detail.

This statement is alarming on so many levels.

[1] https://blog.iota.org/official-iota-foundation-response-to-t...

// edit: oops, I see now that it's a multipart post, so I'll have a look there.

// edit: yeah okay, nothing of substance in the other parts either.

lgierth··on Why I find IOTA alarming
DCI's report: https://github.com/mit-dci/tangled-curl/blob/master/vuln-iot...
lgierth··on Why I find IOTA alarming
> 1. There have no vulnerabilities in the past.

I don't know man, the MIT Digital Currency Initiative found a pretty bad one last August:

https://medium.com/@neha/cryptographic-vulnerabilities-in-io...

>  the IOTA developers had written their own hash function, Curl, and it produced collisions (when different inputs hash to the same output). Once we developed our attack, we could find collisions using commodity hardware within just a few minutes, and forge signatures on IOTA payments. We informed the IOTA developers, they patched their system, and we wrote a vulnerability report

lgierth··on Finland to propose that EU abolish daylight savings time
Portugal, UK, Ireland have been in UTC for ages.
lgierth··on Building for the Blockchain
Ah, thanks - you're half right :) The plan for Filecoin was initially (in 2014) to be based on Bitcoin, but since then this changed to its own Proof-of-Replication and Proof-of-Spacetime, reusing parts of Ethereum.

IPFS itself has never had any cryptocurrency integration, although there are external services that store your data on their IPFS nodes in exchange for Bitcoin.

(source: https://filecoin.io/blog/update-2017-q4/ and I'm on the IPFS team)

lgierth··on Building for the Blockchain
> To add to the baffle, IPFS started using bitcoin and ethereum for storing the initial peer data for new clients to connect to.

This is false. Where did you get that impression?

lgierth··on 120M American Households Exposed In 'Massive' ConsumerView Database Leak
Here's the report from UpGuard, who found the breach: https://www.upguard.com/breaches/cloud-leak-alteryx

It has more detailed information about the dataset.

lgierth··on Ask HN: Is a P2P browser possible?
> There's also IPFS which is a network of static, hash-addressed content

There's means for dynamic content too: IPNS and Pubsub, the latter was on HN just 3 days ago: https://news.ycombinator.com/item?id=15879752

> However, note that the official client comes with "blocklists" which may be used for censorship

There's no blocklists in any of the IPFS clients and libraries at the moment. However there are plans for opt-in, community-maintained blocklists that'll allow communities to govern what content they allow.

lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
Sure -- but libp2p's network transports underneath are pluggable. There's already Websockets (/ws, think domain fronting! [1]) and Tor (/onion) transports, so there's various options for evading censorship (I personally consider bandwidth throttling a form of censorship).

[1] Domain fronting lets you use a well-established web frontend for your web service. E.g. we could host /ws nodes in Google Cloud, and to the ISP the TLS handshake looks like it's for google.com, while inside the connection there's e.g. a `Host: libp2p.googlecloud.com` header. More info: https://www.bamsoftware.com/papers/fronting/

But then again, net neutrality is a political issue! You don't solve it for good with technology.

lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
Yes that's the document in https://github.com/libp2p/research-pubsub/pull/17
lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
If you're looking for raw performance and/or large datasets, go-ipfs is for you. If you're​ looking for running within websites (and in browsers generally), then js-ipfs is for you.
lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
Pins are something that's per-node, and whether a node has a specific piece of content pinned is not visible publicly (only that it's providing the content).
lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
There's no blocking functionality in IPFS yet - the plan is to have customizable opt-in blocklists (and allowlists) for content and peers, though, so communities can govern themselves regarding what content is desired and what's not.
lgierth··on IPFS Pubsub: Distributed named pubsub channels based in the IPFS Cloud
Pubsub is probably one of the lesser known features of IPFS right now, given that it's still marked as experimental. We're researching more efficient tree-forming and message routing algorithms, but generally the interface is pretty stable by now. Pubsub is supported in both go-ipfs and js-ipfs.

A shining example of pubsub in use is PeerPad, a collaborative text editor exchanging CRDTs over IPFS/Pubsub: https://peerpad.net

lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
Not at all :) There's multiple important points about IPFS and I always forget at least one, so thanks :)
lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
> Back to my original points, I don't think it is about hosting the data. It's the location of the data. Eg, a room full of people downloading a large video don't need to leave the room for the majority of the data, they can share the data between each other - seamlessly. Leading to less clogging of the network of data when there's absolutely no need for us to be downloading from youtube/etc.

You're absolutely right here of course

lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
Works with IPFS if you use Pubsub, cryptographic capabilities, and CRDTs :) Check out PeerPad: https://peerpad.net

edit: what I also meant to say is, a chat room doesn't need computation (although there certainly use cases that do)

lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
> A crappy computer, no; a crappy server, yes. The available network is part of a server. A URL that points to a machine that can't be accessed whenever the owner goes into a tunnel, is a URL nobody will link to.

This is one of the very points that IPFS tries to address: decoupling content from location, so that additional copies of the same content in different locations of the network can actually strengthen the content's availability, instead of being non-addressable and thus wasted.

lgierth··on Git hash function transition plan
> Generally, and this is just my gut feeling, I think that for any hash code written to disk or stored in some way having an identifier for the hashing algorithm used is such a common bite you in the ass later thing that it makes sense to always just do it from day one. To that end it’s easier to do day one if everyone agrees to a standard set of numeric codes.

Yes, that's the basic idea of all multiformats: "it's never gonna change" is considered harmful.

> Unifying here might allow git objects to be served natively over IPFS.

IPFS can already do that thanks to the CID format: https://github.com/ipld/cid

There's no good examples for Git specifically yet, but there's a good bunch of working code for transporting e.g. Ethereum and Zcash transaction blobs over IPFS. For Git it's in principle the same: import the raw object into IPFS, and starts addressing it with /ipfs/<git-cid><original-git-hash>

lgierth··on Git hash function transition plan
You can lock it down to specific hash functions no problem.
lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
No, it's more generally about hosting any content-addressed data. That's much much more than files/directories, as S3/Dropbox/Sia are doing.

Files and directories are just one particular data structure you can store on IPFS. Think of it as a global unified content-addressed graph database really, and Filecoin can store any arbitrary (sub)graphs within that.

lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
@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)
lgierth··on Is Filecoin a $257 million Ponzi scheme? [pdf]
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 problem. @jbenet did a great in-depth podcast with YC: https://blog.ycombinator.com/ipfs-coinlist-and-the-filecoin-... (transcript included)
lgierth··on Tutorial: Building a collaborative text editor over IPFS with Yjs in 10 minutes
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/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6...

- http://localhost:8080/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW...

And with the ipfs-companion browser extension:

- dweb:/ipns/peerpad.net

- dweb:/ipfs/QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD

- ipns://peerpad.net

- ipfs://QmXhnaUzhiZ6EGvr2SwPgSZzVhfsTnzTW5EsXH6TNnQcYD

Or by grabbing it using `ipfs get /ipns/peerpad.net` and clicking the html file in the resulting directory.

lgierth··on Tutorial: Building a collaborative text editor over IPFS with Yjs in 10 minutes
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://news.ycombinator.com/item?id=15624158

lgierth··on The sequence 1 1 ∞ 5 6 3 3 3
CRDTs! https://ipfs.io/blog/30-js-ipfs-crdts.md
← PreviousPage 4 of 10Next →