eljenso / livid Goto Github PK

When the user reloads the page, a new socket session is created and the information stored in the old session becomes irrelevant. This is a problem for the voting timeout.
A user exploiting this could vote as much as they want.

A possible fix could be to the session in a cookie to restore it after a refresh.

Would make it easy to search for songs in app, copy link to clipboard and then add to livid queue.

Currently mongoDB is used for saving the current queue and the track history.

MongoDB does not officially support ARM, so installing mongo on the RPi is not straightforward (see the install doc).
Since the this software is designed to run be runnable on the RPi, other options are preferable.
Options would be:

• Another NoSQL DB
• In-memory DB
• Simple variables

Initially next song should be queued 5 seconds before the current song ends, but this delay becomes bigger over time.