Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IPFS Project Roadmap

github.com

Post reply on HN
Print view View original

91–100 of 154 posts

Re: IPFS Project Roadmap

#91

Post by int_19h »

fwip wrote: post #24
marknadal wrote: post #13

Earlier quoted context omitted.

For dynamic data, you need to use a CRDT system like GUN ( https://github.com/amark/gun ). For instance, see P2P Reddit ( http://notabug.io ) which: - Running in production with GUN. - Handling about 42,000 monthly visitors. ( https://www.similarweb.com/website/notabug.io ) - Has done ~1TB in 1 day of decentralized traffic. You can then configure GUN to save to IPFS as the blob/storage engine (or we have filesystem,…

It's a shame that so many P2P advocates - or at least the ones using the stuff built with P2P tech - are very loud alt-right types. I popped on notabug.io just now, and the chat is full of swastikas, racial slurs, and the most up-voted posts are primarily anti-gay misinformation. I see you wrote GUN, which I'm sure was no small feat, and it looks like an impressive piece of technology. How do you feel about your tech…

This is true of pretty much any tech that is anti-censorship in some way or another (anonymizing and/or decentralized).

But it's hardly surprising:

"The trouble with fighting for human freedom is that one spends most of one's time defending scoundrels. For it is against scoundrels that oppressive laws are first aimed, and oppression must be stopped at the beginning if it is to be stopped at all."

In this case, it means that you'll see people who are predominantly censored from other places already use this tech to avoid further censorship. In US right now, at least, that tends to be alt-right, white nationalists etc. For a more detailed take:

https://slatestarcodex.com/2015/07/22/freedom-on-the-central...

Re: IPFS Project Roadmap

#92

Post by int_19h »

Razengan wrote: post #17
robto wrote: post #5

Earlier quoted context omitted.

That's what's got me excited - they've managed to articulate a vision for the future that I'm totally on board with: decentralized, privacy respecting, and user owned. I really want to see that vision become a reality.

For the internet to be truly decentralized, it needs to be so at the physical connectivity layer as well. Perhaps a worldwide swarm of drones creating a mesh network.

I wonder how much Broadband-HamNet could scale in practice.

Re: IPFS Project Roadmap

#93

Post by StreamBright »

viksit wrote: post #26

One of the biggest challenges with IPFS in my mind is the lack of a story around how to delete content. There may be a variety of reasons to delete things, - Old packages that you simply don't want to version (think npm or pip) - Content that is pirated or proprietary or offensive that needs to be removed from the system But in its current avatar, there isn't an easy way for you to delete data from other people's IPF…

Just watch how fast warez people will start to use IPFS to host all seasons and all episodes of Friends.

Re: IPFS Project Roadmap

#94

Post by StreamBright »

Risord wrote: post #31
viksit wrote: post #26

One of the biggest challenges with IPFS in my mind is the lack of a story around how to delete content. There may be a variety of reasons to delete things, - Old packages that you simply don't want to version (think npm or pip) - Content that is pirated or proprietary or offensive that needs to be removed from the system But in its current avatar, there isn't an easy way for you to delete data from other people's IPF…

Managing universal data removal is not universally solved (or even wanted) on internet scale. So it sounds weird to demand it from technology which is trying to solve completely different problem.

The same argument applies to self-driving cars, crashing into objects on the road is not a problem because they are trying to solve an entirely different problem.

Re: IPFS Project Roadmap

#95

Post by StreamBright »

ezoe wrote: post #54

IPFS is a joke. They have name lookup feature but relies on traditional DNS! What are they thinking? Also, if the IPFS's idea of working as local server is sound, BitTorrent DNA(browser plugin, steaming video over BitTorrent) should had been worked. It seems to me, they suffered NIH syndrome. They tried to reinvent the wheel. The P2P file transfer protocol over IP has already been covered by BitTorrent. What we need…

On the top of that when you ask them about it the answer usually is:

- but this is decentralized

- it is not a bug|lack of implementation but a feature

Re: IPFS Project Roadmap

#96

Post by antpls »

mirimir wrote: post #68
viksit wrote: post #26

One of the biggest challenges with IPFS in my mind is the lack of a story around how to delete content. There may be a variety of reasons to delete things, - Old packages that you simply don't want to version (think npm or pip) - Content that is pirated or proprietary or offensive that needs to be removed from the system But in its current avatar, there isn't an easy way for you to delete data from other people's IPF…

> But in its current avatar, there isn't an easy way for you to delete data from other people's IPFS hosts in case they choose to host your data. If you put it on IPFS, it's not "your data" any longer. If that doesn't work for you, then don't use IFPS. Edit: I do get why people are concerned about persistence of bad stuff. But it's not at all unique to IPFS. And even IPFS forgets stuff that nobody is serving. I mean,…

If IPFS becomes famous to the point governments have to look at it, and that it allows to bypass laws, they will try to forbid by law people to run nodes, same way with Tor in some countries.

Re: IPFS Project Roadmap

#97

Post by zrm »

viksit wrote: post #26

One of the biggest challenges with IPFS in my mind is the lack of a story around how to delete content. There may be a variety of reasons to delete things, - Old packages that you simply don't want to version (think npm or pip) - Content that is pirated or proprietary or offensive that needs to be removed from the system But in its current avatar, there isn't an easy way for you to delete data from other people's IPF…

> One of the biggest challenges with IPFS in my mind is the lack of a story around how to delete content.

"One of the biggest challenges with [HTTP|ZFS|TLS|USB|ATX|VHS|USPS] in my mind is the lack of a story around how to delete content."

If you delete your copy of some data, someone else may still have theirs, but then it's them who controls whether to delete it. It's not a challenge for Serial ATA that it doesn't have a function to delete certain data from every hard drive in the world at the same time. Most systems don't work that way, not least because it's inherently dangerous.

Re: IPFS Project Roadmap

#98

Post by gritzko »

fwip wrote: post #18

"2019 Goal: The most used code and binary Package Managers are powered by IPFS." That's kind of stupid-ambitious for 2019 when another 2019 goal is "a production-ready implementation" and IPFS has been around for 3 years already. This isn't a roadmap, it's a wishlist. And I'm someone who wants to see IPFS succeed.

In theory, there are incremental paths to achieve that objective, while serving clients all the way along.

1. Define a P2P ready data model and protocol (which they have, Merkle forest and everything)

2. Run a single server/cluster, make a very lightweight client library for that

3. Expand the server to a makeshift CDN (start simple, e.g. rsync like mirrors)

4. Federate the CDN (still in a hierarchical fashion, so you always know whom you are talking to). Also, look for peers on the local subnet (broadcast is simple).

5. Expand that to a friend-of-a-friend network, use PEX like peer finding (PEX is shockingly simple https://en.m.wikipedia.org/wiki/Peer_exchange)

6. Go full P2P, talk to strangers on the Net, use DHT or anything.

The only trick is to start with a data model that can go all the way to (6). So backward compatibility/ installed base issues do not stop you at earlier stages. Think globally, act locally.

The dangerous thing is deploying an untested complex codebase to serve the most hardcore use case for live customers on Day#1. That may not work. Because even all these shockingly simple steps will turn quite long and tedious in practice. There will be "issues". Advancing one step a year is quite impressive if done under the full load.

Re: IPFS Project Roadmap

#99

Post by feanaro »

antpls wrote: post #96
mirimir wrote: post #68

Earlier quoted context omitted.

> But in its current avatar, there isn't an easy way for you to delete data from other people's IPFS hosts in case they choose to host your data. If you put it on IPFS, it's not "your data" any longer. If that doesn't work for you, then don't use IFPS. Edit: I do get why people are concerned about persistence of bad stuff. But it's not at all unique to IPFS. And even IPFS forgets stuff that nobody is serving. I mean,…

If IPFS becomes famous to the point governments have to look at it, and that it allows to bypass laws, they will try to forbid by law people to run nodes, same way with Tor in some countries.

Try and succeed are different things. The larger the use case set, the tighter the integration with everything else, the stronger the reliance on it, the harder it will be to outlaw it. Often the laws drift ever-so-slightly to accommodate the new reality.

Re: IPFS Project Roadmap

#100

Post by posnet »

anandology wrote: post #57

In addition to apt and npm, I would like to see docker image distribution powered by IPFS. It really feels stupid to pull images from a central registry sitting on the other side of the globe when the image is already present in the next node in your kubernetes cluster.

If it's for your own cluster, uber open sourced a docker p2p registry explicitly for use with clusters.

https://eng.uber.com/introducing-kraken/

Post reply on HN