This thread summarizes Qs and feedback from the Livepeer community, which are currently collected on Discord and the weekly Watercooler chat event.
Creation of a community wiki and where to host it; is GitHub - livepeer/wiki: Wiki for the Livepeer Project the right place for it?
A common consensus among experienced Orchestrators is that running the Orchestrator and Transcoder on the same machine results in the least to zero stability issues. This has the downside of requiring to setup an Orchestrator (and thus the wallet) at every transcoder location.
Splitting the O and T also adds latency since communication isn’t over a local socket. Orchestrators with split O+T setups will provide the data and metrics LP may need around this.
Orchestrators wish to have network insights into the protocol, to measure things like traffic demand by geographical regions. Since this data is best know to Orchestrators, a proposal to create an opt-in, community run and driven “Livepeer Network and Orchestrator” map and website was suggested. An RFC for this should be posted to the forum soon.
@ftkuhnsman has created some interesting tools at GitHub - musicmank545/livepeer
What is the Redeemer role, and what part does it play, if any, in today’s version of the protocol?