The old IPFS URl vs URL vs ipfs:// scheme thing

[olizilla]

whilst strictly correct to refer to ipfs:// scheme URLs as URIs there is something that doesn't quite sit right with referring to https://<ipfs gateway> URLs as URLs but ipfs:// scheme URLs as URIs in the minty mint output

🌿 Minted a new NFT: 
Token ID:              1
Metadata URI:          ipfs://bafybeihadb4iu2qluldbypnt564elwnq7gfhgci7njnqekmnbfuqyncq3e/metadata.json
Metadata Gateway URL:  http://localhost:8080/ipfs/bafybeihadb4iu2qluldbypnt564elwnq7gfhgci7njnqekmnbfuqyncq3e/metadata.json
Asset URI:             ipfs://bafybeidlyceq3bnf63pxszlxmnqz7jqwr22rirjvxgyxi7nwrlboou5ksa/meat-skeleton.jpg
Asset Gateway URL:     http://localhost:8080/ipfs/bafybeidlyceq3bnf63pxszlxmnqz7jqwr22rirjvxgyxi7nwrlboou5ksa/meat-skeleton.jpg

as both forms are URLs and both forms are URIs. It's worth noting that there is a defined URI flavour of ipfs address in this seminal comment The four stages of the upgrade path for path addressing. ipfs/specs#152 (comment) and that looks like dweb:/ipfs/<CID> and is not commonly seen in the wild, but we should avoid taking it's name in vain.

[olizilla]

meybe Address?

🌿 Minted a new NFT: 
Token ID:              3
Metadata Address:      ipfs://bafybeihadb4iu2qluldbypnt564elwnq7gfhgci7njnqekmnbfuqyncq3e/metadata.json
Metadata Gateway URL:  http://localhost:8080/ipfs/bafybeihadb4iu2qluldbypnt564elwnq7gfhgci7njnqekmnbfuqyncq3e/metadata.json
Asset Address:         ipfs://bafybeidlyceq3bnf63pxszlxmnqz7jqwr22rirjvxgyxi7nwrlboou5ksa/meat-skeleton.jpg
Asset Gateway URL:     http://localhost:8080/ipfs/bafybeidlyceq3bnf63pxszlxmnqz7jqwr22rirjvxgyxi7nwrlboou5ksa/meat-skeleton.jpg