Discourage/block using the same stream key simultaneously at multiple ingest centers
Open
Nobody has claimed this yet.
type: feature
- Dominant language
- TypeScript
- Stars
- 88
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
- [ ] Update docs
- [ ] Put notice on livepeer.com stream page
- [ ] Outright block it
- [ ] If we don't block it outright, confirm we are still charging them properly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points, so first map the ingest-center handling, stream-key flow, livepeer.com stream page, documentation, and charging behavior. Clarify which of the listed outcomes is required and define acceptance checks for simultaneous use, user notice, and billing before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- backend, documentation, frontend, payments
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100