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

Neocities is implementing IPFS – distributed, permanent web

ipfs.io

Post reply on HN
Print view View original

121–130 of 249 posts

Re: Neocities is implementing IPFS – distributed, permanent web

#121

Post by chippy »

kardos wrote: post #118
niklasni1 wrote: post #113

Earlier quoted context omitted.

If somebody put something online fifteen years ago, they might not care about it anymore, but I might. With the current web, I can mirror that content by downloading it and putting it on a new server. With this system, that process would be part of the basic workings of the system.

Sounds somewhat like bittorrent.... as long as there is a "seed" then the content is available, but it falls apart when the last seeder disconnects. ... and it also sounds like usenet, but here everybody is a news server and they selectively host articles.

With bittorrent you could make a call in a public forum for more seeds for a file. And if people have a copy of that particular content they can reseed.

I wonder if this would also be possible in this case?

For example, my small server might serve 200 sites but I'll backup around 500 or so older ones somewhere else.

Re: Neocities is implementing IPFS – distributed, permanent web

#122

Post by wodenokoto »

crypt0x wrote: post #116
wodenokoto wrote: post #98

This reminds me of a feature I sorely miss on my blog (and almost every other blog I visit!) which is for the blogging engine to automatically take a snap-shop of webpages you link to and let users read the cached version at will. If I link to a page and it goes down, or the content changes, it in a way changes the content of my blog too - in an unwanted way that is!

This! I already thought about starting a project for a local browser proxy that builds an index of => $snapshotHash as I go. Maybe mixin readability and metadata like referrals. I find it quite belittling how browser vendors treat their history features in terms of archival.

Zotoro saves snapshots, although it is for scientific references (citation manager). Due to ads and what not, it will balloon in size surprisingly fast.

Re: Neocities is implementing IPFS – distributed, permanent web

#123

Post by emilburzo »

But what happens if mobile devices will become the norm instead of PCs?

The number of hosters will be far less than the number of clients.

The same issue is now in bitcoin, lots of lightweight clients (that don't keep a full ledger), and not so many full nodes (probably even less after mining rewards will be zero).

Re: Neocities is implementing IPFS – distributed, permanent web

#124

Post by adam12 »

emilburzo wrote: post #123

But what happens if mobile devices will become the norm instead of PCs? The number of hosters will be far less than the number of clients. The same issue is now in bitcoin, lots of lightweight clients (that don't keep a full ledger), and not so many full nodes (probably even less after mining rewards will be zero).

Mobile devices are getting increasingly powerful, so by the time this is implemented (and when/if it becomes popular) it probably won't be an issue.

Re: Neocities is implementing IPFS – distributed, permanent web

#125

Post by laumars »

sdoering wrote: post #79
_prometheus wrote: post #20

Earlier quoted context omitted.

Two pieces of (coming soon) good news: - very soon, you wont need to install anything to use IPFS. it will "just work" with js on today's browsers. - for best perf, yes, we need browser implementations. and... those have begun :)

OK, as apparently .js is the defacto thing to build cool sites, I for one will be left out here. On sites not known to me, I typically block most (read all) .js at first, just to make sure that these sites do not leak too much information about me to external tracking tools, advertisers or the like. So using .js seems to me a bit problematic in regards of people not enabling it by default (but this is an absolut mino…

I use a custom hosts file (well, technically I run it as an internal DNS server) from Someone Who Cares to block most of the aforementioned annoyances: http://someonewhocares.org/hosts/

It works very well for me so I'd recommend it to others, if they're not already aware of it.

Re: Neocities is implementing IPFS – distributed, permanent web

#126

Post by david_ar »

emilburzo wrote: post #123

But what happens if mobile devices will become the norm instead of PCs? The number of hosters will be far less than the number of clients. The same issue is now in bitcoin, lots of lightweight clients (that don't keep a full ledger), and not so many full nodes (probably even less after mining rewards will be zero).

On the other side of the coin, I'd say mobile clients offer more opportunities for local p2p distribution (Bluetooth, etc)

Re: Neocities is implementing IPFS – distributed, permanent web

#127

Post by viraptor »

crypt0x wrote: post #104
viraptor wrote: post #66

Earlier quoted context omitted.

I love the person who made it. It's exactly what I needed.

thanks :) if you find any issue - let me know

I'm assuming that once ipns starts to work reliably you'll add the support for it? Or is there something that would prevent it? (I mean for single-user repo anyway - multi-user would have to share the key... somehow)

Re: Neocities is implementing IPFS – distributed, permanent web

#128

Post by enkiv2 »

Just to point out -- hypertext systems prior to the web almost universally expected permanent stable addresses (and this was, for instance, required by the various Xanadu specs). Enquire (Tim Berners-Lee's immediate predecessor to the Web) had permanent stable addresses, too.

The web didn't have permanent stable addresses because the web was a hack, intended as a way to explain Enquire to people who didn't have a background in real hypertext systems. (Let the entire existence of the Web, with its myriad flaws, be a lesson to you: your crappiest demo may well become the thing you're known for twenty-five years later, so make sure your crappiest demo doesn't suck as bad as the Web does.)

Re: Neocities is implementing IPFS – distributed, permanent web

#129

Post by david_ar »

chipsy wrote: post #85
adrusi wrote: post #30

Earlier quoted context omitted.

With IPNS, which allows the creation of links whose destination can be mutated by whoever has the private key, you can implement quite a lot of interactivity. You won't ever be able to implement facebook over this platform, but you can replicate all of its functionality by using a tumblog-like architecture. Facebook's design is inherently centralized, and therefore doesn't really fit into the world of IPFS. The idea…

I'm thinking about the discovery problem and how this relates to distributed technology now. File storage looks solved but creating content relationships like lists of similar files sounds much harder and still reliant on a authority that curates and filters the spam. Lost data in IPFS will be "buried treasure" in that nobody has the link to it anymore, but it still exists in a literal sense. Interesting to think abo…

There are plans for a (distributed) search engine: https://github.com/ipfs/archives/issues/8

Re: Neocities is implementing IPFS – distributed, permanent web

#130

Post by tropin »

laumars wrote: post #125
sdoering wrote: post #79

Earlier quoted context omitted.

OK, as apparently .js is the defacto thing to build cool sites, I for one will be left out here. On sites not known to me, I typically block most (read all) .js at first, just to make sure that these sites do not leak too much information about me to external tracking tools, advertisers or the like. So using .js seems to me a bit problematic in regards of people not enabling it by default (but this is an absolut mino…

I use a custom hosts file (well, technically I run it as an internal DNS server) from Someone Who Cares to block most of the aforementioned annoyances: http://someonewhocares.org/hosts/ It works very well for me so I'd recommend it to others, if they're not already aware of it.

I've always wondered if Windows or other operative systems read the entire hosts file everytime they want to resolve an address. Maybe a big hosts file is bad for network performance?
Post reply on HN