Steve Loeppky

@ajnavarro : doh - fixed - https://github.com/libp2p/go-libp2p/blob/master/p2p/host/resource-manager/README.md#usage

2022-09-29: * Adjust log levels so see whenever there is a resource checkout * Expose grafana dashboards from go-libp2p resource manager: https://github.com/libp2p/go-libp2p/blob/master/p2p/host/resource-manager/obs/grafana-dashboards/README.md * Write out what we're planning to do...

Moving this to draft until we're able to give a concerted effort on IPNS improvements as part of https://github.com/ipfs/js-ipfs/issues/2921

@mpetrunic @achingbrain : what are the next steps for getting this over the line? Is it just about code review?

I haven't been following the details closely, but I know we have had security issues with tar issues over the years. Can we make sure the security hardening is all...

2022-06-28 conversation: in general, it has been intentional for js-libp2p to not just strings to avoid ambiguity around peerIds, multiaddrs, etc. There have been improvements in recent js-libp2p releases. Another...

2022-04-07: we need to see if this has been superseded by go-libp2p work.

@schomatis : are you going to make the corresponding change/improvement in go-lobv2?

2022-04-26 conversation: 1. For 0.13: do nothing (in the release notes for 0.13, "if you were using log-tail for certain things, you'll need to look at the daemon input. Previously...

@Jorropo : is there an issue in https://github.com/ipfs/go-log to improve things there?