https://github.com/illegalprime/lazysoundsystem

A system for allowing multiple unauthenticated users nearby to control and queue music based on a voting system.
https://github.com/illegalprime/lazysoundsystem

Last synced: about 1 month ago
JSON representation

A system for allowing multiple unauthenticated users nearby to control and queue music based on a voting system.

• Host: GitHub
• URL: https://github.com/illegalprime/lazysoundsystem
• Owner: illegalprime
• Created: 2015-02-01T04:32:15.000Z (almost 10 years ago)
• Default Branch: master
• Last Pushed: 2015-06-17T03:42:38.000Z (over 9 years ago)
• Last Synced: 2023-08-02T12:31:15.913Z (over 1 year ago)
• Language: JavaScript
• Size: 391 KB
• Stars: 4
• Watchers: 4
• Forks: 0
• Open Issues: 6
• Metadata Files:
  • Readme: README.md

Awesome Lists containing this project

README

        
# LazySoundSystem

A system for allowing multiple unauthenticated users nearby to control and queue music based on a voting system.

## What is working now:

 - Go to a DJ Webpage from the homepage

 - Get DJ Webpage with /dj/

 - Spotify API Search is exposed to the front end

## What there is to do:

 - Queue to manage songs that is based on user votes. DONE!

 - Restructure the database to remove the voting users from the queue.

 - Veto-ing system

 - Better UI

 - Apps to be able to share music with music apps

 - "Host" computer that actually plays the music

### Queue

 - Should have a downvote, upvote, and veto button.

 - A User only has limited veto's.

 - There should be some weight to the votes for when they are processed

## Ideas

 - Slimer.js for Grooveshark API

 - WebApp for Queue and Voting System

 - Backed by node

 - Using IO for no server

 - 3 Vetos for everyone.. maybe?

## Current Plans (Implemented and To-Be-Implemented)

### Backend (mostly Firebase)

Frontend -> Backend (our node.js server) -> Firebase -> Frontend

#### Structure for Firebase backend

(where does authentication (single session) come into play???)

 - Queue names (mapping to ids)

 - Queue ids (mapped to metadata)

   - name

   - id

   - (password)

 - Queue ids (mapped to actual list of songs)