generalize stream tags
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 46
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
At the moment there is something like a stream table that contains boolean flags for some pre-defined tags (nsfw,afk,...) that streams can receive. Instead, think about setting tags dynamically, and letting the front-end decide what to do with any given tag. In the future that might allow people to tag their own streams and letting people filter via that.
Another idea is introducing special tags like news for streams that could be displayed in some special way as always-online regardless of viewership for well-known always-online news coverage streams.
Another idea: admin ability to mark custom m3u8/advanced embeds "saved" so you do not have to click the warning away. General version: whitelist whole domains or similar.
Contributor guide
No contributing guide indexed for this repository
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
No files or tests are named. Start by tracing how the stream table, existing boolean tags, frontend tag handling, and custom m3u8 or advanced-embed warnings are implemented. The scope needs narrowing before completion can be judged: dynamic tags, filtering, special news behavior, and domain or embed whitelisting are separate possible outcomes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend-api-design, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100