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

61–70 of 154 posts

Re: IPFS Project Roadmap

#61

Post by viraptor »

fiatjaf wrote: post #50
fwip wrote: post #43

Earlier quoted context omitted.

You think somebody would do that? Just go on the internet and tell lies? Warning: image contains racial slurs and swastikas: https://i.imgur.com/0kdxzVR.png A little later in the chat, the developer chimes in and talks about some stuff. Then some people angrily accost them for censoring things. If the Nazis and the racists aren't censored, I don't want to think about the odious content that is. Edit: Here's a thread…

Well, to me these seem like some adolescents trying to be funny and go against the mainstream. They post swastikas and call racial slurs because they know they shouldn't be doing that. They aren't really nazis, right? They don't even know what a nazi is. You can call this "decentralized reddit" a bad place, as it really is, but you can't say it's because it's "full of right-wing people". These adolescents are not "ri…

> They aren't really nazis, right?

At some point... is there a difference? If you find yourself in a group "ironically" screaming you all support X for long enough, soon you'll find that some of you actually support X. And that you enabled those people.

Re: IPFS Project Roadmap

#62

Post by heyitsguay »

viraptor wrote: post #61
fiatjaf wrote: post #50

Earlier quoted context omitted.

Well, to me these seem like some adolescents trying to be funny and go against the mainstream. They post swastikas and call racial slurs because they know they shouldn't be doing that. They aren't really nazis, right? They don't even know what a nazi is. You can call this "decentralized reddit" a bad place, as it really is, but you can't say it's because it's "full of right-wing people". These adolescents are not "ri…

> They aren't really nazis, right? At some point... is there a difference? If you find yourself in a group "ironically" screaming you all support X for long enough, soon you'll find that some of you actually support X. And that you enabled those people.

Well and besides, the actual content on the site seems to skew alt-right pretty heavily, whether the racial slurs and swastikas are ironic or not. Taken altogether, it paints a pretty clear picture of a voat-style forum that will alienate most other people if it stays that way.

Re: IPFS Project Roadmap

#63

Post by paulsutter »

So I can store a file in ipfs by its hash, but there’s no way to link to the next version of the file. I can only link to older versions?

I’m a giant advocate for decentralized architectures but so far I’ve never found a use for it that doesn’t rely on a centralized way to find out about new data

Re: IPFS Project Roadmap

#64

Post by viraptor »

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…

> IPFS is a joke. They have name lookup feature but relies on traditional DNS!

This is not a criticism. That's describing a feature. Yes, they do have that. You could implement your own name resolution in a different way if you need that.

Re: IPFS Project Roadmap

#65

Post by johntash »

paulsutter wrote: post #63

So I can store a file in ipfs by its hash, but there’s no way to link to the next version of the file. I can only link to older versions? I’m a giant advocate for decentralized architectures but so far I’ve never found a use for it that doesn’t rely on a centralized way to find out about new data

I'm not super familiar with ipfs, but I _think_ ipns is supposed to solve that problem.

> Inter-Planetary Name System (IPNS) is a system for creating and updating mutable links to IPFS content. Since objects in IPFS are content-addressed, their address changes every time their content does. That’s useful for a variety of things, but it makes it hard to get the latest version of something.

https://docs.ipfs.io/guides/concepts/ipns/

Re: IPFS Project Roadmap

#66

Post by mirimir »

fwip wrote: post #30
tick_tock_tick wrote: post #28

Earlier quoted context omitted.

I doubt there will every be a way to delete content as every legitimate method of deleting will be commandeered for censorship. Even if they did add something you can never really know the other nodes actually deleted it.

Sometimes, censorship is good. For a silly example, if somebody somehow filled this comment section with images of goatse, it would be nice if we could take that down. I definitely agree from a technical level, you can't ever guarantee the deletion of files on somebody else's machine. So the question is, how do we build systems that enable users to protect their communities, without them becoming yet another tool for…

> For a silly example, if somebody somehow filled this comment section with images of goatse, it would be nice if we could take that down.

Or you could just not look at it.

Re: IPFS Project Roadmap

#67

Post by theamk »

georgyo wrote: post #35
hombre_fatal wrote: post #22

Earlier quoted context omitted.

One practical difference is that all the parts of a "collection" are individually addressable in IPFS. For example, unlike torrents, you can seed a collection like "My Web Show (All Seasons)" and add new files as new episodes become available. With torrents, you have to repackage them as new torrent files. IPFS also then encourages file canonicalization instead of everyone seeding their own copy of a file.

This is a over simplification I think. In IPFS to add a file to a folder, you need to rebuild that folder which changes the address. You still need to get people to access the new address to see any updates. IPNS makes that fairly easy, but a similar technology could be made for bittorrent. I think what makes IPFS interesting is that all files are like torrents and all folders all like torrents of torrents. And since…

In traditional torrents, the files are concatenated and only then divided into chunks. So if I take a existing torrent and add a single 16-byte file to the beginning, there is a good chance it will have no common hashes between new and old one.

Update: There is apparently "bittorrent V2" protocol [1][2], which allows file sharing. It is still not implemented in major clients, like libtorrent[3]

[1] http://bittorrent.org/beps/bep_0052.html

[2] https://news.ycombinator.com/item?id=14951728

[3] https://github.com/arvidn/libtorrent/issues/2197

Re: IPFS Project Roadmap

#68

Post by mirimir »

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, try to find these files that I uploaded a few years ago: https://ipfs.io/ipfs/QmUDV2KHrAgs84oUc7z9zQmZ3whx1NB6YDPv8ZR... and https://ipfs.io/ipfs/QmSp8p6d3Gxxq1mCVG85jFHMax8pSBzdAyBL2jZ.... As far as I can tell, they're just gone.

Re: IPFS Project Roadmap

#69

Post by mirimir »

cortesoft wrote: post #59
miguelrochefort wrote: post #56

Earlier quoted context omitted.

Data should never be deleted. Ever. Start by accepting that, and everything starts to make sense.

Child porn? Video of you in the bathroom that someone took from a hidden camera? Your stolen financial information?

Sure, of course.

But the problem is that if you can delete that stuff, someone else can delete stuff that you don't want to be deleted.

Re: IPFS Project Roadmap

#70

Post by [deleted] »

StavrosK wrote: post #36
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.

The IPFS client is such an untunable memory hog that I turn it off whenever I'm not using it (which, of course, defeats the entire purpose). I would be ecstatic if we had something like the old uTorrent, but for IPFS. A nice UI, easy configuration, an ultralight implementation. It would be a dream come true.

[deleted]
Post reply on HN