Further ideas and issues.

Author: Ricardo Santos

IDEAS

@@ -9,3 +9,7 @@ party starts.
 == EchoNest suggestions ==
 In addition to searching, suggest tracks (seeded with the play history of the
 party) to the user with high danceability.
+
+== Add songs via Twitter ==
+Grab tweets mentioning the event/to @spartify, use echonest API to figure out
+song and add it to play queue.

ISSUES

@@ -3,3 +3,8 @@ Current memcached based solution is suboptimal, and predictably the more people
 participating, the more likely votes or tracks will get lost. In reality, this
 doesn't pose itself as a major issue given the likely low number of participants
 per party.
+
+== Security ==
+Potential issues with access levels, party guests may potentially be considered
+hosts. Currently it's the frontend responsability to make sure this doesn't
+happen, in the future the Backend should.