While potentially useful, our transports won't accept blocks of this size. If we allow users to add them to their datastore, they'll run into hard to debug issues where we won't actually transfer the files.
I believe I was thinking about banning this in the go-ipfs block API (and the add options) instead of at the blockstore level itself. This limitation is a side effect of the IPFS protocol as it exists today, not necessarily IPLD itself.
While I'd prefer not to add this blanket restriction to the default blockstore, it might make sense to implement it as a wrapper. That would make it easy for applications to specify a size policy without enforcing a default policy (alternatively, it can just be added as an optional/configurable limit to the default blockstore.
While potentially useful, our transports won't accept blocks of this size. If we allow users to add them to their datastore, they'll run into hard to debug issues where we won't actually transfer the files.
I believe I was thinking about banning this in the go-ipfs block API (and the add options) instead of at the blockstore level itself. This limitation is a side effect of the IPFS protocol as it exists today, not necessarily IPLD itself.
While I'd prefer not to add this blanket restriction to the default blockstore, it might make sense to implement it as a wrapper. That would make it easy for applications to specify a size policy without enforcing a default policy (alternatively, it can just be added as an optional/configurable limit to the default blockstore.