after implementation of the fully working socket battle room, there was a styling issue on the editors.

one in every 20 or so times, when a user challenges another user to a battle, only one user (at random) will get the link to the battle.

notifications should be a directive so that they are accessible throughout various parts of the app, especially as settings, profiles, and listing pages develop.

refactor the sockets into an ng module for easy usage

occasionally, editors get duplicated. can't seem to mimic the behaviour yet, but definitely needs to be looked in to.

consider making it dynamic, load it from the database. no need for live updates on it.

look into the following:

• add viewport meta tag for full responsiveness
• make sure all grids look good at all sizes
• check font sizes at all screen sizes

if you log out from one username and sign in with another (on the same machine), the old (logged out) user is displayed in the "online now" list.

Possibly a slider, or 4 options (challenging, difficult, expert, insane)

consider the following:

• js hint
• concat
• uglify

just because!

when two players accept a challenge, and one user goes to the link ahead of time, the following may happen:

• the user who went to the link first might click the "i'm ready" button
• the user who goes to the link second will not see that the first user clicked it
• if that second user clicks the ready link, the first player goes to the battle room
• the second player will then be stuck in the waiting room

in the earlies, we used "duels" as the server api routes, but later called them "battles" on the client side. these should be consolidated for consistency.

Need to update the user on the database with problems they have already attempted