Ivan Poleshchuk

I've been doing endurance test locally with streamtester for almost 10 hours: ``` ./streamtester -sim 10 -repeat 10000 ``` And so far didn't encounter any abnormal behavior of B. One...

Hmm, after further investigation, I think it's a race condition [here](https://github.com/livepeer/go-livepeer/blob/cb97d577de35c1737a35951b6b55064dbb87a930/server/broadcast.go#L224). Domain name or IP doesn't matter, it just affects latency so that error appears. The issue seem to occur...

Turns out domain name does matter after all, but in an indirect way, with issue occurring on a localhost as well. Fix is ready. Workaround for current version: specify **precisely**...

Interesting idea. My initial reaction is that it contradicts decentralized nature of Livepeer. Could we instead identify and address an inefficiency, which lead to such request?

#2486 seem to be related to this

Maybe Jaron could comment on most suitable protocols for Mist T (Ffmpeg) interactions and what it would take to implement? His remark inspired me to experiment with direct communication and...

@AlexKordic I think the main question is how to stream segments to and from Mist. To keep changes to minimum, we need a secure protocol which a) already supported by...

@thomshutt * Ts are not actually exposed with direct model, they just need to have internet access to reach B (Mist) and pull the stream / push results. I think,...

Thanks for comments @yondonfu. > Seems that there would need to some sort of feedback mechanism b/w M & B so B can learn about T failures from M as...

That's a good idea to have some sort of backup transcoders on O level. It could be implemented by adding a CLI flag `-secondary` for a standalone T, with which...