If you told that IPFS is a protocol, why do not use “ipfs://” for canonical links?
The browser extension “IPFS Companion” is using “/ipfs/” for canonical links, why not “ipfs://”?
Typing ipfs:// in the browser would be more beautiful and simple than the ugly and proprietary https://ipfs.io/ipfs/
The browser could find directly the file behind “ipfs://” in the network, instead of going through the “ipfs.io” server. This would be truly decentralized and easy to share.
An ipfs link is easier to share and less destructible than a ordinary, ugly, and centralized http link.
The only problem with the ipfs:// link is that you would have to install a browser extension (or a new browser itself, who knows?), but we can hope that common browsers will include the ipfs:// protocol directly in their code in a near future.