Ashley Jeffs

This seems reasonable. I'm marking this as a bug since confusing APIs aren't an intended feature! The internal workings of leaps have changed significantly since the client API was first...

This should probably be tackled after https://github.com/Jeffail/leaps/issues/8 is resolved.

Hey @amlwwalker, The conventional way of going about this is to add an AWS S3 implementation of the `Store` type: https://godoc.org/github.com/Jeffail/leaps/lib/store#Store, and that could be dropped in and used directly....

Hey @amlwwalker, yeah just implement the Store interface. I'm currently part way through a large refactor to make the library easier to work with, the interface should stay the same...

Hey @nfisher, I've wanted to add this in for a while but my front-end skills are my most lacking. To be honest the entire UI could do with some TLC...

Hey @mindeavor, Leaps currently has support for authentication via single-use tokens, which you can activate through the [authenticator](https://github.com/Jeffail/leaps/wiki/Configuration#authenticator) configuration option, and this allows you to utilize an authentication system of...

So the latest pull request jazzes up the authentication interface within leaps so we can start supporting more/better authentication options. I'm going to look at making a JWT option ASAP.

@qknight, sounds like a good idea, let me know how it goes!

Hey @adevress, looks good. Would you be able to add some unit tests to https://github.com/meltwater/served/blob/master/src/served/multiplexer.test.cpp?

Hey @nikhedonia. Sounds good, would be happy to take a pull request.