On the path towards creating a network that does not depend on centralized entities, making sure the content you post online lives on a peer-to-peer network is an important step.

Every post you make in HyperSpace gets hosted on a decentralized cloud, forever available and retrievable regardless of the status of HyperSpace. For this purpose, we’re using IPFS, and have created a solution combining the best of both centralized and decentralized worlds.

Let’s walk through an example to understand how this works:

You make a post on HyperSpace. Hurray! https://alpha.hyperspace.app/post/5c180cb0ab000700064cce13 The post gets uploaded to HyperSpace’s centralized server as well as to HyperSpace’s IPFS node. https://file.hyperspace.app/ipfs/QmQcRcrjNCmo6mWB3gomsvBgYikdQBMwiPt6dbbWKJi6BS The post gets disseminated to other IPFS nodes and becomes retrievable from the cloud — from outside, and regardless, of HyperSpace. https://gateway.ipfs.io/ipfs/QmQcRcrjNCmo6mWB3gomsvBgYikdQBMwiPt6dbbWKJi6BS ^^ Kind of slow, isn’t it? That’s why when you do browse through HyperSpace.app, your content is quickly retrieved from our standard centralized server. As long as decentralized hosting isn’t robust enough to serve pages quickly and reliably, we’ll continue relying on this standard method to serve our users — while beginning to seed the cloud and making your content untakedownable.

To see your post’s IPFS hash, click the “…” found next to every post on HyperSpace.

As we develop, more and more features related to the content will be migrated such that they’re available outside of HyperSpace; Amplifications, referrals, AMP allocation, and so on, to create a complete decentralized experience.

Read more