I have published a name key using the w3name service and when I resolve the name via https://name.web3.storage/ it works fine, but when i try to resolve it via other public gateways such as https://ipfs.io/ipns then it doesn't resolve.
queries :
Is this an intentional behaviour ? and if it intentional then is there any way we can modify it so that the name can be resolved via public gateways
Could it be possible that, the w3name ipfs node is pushing the updates but they might not be understandable by the other nodes as there is a format change which they are not able to process.
Issue Description :
I have published a name key using the w3name service and when I resolve the name via https://name.web3.storage/ it works fine, but when i try to resolve it via other public gateways such as https://ipfs.io/ipns then it doesn't resolve.
queries :