Use ipns://<.crypto or .eth> by default when IPFS is setup

[bbondy]

For our Unstoppable Domains and ENS we're currently resolving to HTTP. We should prefer to resolve to IPFS first by simply loading ipns:// as the default protocol for them when IPFS is setup.

go-ipfs will support this in 0.9.0 so we can wait for the RC1 to be released and then use an RC manually before we ship the update to implement this.

Note that we shouldn't use this ipns:// method when the option mentioned in this issue is set to Ethereum:
#15750

[lidel]

• FYSA DNS resolver configuration in go-ipfs 0.9.0 will look like this: https://github.com/ipfs/go-ipfs/blob/master/docs/config.md#dns
• 0.9 release process is being tracked in Release v0.9.0 ipfs/kubo#8058, subscribe to it to get notified about RC1

[spylogsster]

waiting for 0.9.0 for this #15937

[bbondy]

Just checking on the status of this since 0.9.0 is shipped.

[lidel]

afaik this is ready to be picked up and worked on – go-ipfs 0.9+ already shipped to all users, so we can have ipns://*.eth in address bar and control which DoH endpoint is used for resolving them via DNS.Resolvers in $IPFS_PATH/config

[gerbz]

@bbondy Would love to see ENS domains defaulting to ipns:// which leaves the .eth name in the address bar. This also makes the .eth name accessible via javascript window.location.hostname.

You can use Vitalki's as an example as vitalik.eth's ENS Content record is set with an ipfs:// key.
esteroids uses an ipns:// key in their esteroids.eth ENS Content record and it appears to behave the same way as Vitalik's in Brave.

Brave Settings -> Method to resolve IPFS resources -> Local IPFS Node:

• ✅ ipns://vitalik.eth -> ipns://vitalik.eth
• ❌ vitalik.eth -> ipfs://bafybeibc7nsbhktzjvplpi4qmzk7kd22yqol3v4thpbhp5yzfspcc56hsi/

Brave Settings -> Method to resolve IPFS resources -> Gateway:

• ✅ ipns://vitalik.eth -> https://vitalik-eth.ipns.dweb.link/
• ❌ vitalik.eth -> https://bafybeibc7nsbhktzjvplpi4qmzk7kd22yqol3v4thpbhp5yzfspcc56hsi.ipfs.dweb.link/

@lidel and @makoto may have some input/insights on this as well.