Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Video tagging/saving #8

Open
anddero opened this issue Mar 19, 2020 · 0 comments
Open

Video tagging/saving #8

anddero opened this issue Mar 19, 2020 · 0 comments
Labels

Comments

@anddero
Copy link
Contributor

anddero commented Mar 19, 2020

Possibility to add/remove/view tags of the current playing video. Later these tags may be used to extract playlists or other activity.

Added tags may belong to any or all of the following scopes (tagger's choice):

  • Local
  • User
  • Server

Note: tagger = DJ = the client adding/removing/viewing the tags on the /client page.

Local scope: tag is saved into the tagger's browser's local storage. Needs research: How to make cross-LAN tags work properly, so that Giggl client of any origin may access the storage? How long will these tags persist in local storage (should not be cleared if the Giggl client tab/browser is closed)?

User scope: based on the YouTube user the tagger is logged in as. Tags should be saved on the user's YouTube account, not some other type of storage for Giggl-independent and device-independent personal access. To accomplish this, tags may be equivalent to YouTube personal playlists. If the tag is added, the video is added to the playlist of the same name as the tag.

Server scope: tags for videos are saved in the local/remote database of the server running the Giggl instance, depending on configuration. (Usage of local/remote database should be configurable via configuration file. Default database would be a single human-readable file in the execution directory.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant