Migration to IPFS

Beyond the technical challenge, what's the interest for the D* community?

ull "">

The obvious outcome is that, ideally, the Diaspora network would no longer need to rely on shared pods. If the community has no interest in the idea, I'm sure there will be others to come along and take up the torch. I just thought of Diaspora because IPFS seems to be the answer the biggest hurdle of getting people to join--i.e. explaining what a pod is and getting them to sign up to an individual pod.

No longer would individual servers need uptime tracked, or separate URLs. You could potentially keep all of your personal data locally; pinning it to IPFS to share with the network.

There are concerns with control over data after its been shared over the protocol, but that problem is also true of current protocols. The project is currently working on finding ways of giving more control to users in that regard.

Isn't there a problem with dynamic website and IPFS? I thought it was good for static website and data (maybe it has changed since I last checked).

Edit: I thought you were proposing IPFS in order to store user data like the photo albums (which would have been a privacy problem, I think)..

ull "">

Dynamic in reference to content, or dynamic in reference to naming system?

Edit: I think it depends on how and what gets moved to the IPFS protocol. It also depends on how you define privacy risk. Multiple computers already access photo albums on Diaspora over HTTP right now.

ull "">

See https://alexandria.io for one website which has built itself on top of IPFS to distribute dynamic media (video, audio, etc.).

Dynamic in reference to content. I'll check alexandria! Thx

This is also relevant.

http://akasha.world/