ERC-4804 support: Add support for translation of EVM call messages from Web3 URLs

[KingKratus]

We would like to request that the open source dapp Status Messenger add support for translating Web3 URLs to EVM call messages according to the ERC-4804 standard.

Currently, reading Web3 data relies mainly on a translation performed by a Web2 proxy for Web3://. The translation is mainly performed by the proxies, such as dApp sites, node/etherscan service providers, which are out of the users' control. The ERC-4804 standard aims to provide a simple way for Web2 users to directly access Web3 content, especially content on the chain, such as SVG/HTML.

Support for the ERC-4804 standard will allow users to easily access Web3 content while enabling interoperability with other standards that already support URIs such as SVG/HTML.

Please consider adding support for the ERC-4804 standard to
Status Messenger Browser to allow users to easily access Web3 content directly, without relying on Web2 proxies.

The web3:// protocol allows for on-chain websites, which are fully read from the blockchain itself ; it is a finalized ERC, ERC-4804 : https://eips.ethereum.org/EIPS/eip-4804
You can see the website of their creator :
https://w3url.w3eth.io/#/
You can see a simple implementation in a electron based browser here :
https://github.com/nand2/evm-browser

Thank you for your time and consideration.

[KingKratus]

Web3:// allows you to access anything that is on-chain: Dapps, NFTs, on-chain hosted websites, videos, files. Anything that is on the blockchain can be accessed, the front end does not depend on being on centralized servers or on IPFS.