4 ms·

You can host the UI wherever you want. You can put it on IPFS, you can broadcast it as a bittorrent, you can put it on Github, you can put it in a pastebin, you

by shazow 9y ago

You can host the UI wherever you want. You can put it on IPFS, you can broadcast it as a bittorrent, you can put it on Github, you can put it in a pastebin, you can even put it on the blockchain. A lot of developers choose to have a replica hosted on traditional HTTP for easy onboarding, but the point is that the application itself can be completely decoupled from the developer. Even if the developer hosts their app on their own domain, there is nothing stopping you from forking it and replicating/hosting it elsewhere. It's like the ultimate extreme of open source, but also applied to APIs that can't be taken away. For example, you can launch a smart contract which hard-codes an IPFS hash to a GUI that can never be changed, even if the original owner wanted to. It's more about what can be done, rather than what is being done today. The possibilities are inspiring and attractive.

sargun 9y ago
But, if you put it on IPFS, what hosts the wallet, and wallet API? Also, last I checked, IPFS is not censorship resistant: https://github.com/ipfs/faq/issues/36#issuecomment-140567411 https://github.com/ipfs/faq/issues/36#issuecomment-140567411
- shazow 9y ago
  > But, if you put it on IPFS, what hosts the wallet, and wallet API? Which wallet? You can use whatever wallet you want which supports the functionality the DApp requires. There are dozens of wallets, some are in-browser. > Also, last I checked, IPFS is not censorship resistant: https://github.com/ipfs/faq/issues/36#issuecomment-140567411 https://github.com/ipfs/faq/issues/36#issuecomment-140567411 While I didn't mention anything about censorship, I suggest reading that entire thread and its continuation. All it discusses is the ability to have curated blocklists. It's up to you whether you want to use them or not. What I did mention is that you don't have to use any specific replication protocol. Don't like IPFS? Use something else. If you did want to use IPFS and you're concerned about censorship, then consider that IPFS is a distributed hash table protocol with some default client rules. If you don't use their default bootstrapping nodes, you can create your own IPFS network. In fact, IPFS is totally usable in an isolated local network, or even over a sneaker net.

by shazow 9y ago

sargun 9y ago

But, if you put it on IPFS, what hosts the wallet, and wallet API? Also, last I checked, IPFS is not censorship resistant: https://github.com/ipfs/faq/issues/36#issuecomment-140567411 https://github.com/ipfs/faq/issues/36#issuecomment-140567411

shazow 9y ago
> But, if you put it on IPFS, what hosts the wallet, and wallet API? Which wallet? You can use whatever wallet you want which supports the functionality the DApp requires. There are dozens of wallets, some are in-browser. > Also, last I checked, IPFS is not censorship resistant: https://github.com/ipfs/faq/issues/36#issuecomment-140567411 https://github.com/ipfs/faq/issues/36#issuecomment-140567411 While I didn't mention anything about censorship, I suggest reading that entire thread and its continuation. All it discusses is the ability to have curated blocklists. It's up to you whether you want to use them or not. What I did mention is that you don't have to use any specific replication protocol. Don't like IPFS? Use something else. If you did want to use IPFS and you're concerned about censorship, then consider that IPFS is a distributed hash table protocol with some default client rules. If you don't use their default bootstrapping nodes, you can create your own IPFS network. In fact, IPFS is totally usable in an isolated local network, or even over a sneaker net.