bigs

To expand on this issue, problems seem to be rooted here: https://github.com/joefitzgerald/go-plus/blob/72d998a58a2b18fa34da588054f7f019e70db77a/lib/config/locator.js#L269 The paths are statically programmed and don't really work for any alternative package managers on *nix systems (I'm...

@joefitzgerald ah, odd. got a bit lost in the indirection, but that definitely checks out. i'll try and debug this soon... would be nice to know what was happening if...

thanks @vyzo! def agree, will remove the memorytransport.

> To actually hook this in, I think we'll need a `/memory` multiaddr. We strip out the `/p2p/Qm...` part when looking up transports as that isn't actually a part of...

oh wow @lgierth thanks for the link in

> > i wanted to avoid having to extend the multiformats repo, though it seems it's unavoidable. i'd advocate for both /memory and /pipe, even if we don't choose to...

@Stebalien i've fixed the implementation of the pipetransport to eschew upgraders and the like. i'm going to focus my attention to the multiformats side to get that set up, then...

@raulk the only blocker right now is consensus around /memory multiaddrs at pierre’s linked issue. i’ve already implemented a version that uses opaque uint64 slots should we thumbs up that!...

regarding the dialer work, i think the transport is still necessary (you still have to listen somewhere in your code) but it will be much cleaner determining where we want...

i suppose so long as a stream handler exists, listening becomes irrelevant, though that does break pierre’s testing use case, which could be quite nice. it allows us to allocate...