Eric Tang

@j0sh broadcaster can create a new NodeID anytime, but the IP will stay the same. Everyone - I think this has been a great discussion. I updated the proposal. Let...

@rairyx I think given a large enough N (for each R to relay to its neighbors), it'll work. We'd have to test in practice to see what N is. Also,...

@j0sh I don't have a strong preference between multiaddr and IP/port, just thought it might be more "generic" to use IP/port, and have the client decide how to make the...

Updated `TranscodeSub`. @j0sh I think you can create multiple streams over the same connection, but may only be able to create a single connection for a single multiaddr.

@j0sh updated the document according to your comment about `6` We'd probably have to implement some kind of policy for connection handling for T. For example, it can check the...

> How long should the transcoder multiaddr be valid for? The duration of the job unless indicated otherwise? The transcoder could send new TranscodeSub requests as needed, in order to...

@j0sh I think the ability to look up a JobID from StreamID might be necessary anyways. Currently we don't have any "permanent" state in the node. But I think we'll...

Hi @darkdarkdragon, [Pavel Baykov](https://angel.co/pavel-baykov-1) have been talking to me about this in Discord so I created this issue for him. Sorry about the confusion. I will be more clear about...

Ahh yeah - json + gob is definitely not the best approach... I was planning to eventually use protobuf (suggested by the ipfs team and I think you can find...

You are correct in that we have an routing loop issue. There are some possible fixes, one being always caching the message for some period of time via a package...