GitLab

Co-authored-by: Marcin Rataj <lidel@lidel.org>

This outputs a missage that blames a specific sife for not having DNSLink record.  For example, the error message looks like:

`could not resolve name: bad.example.net is missing DNSLink record (https://docs.ipfs.io/concepts/dnslink/)`

The "could not resolve name" portion is still present because the returned error wraps the original ErrResolveFailed, allowing code to test if the error is an ErrorResolveFailed error.

Use eth.domains instead of eth.link for .eth names

Remove dependencies to go-unixfs

Remove InitializeKeyspace function from publisher

Chore: bump go.mod and testing to go1.15

chore: remove unused go-ipfs dependency in go.mod

The remaining dependency was in tests. We can hardcode a CID instead of
requiring unixfs just to obtain an arbitrary CID that correspond to the empty
directory.

This is mostly go-ipfs specific and has been moved there.

See https://github.com/ipfs/go-ipfs/pull/7984

This was a bad leftover.

Improve go-namesys documentation

Co-authored-by: Adin Schmahmann <adin.schmahmann@gmail.com>

This "simplify" flag mainly removes redundant types in expressions.

Not particularly important, but a nice change that also makes gopls not
show warnings.

* show the domain name if DNSLink failed to resolve a domain because it wasn't a valid domain name

Original author: @AluisioASG

Namesys cache uses IPNS keys with their binary representation instead of string representation to avoid encoding mismatches

* feat: stop checking the DHT for public keys before doing an IPNS get. It has been many releases since we started adding the public keys into the IPNS records by default.

Previously, we'd return the error + result, then the result.

feat: introduce the dual WAN/LAN DHT

If we fail to publish, _invalidate_ our cache. The publish may have partially
succeeded.

License: MIT
Signed-off-by: Marcin Rataj <lidel@lidel.org>