Zeronet: How is this different from IPFS?

[Porco-Rosso]

Hi, As i understand this project is a combination of bittorent decentralised technology and bitcoin-like crypto to serve web pages.
How is this different from https://github.com/ipfs/ipfs/ where both of these technologies are already implemented?
Apart from TOR compatibility, every feature of ZeroNet is already implemented in IPFS. Am I wrong? could you share some light on this?

[HelloZeroNet]

IPFS does not support dynamic content as far as I know and the content distribution works differently. There is lots of similar project out there ZeroNet created to focus on simplicity, easy of usage and user experience.

[JayBrown]

From what the IPFS developers said, IPFS does support dynamic content. As for TOR or VPN etc., IPFS works flawlessly on top of that, as ZeroNet does.

[weakish]

From what the IPFS developers said, IPFS does support dynamic content.

You can _distribute_ dynamic content via IPFS.
You need to write your own JavaScript script to call ipfs to publish dynamic content.
There is no built-in support for basic features like forum and comment.
ZeroNet is full stack dynamic, but IPFS only provides the backend (storage) of dynamic site.
For now, static sites with a lot of files, use IPFS.
Dynamic sites like forum or ZeroMe, use ZeroNet.
Small static site, use either.

[alugarius]

i use ipfs for everything, zeronet is cool but it is slow on boot

[HelloZeroNet]

The startup speed zeronet has been fixed, please check the blog for instructions