Added session token model to que
Added que token authentication on the backend

just do a POST /auth with {"user": "username", "pass": "password"} to login.
GET /auth/whoami to get user info, and DELETE /auth to logout
Frontend logging in and out, but it doesn't really do anything yet
things have fully working permissions
serverside permissions
Authentication header in frontend client in all http requests
Backend now has fully working auth (I think...)
added thing permissions
got rid of those pesky 'trigger' and 'detrigger messages'
all the permissions for everything else that I can think of right now
changed defaut page to login page
somewhat complete login screen
fixed a bug with session token's permissions being stored in the db as a string
redirect a user to the login page who isn't logged in on another page
animations on view change

this fixes the jerkyness between views that has been their sience the introduction of routes
Settings screen for adjusting tokens now abides by permissions on the client side
allowd for improoved stacking of settings panes
added .loginWithKey, so login is possible with just a key now, too.
persistant login sessions

They are managed in the client - I don't really think this is a security problem though, because the auth key is sent with all requests anyway.
routes are redirected after login to what they were before the login