Al Zohali

Hello, The template looks good and simple. I will link it in `README` file, thank you too! I see, you use a persistent server key, which is fine, except it's...

I haven't followed news around `servant` for a long time and learned about `servant-auth` from your repository :) It's awesome, that the API becomes stable. The future of `servant-auth-cookie` depends...

Hello, first of all my apologies for a late response! At the moment there is a problem with clashing dependencies of `servant-0.9` and the other packages. I'll take a closer...

Alright, I was mistaken, the packages are ok. The problem was in incompatible default values of stack's resolver and `servant9` flag. This was fixed, so you can build the package...

One more update: I reverted default value of the flag as it caused conflicts in the nightly stack. So to use package with default resolver you should turn off the...

Hi! Sorry for the delay. Your idea sounds great! Gotta implement :) I think we can change `Cookied` from type synonym to servant combinator, so the migration will be straightforward....

Hmm, things are getting complicated again... let's see. At the moment there are three types of modifiers: - `AuthHandler`, that checks cookies, decodes them and provides an extra argument to...

Hi, I'm still not familiar with `servant-auth` codebase, but if it's possible to migrate to the same API they use, it will be very reasonable step towards the next release!...

Hello, the library was developed with an assumption, that a client is not allowed to read cookies. Because of this, a server just serializes/deserializes a record in the most simple...

Hello! You're right, it can be achieved with two auth-handlers, one for cookie/err403 cases and one for cookie/no-cookie cases, that returns `Maybe Session`. However, at the moment it's not possible...