whossname

@craigp do you have any interest in updating and maintaining this library? I might be interest in taking ownership if you aren't. I need to try it out in production...

I've just done a quick review of my own, it will definitely need some work before it is merged. The biggest issue is that I don't think `SlackLoggerBackend.Pool` should be...

added another commit that solves the issues described above.

I've noticed a security concern while playing around with this library. I think the slack webhook should be treated as a secret, but it is stored as state in the...

I added two commits that change some functionality. The first overrides the Poison.Encoder.List implementation. This code was crashing when it needed to encode list of the form `[head | "string"]`....

I have done most of the stuff mentioned in the previous post and updated the documentation. I moved the `get_url` function into the `Pool` module, so at least it isn't...

I've figured out a better way of handling the Poison encoding issues, so I've removed the code to override the implementation for `Poison.Encoder.List`. It cuts the log message after the...

That last commit hides the webhook in the `HTTPoison.Response` in the event of an error. This doesn't cover every situation where it might appear in logs, but I think I've...

Added the `"SLACK_LOGGER_DEPLOYMENT_NAME"` environment variable, the value of which is included in the "Deployement" field in the Slack message. It means that if multiple deployments report to the same slack...

@craigp I'm pretty sure I just need to update the documentation and I am done here. In summary I added these new features: * Debouncing in the producer. If the...