Joystream / Joystream/joystream
idea:Media Management
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Currently Joystream has a limited number of videos and has seen slow expansion, it would appear that many more videos are now being posted and with the consideration to actively market Joystream through Online Blogs we can expect that many more users will soon join.
At present the curation of videos is managed through Google Sheets, whilst this solution is and will work with limited numbers of videos as Joystream expands this will become unsustainable and cumbersome to manage.
My proposal (I can not implement this, but can present the strategy) is additional functions to the Web front end of Joystream for users and channel owners, whereby channel owners can be warned/blocked/have videos deleted and be notified of such.
A simpler solution to managing the video content at Joystream might be something like the following.
Curators have an Admin page/login to play.joystream.org whereby when viewing videos they would have UI buttons to Warn (with ability to describe reasons why), Delete and Block Video content. It would also be quicker for Curators (and provide better function for the Video Channel owner/content creator) if the action of Warn, Block, Delete sent a notification to them perhaps as a message to them within the forum and to their registered email account.
As Joystream grows this management system would allow for content curators to manage the viewing/checking of video content far quicker and (ideally) the actions necessary after a user is warned for a video, could be automated. For example, users is warned about video and given 3 days to make changes, content curator receives notification to check video at end of 3 days and if no satisfactory change is made curator can take relevant action to delete video.
This Web UI change would have functions than integrate into the back end database, creating a centralised management of play.joystream.org that is sustainable as the service grows.
I hope other members see the benefit to Joystream to implement these changes, for the efficient and effective management of the service.
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
The proposal names no files, tests, or entry points; start by reviewing the existing Google Sheets curation process and the play.joystream.org video and channel-owner flows. Define the scope for curator warnings, blocking, deletion, and notifications before implementation, with completion requiring an agreed end-to-end workflow.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, full-stack
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100