Community Feedback & Questions Summary - 2021-12-07

This thread summarizes Qs and feedback from the Livepeer community, which are currently collected on Discord and the weekly Watercooler chat event.

  1. Creation of a community wiki and where to host it; is GitHub - livepeer/wiki: Wiki for the Livepeer Project the right place for it?

  2. 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.

  3. 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

  4. What is the Redeemer role, and what part does it play, if any, in today’s version of the protocol?

  1. Creation of a community wiki and where to host it; is GitHub - livepeer/wiki: Wiki for the Livepeer Project the right place for it?

I missed the first half of the water cooler - what’s the goal here in terms of content? Is it (a) a more useful version of Livepeer - Livepeer Documentation, or (b) something else entirely?

If it’s (a), I’d push for contributions to the docs. If it’s (b), the wiki might be a good place with the caveat that a lot of the info there is very outdated.

Two guiding principles: (1) we should avoid duplicating information (2) we should attack the root of the issue. If “community wiki” is filling in for lackluster documentation, then we should fix the documentation (and potentially KO the wiki so it doesn’t confuse people) rather than increasing the maintenance surface area.

stability issues

Sounds like we’re having some trouble reproducing this? Definitely on the radar but concise steps to reproduce will go a long way towards moving this forward. cc @yondon @rafal

Orchestrators wish to have network insights into the protocol… An RFC for this should be posted to the forum soon.

Excited to see this RFC!

What is the Redeemer role, and what part does it play, if any, in today’s version of the protocol?

@yondon @NicoV can you provide any color here?

It’s something else entirely, and not due to lackluster documentation.
A community maintained wiki for non-Livepeer topics like:

  1. Dynamic DNS and choosing / using a provider
  2. OS and network security
  3. Tips for split O / T setups
  4. Long detailed howtos

Livepeer.academy may be more appropriate?

Let me think about this and get back to you later today… I would argue that some of this should be in the docs to begin with, but I also see the value of a standalone wiki.