Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I've been following the development of IPFS for the last few years and I'm getting the impression that it's fizzling out. Maybe Protocol Labs are working on Filecoin now (that's what's bringing them money), but they never really finished the pubsub implementation and js-ipfs still can't run in the browser because there is no IPFS network that communicates using WebSockets and not TCP/UDP.


> they never really finished the pubsub implementation and js-ipfs still can't run in the browser because there is no IPFS network that communicates using WebSockets and not TCP/UDP

I don't believe the pub/sub is critical functionality (progress at [0], but it's really just chatty). Progress of that additional feature should not be a measuring stick for the project as a whole. For js-ipfs, I see work being done frequently, e.g. the DHT work[1] and weekly syncs[2]. I agree work is slow, but I am not getting the impression it is fizzing out.

Having said that, I think there are fundamental problems with the ideas behind it. I want MaidSafe's ideas and IPFS's completion/MVP schedule. IPFS doesn't bring enough anonymity or forced, equitable, encrypted block sharing IMO (I am aware of efforts on both fronts of course).

0 - https://github.com/ipfs/notes/issues/64

1 - https://github.com/ipfs/js-ipfs/pull/856

2 - https://github.com/ipfs/js-ipfs/issues/1179


I find that unlikely. They got 250 MUSD quite recently and they need IPFS working if they want filecoin to work.


They already got 250M USD. Why do they need to get Filecoin to work?

The easiest and least stressful outcome is to drag it along forever while paying themselves giant executive salaries from that stash. As long as there’s some minimal progress, it’s not fraud.


I understand that it's fashionable to be cynical about ICOs. However the IPFS people have clearly been working their asses off writing solid software and giving it to us for free, for several years now. All along they've been talking about their plan for filecoin.

With that track record, the burden is on you to explain why you think they will suddenly throw all that away, and stop working on a project they're so clearly passionate about, ruining their reputation in the process.


With a track record of major ICO success, they could easily start a fund or raise money for the next venture — regardless of what happens to Filecoin.

Convincing people to give up $250 million is the part that built their reputation and ensures lucrative deals will be coming their way. Whether they’re passionate about some storage-sharing token is neither here nor there.


You're absolutely right. All human beings are selfish monsters and are motivated by money more than anything good. And that of course includes you yourself.


What’s good about Filecoin? It’s not like it would benefit humanity somehow. You make it sound like I’m criticizing Doctors Without Borders here, rather than a clunky S3 alternative.


Please take your cynicism somewhere else.


Cynicism about overhyped technology projects isn't welcome on HN anymore? Now that's quite a change.


Isn't filecoin built on top of IPFS?


Yes, it is, but Filecoin is not live (yet).


Sure. My point was they're unlikely to abandon IPFS since it's a core component of Filecoin.


Wait, what?

js-ipfs runs in the browser just fine. See https://filemap.xyz/.


Only some features work in the browser. Notably DHT and relaying does not. See the repository's "Please read this" at https://github.com/ipfs/js-ipfs/#project-status


An in-browser DHT cannot be created until until we can have something that's analogous to opening a port in the browser.

For a DHT to work, you need to be able to able to connect to be discoverable and be able to connect to multiple peers.

WebRTC unfortunately doesn't allow for this yet.


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




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: