1. Centralized bootstrapping: you must rely on a centralized set of nodes to connect into the network. 2. No user-server model: users are forced to spin up a server to browse their decentralized web. You can’t even turn a file into a merkle tree without being forced to spin up an IPFS blockstore server. 3. Their Merkle Trees/DAGs are not optimized for downloading one branch at a time, because you must download a list of all children hashes when downloading any parent hashes — creating excessively bloated merkle branches.

1. Centralized bootstrapping: you must rely on a centralized set of nodes to connect into the network. 2. No user-server model: users are forced to spin up a server to browse their decentralized web. You can’t even turn a file into a merkle tree without being forced to spin up an IPFS blockstore server. 3. Their Merkle Trees/DAGs are not optimized for downloading one branch at a time, because you must download a list of all children hashes when downloading any parent hashes — creating excessively bloated merkle branches. We’ve invented a new type of Merkle Tree/DAG that has the ability to map file directories like IPFS Merkle DAGs, and maintains the small branches of Merkle Trees for quick user validation. This achievement may help projects independently of Nostr.

Hmm. I believe you have the ability to specify bootstrap servers. And my understanding is that IPFS is more of a foundational protocol on which to build services that can offer a user-server model (like

Storacha - Decentralized Hot Storage Layer on Filecoin

Storacha - Super Hot Decentralized Data at Scale

Open hot storage network that scales IPFS and Filecoin with verifiable, user-owned data.

) so I'd imagine a service that acts as a nostr relay and has an ipfs node in combination to provide git services. I don't have knowledge of your third item though.