> Cryptocurency integration and identity within IPFS could have been done without a new coin
I don't think thats a fair claim to make. There are many attacks on 'pay for distributed storage' that Filecoin addresses. Take a look at [the paper](https://filecoin.io/filecoin.pdf), in particular section 3.1 where we discuss sybil attacks, Outsourcing attacks, and generation attacks. We cover a lot of cases, and build in incentives to continually increase the amount of available storage and push down the price-per-byte. If we thought it was possible to properly incentivize data storage on ipfs without building a blockchain, we would have done so.
Because IPFS uses a distributed hash table like Bittorent, you don't have to know where stuff is--that's the problem with the HTTP, which is location addressed. IPFS is content addressed—the hash is the location.
You never host anything unless you want to; you don't host random stuff.
It's 2017, if you're using Google Docs or an instant messenger program and lose access to the backbone, you can't communicate with somebody who's in the same room with you. That's kinda silly. IPFS solves that issue.
IPFS is censorship resistance because it's a distributed protocol that can use a variety of transports. If I run example.com, people can DDOS it; it's much harder to do that when hundreds or thousands of nodes have the same content and you can connect to any of them. Sure worked in Turkey: http://observer.com/2017/05/turkey-wikipedia-ipfs/.
Filecoin is a cryptocurrency that will be mined by providing storage via IPFS.
Folks may want to read the white paper before they make assumptions about what's possible and what's hype: https://filecoin.io/filecoin.pdf