"especially when bandwidth rates for small players start around $0.12 per gigabyte" - who the heck is paying $0.12/gb?!
Neocities is implementing IPFS – distributed, permanent web
161–170 of 249 posts
Re: Neocities is implementing IPFS – distributed, permanent web
#162Earlier quoted context omitted.
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?
The upside is less battery drain from long-distance data connections. But yes, it's not a panacea.
Re: Neocities is implementing IPFS – distributed, permanent web
#163This 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…
1. Don't use it for what's basically messaging
2. I thought torrents can work decentralized e.g. using magnet links and DHTs.
Re: Neocities is implementing IPFS – distributed, permanent web
#164This 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…
I concur.
On principle, they could let the centralized server propagate the information that the file was updated. They could convert IPFS to a mere cache sharing system between browsers that are close by.
Re: Neocities is implementing IPFS – distributed, permanent web
#165Earlier quoted context omitted.
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.
Interesting. The ads problem is what i meant with 'mixing in readability' by using techniques to reducing a page to its core content. Only text paragraphs from blogs, images from flickr/imgur albums, audio/video from media sites, etc.
Re: Neocities is implementing IPFS – distributed, permanent web
#166You might also want to take note of the browser addons for firefox[1] and chrome[2].
Those redirect requests to public gateways (http://(gateway.)ipfs.ip/ipfs/$path) to the http server of the local ipfs daemon. It fetches the content using bitswap protocol and makes it in turn available to other nodes, helping with the distribution.
[1] - https://github.com/lidel/ipfs-firefox-addon [2] - https://github.com/dylanPowers/ipfs-chrome-extension
Re: Neocities is implementing IPFS – distributed, permanent web
#167This 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…
> uses bittorrent trackers to identify the nodes in the network
It's using a distributed hash table, not trackers. Nothing's completely decentralized; distributed hash tables are pretty good, since you can join them by talking to any participating node at all.
Re: Neocities is implementing IPFS – distributed, permanent web
#168"especially when bandwidth rates for small players start around $0.12 per gigabyte" - who the heck is paying $0.12/gb?!
More like 2€/TB
Re: Neocities is implementing IPFS – distributed, permanent web
#169Earlier quoted context omitted.
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?
A neat system might be, when the reciprocation system gets more advanced, to allow for nodes to build up a reputation/trust with other nodes while they're at home sitting on charge/wifi. Then, they can 'cash in' these brownie points when they're out and about, to download stuff without reuploading anything at the time.
There are a number of ways this reputation could be represented, perhaps one possible approach might involve exchanging some unit of cryptocurrency (Filecoin?), or perhaps a web-of-trust style system where nodes publicly 'trust' other nodes based on how much use that node was to them. Personally, I think cryptocurrency is the way to go here, but there's lots of work out there on P2P incentivization strategies.
Of course, this could work in tandem with the standard barter system that bittorrent uses, IPFS is not locked into any one reciprocation algorithm and could happily use multiple different systems depending on the situation.
Re: Neocities is implementing IPFS – distributed, permanent web
#170Earlier 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…
The reason why they get people to sign up at other people's pods is that it's easier to get users that way.
They are struggling to get users regardless and that is their biggest flaw.