livepeer / livepeer/explorer

Display Orchestrator's "Work In Progress" Streams in Livepeer Explorer

Open
#79 1 comment 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

data
Dominant language
TypeScript
Stars
11
Forks
26
Avg merge
11h 58m
Merged PRs (30d)
16

Description

What's the problem? (required)

There is a disconnect in Livepeer's outward-facing interfaces.

The connection should be directly between the:

  • staking / bonding / reward functionality
  • resizing of video content functionality.

This connection is not being made, hence there is a disconnect.

What's the current behavior? (required)

People who visit the Explorer are only really there because of rewards. Money. Hard cash. Income. Streaming money. They don't ever get to understand the fundamental point of what we're doing here... providing video infrastructure services. Not shitcoins. GPU-powered farms of specialist computer capacity, resizing the content to make it much ore accessible.

They turn up, play with a slick black and green interface, which tells them how much money they might make. And then they go away. To the next Ethereum-based protocol or open source video project, looking for the truth.

Describe a possible solution you've considered (optional)

Display all the streams being processed by an Orchestrator at that moment, on the Orchestrator's page in the Livepeer Explorer. After all, it's the most engaging way to explore what the protocol is for.

Show the source.m3u8 and the P144p30fps16x9 and everything in between. Show them as individual streams, not auto-selected in a player. Don't resize in browser... let the 4k / 8k streams break the UI (to begin with).

Additional context (optional)

I don't know what to say here. But I think that this needs some serious consideration. Even some experimentation to MVP it somehow.

Not a broadcaster's stream, the work being done by the orchestrator. In all its glory.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The issue names no files, tests, or entry points. Begin by locating the Explorer's Orchestrator page and the data source for currently processed streams; done means the page can display an Orchestrator's in-progress source and transcoded streams individually.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
frontend, web-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.