Update IPFS codec registration example

[jbouwman]

Update documentation to reflect that versions of js-IPFS greater than 0.40 support direct usage of multiformats codecs.

[rvagg]

best to use use dagJose.name since that's the internal matching that's going to happen in js-ipfs and the user can avoid one magic string

[oed]

Suggested change

	const cid = await ipfs.dag.put(jwe, { format: 'dag-jose', hashAlg: 'sha2-256' })
	const cid = await ipfs.dag.put(jwe, { format: dagJose.name, hashAlg: 'sha2-256' })

[rvagg]

👌 nice
lgtm aside from the use of 'dag-jose' over dagJose.name as mentioned inline

[jbouwman]

ok_hand nice
lgtm aside from the use of 'dag-jose' over dagJose.name as mentioned inline

Done -- thank you for the review. I arrived here after stepping through https://blog.ceramic.network/how-to-store-signed-and-encrypted-data-on-ipfs/ which refers to the legacy codec wrapper. I wonder if there's a way to attach a note there mentioning the change.

[rvagg]

@oed will know. There's been a lot of change in the entire IPLD (and therefore js-ipfs) stack this year but it should have stabilised now so this pattern should be good for the time being.

[oed]

Thanks for this update!
Just a small change needed as already mentioned by @rvagg.

Regarding the blog post. I made a note to update it once we update to the latest js-ipfs in the js-ceramic code base.

[oed]

Suggested change

	const cid = await ipfs.dag.put(jwe, { format: 'dag-jose', hashAlg: 'sha2-256' })
	const cid = await ipfs.dag.put(jwe, { format: dagJose.name, hashAlg: 'sha2-256' })

[oed]

Suggested change

	const cid = await ipfs.dag.put(jwe, { format: 'dag-jose', hashAlg: 'sha2-256' })
	const cid = await ipfs.dag.put(jwe, { format: dagJose.name, hashAlg: 'sha2-256' })

[oed]

Suggested change

	const cid = await ipfs.dag.put(jwe, { format: 'dag-jose', hashAlg: 'sha2-256' })
	const cid = await ipfs.dag.put(jwe, { format: dagJose.name, hashAlg: 'sha2-256' })