GitLab

remove unused field permanent from mapping

Bump github.com/jbenet/goprocess from 0.1.3 to 0.1.4

Bumps [github.com/jbenet/goprocess](https://github.com/jbenet/goprocess) from 0.1.3 to 0.1.4.
- [Release notes](https://github.com/jbenet/goprocess/releases)
- [Commits](https://github.com/jbenet/goprocess/compare/v0.1.3...v0.1.4)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

Bump github.com/ipfs/go-log from 1.0.1 to 1.0.2

Bumps [github.com/ipfs/go-log](https://github.com/ipfs/go-log) from 1.0.1 to 1.0.2.
- [Release notes](https://github.com/ipfs/go-log/releases)
- [Commits](https://github.com/ipfs/go-log/compare/v1.0.1...v1.0.2)
Signed-off-by: dependabot-preview[bot] <support@dependabot.com>

typo and changed deprecated method

update go-nat to v0.0.4

nit: fix log format

fix: remove notifier

1. It was unused.
2. It was broken. Attempting to register a notification listener would have
   registered the notifier itself.
3. We need to switch to some consistent event/notification system anyways so
   we're going to replace this code no matter what.

(found by @pornin)

dep: update go-nat

This reverts the change where we were explicitly trying to match the internal
port to the external port. Unfortunately, we really want a truly _random_ port
as not all NATs handle conflicts gracefully.

switch to libp2p's go-nat fork

remove all uses of multiaddrs

NATs only care about TCP/UDP and ports. Using multiaddrs here made this library
really hard to work with correctly.

Furthermore, this library doesn't _actually_ support specifying the internal IP
address. However, we'd still _act_ like the internal IP address mattered. This
caused all sorts of mismatches.

add gomod support // tag v0.0.1.

gx publish 0.8.12

gx publish 0.8.10