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

151–160 of 249 posts

Re: Neocities is implementing IPFS – distributed, permanent web

#151

Post by ianopolous »

junto wrote: post #117
colordrops wrote: post #74

Earlier quoted context omitted.

> Facebook's design is inherently centralized Not really. There's no reason you couldn't implement Facebook's core functionality with personal servers containing a profile at each node and a pub/sub (or even just pull) system connecting each node with its friends.

Actually, this is exactly what I'm looking for. I want to be able to control my photos and other content, and share that with family and friends. All data is encrypted and my server can be hosted anywhere (just as simple as setting up a WordPress instance). My own "news feed" are a combination of all of the other nodes I'm subscribed to. My problem with Disapora is that they push the "sign up to someone else's pod" r…

We're heading towards this with Peergos (https://peergos.org source at https://github.com/ianopolous/Peergos). Encrypted, self-hostable file storage, sharing and social network. We're considering using IPFS under the hood for fragment storage/finding. You'll be able to either use your own disk, or enter credentials for a cloud provider. It's still very early days yet though.

Re: Neocities is implementing IPFS – distributed, permanent web

#152

Post by crypt0x »

viraptor wrote: post #127
crypt0x wrote: post #104

Earlier quoted context omitted.

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)

Right, that's the idea.

Nothing is technically stopping me from adding ipns except finding the time to do it.

Re: Neocities is implementing IPFS – distributed, permanent web

#154

Post by qznc »

adam12 wrote: post #124
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.

Batteries and power will most certainly be an issue for mobile devices.

Re: Neocities is implementing IPFS – distributed, permanent web

#155

Post by anc84 »

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!

A plugin that makes archive.org and archive.today save a snapshot would be ace. I would give (measly, sorry) 20$ if someone goes to crowdfund this as wordpress plugin.

Re: Neocities is implementing IPFS – distributed, permanent web

#156

Post by emilburzo »

david_ar wrote: post #126
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)

So even more battery drain?

I mean indeed local p2p distribution sounds nice, but what's the use if the device is dead in a few hours?

Re: Neocities is implementing IPFS – distributed, permanent web

#157

Post by kang »

This sounded like many of the bitcoin projects, specially filecoin and upon reading further I came to know it is by the same guys.

Similar projects have been in development for past few years such as https://github.com/feross/webtorrent and zeronet

This has same problems as the bitcoin infrastructure though:

1. It is unscalable. A page built on IPFS receiving huge inflow of comments would generate many diffs quickly and as soon as they spread in the network they get outdated, thereby clogging space on people's disks but more importantly clogging the bandwidth where nodes compete to download the quickly changing diffs.

2. This is not completely decentralised because it uses bittorrent trackers to identify the nodes in the network. Taking down the the trackers would take down the system as well.

Webtorrent is an already working, fast, alternative to IPFS but still centralised. Think of it this way, can you do a pure peer-to-peer webrtc site without needing a ICE/TURN/STUN server? Peer discovery is the centralised part of the problem.

Re: Neocities is implementing IPFS – distributed, permanent web

#158

Post by fizzbatter »

I love IPFS, the team has done an amazing job with the implementation. As much as i love it though, i can't help but feel https://morph.is/ 's technology of a Targetted Block is required for the web. I know that is outside of IPFS' specific scope, but is that something any of the IPFS/IPNS/IPN developers are thinking of?

Being able to push data to a target seems to be a tool that will empower real change - not just solve a technical problem (HTTP failings).

Thoughts?

Re: Neocities is implementing IPFS – distributed, permanent web

#159

Post by arethuza »

enkiv2 wrote: post #128

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 bac…

I've been using the Web since late '92 and evaluated and selected the Web for a project in '93 where I looked at other hypertext tools.

If the Web was a hack then the world could be doing with more hacks.

Re: Neocities is implementing IPFS – distributed, permanent web

#160

Post by dsr_ »

tropin wrote: post #130
laumars wrote: post #125

Earlier quoted context omitted.

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?

It will largely be read out of memory, since it doesn't change much and is frequently requested. Scanning 64K or so won't break a sweat compared to doing a DNS lookup across the network to a resolver that might itself need to make a request.
Post reply on HN