I would like to open the discussion to support more types of content in the Contenthash field.
The support of IPFS files does not seem to support IPNS, which points to a public key signing upgradable content in IPFS.
If a developer wishes to use IPNS to update their content, they should be able to.
As discussed in https://github.com/beakerbrowser/beaker/issues/33, dat can be consumed by ethereum dapps, however the dat devs won’t take the effort to integrate.
DAT is gaining popularity for developers willing to decentralize everything, including ethereum DApps (see the discussion below).
Torrents? Maybe torrents could also become a contenthash, so magnet links can be translated from Contenthash. Technically speaking, is feasible to use old good torrent technology to host a dapp.
Maybe it could work just with the plain hash of the file, not including the trackers, assuming that a decentralized messaging stack (as Whisper/Waku) could be used to implement a decentralized tracker.
Probably this can be left to future.
Please, suggest in comments.