Simon Frings

@kelunik We try to avoid squashing changes via GitHub's squash on merge. This will always lead to GitHub being the new committer and it will also add an extra commit.

@dinooo13 Thanks for this PR, can you add some references in your PR description similar to my comment in [clue/reactphp-mq#34](https://github.com/clue/reactphp-mq/pull/34).

@simPod thanks for your work on this so far :+1: To keep you updated: @WyriHaximus, @clue and I are currently looking into this, we'll have a call later this day...

@Thomas-Gelf thanks for looking into this :+1: It's not 100% guaranteed that this will always return a ExtendedPromiseInterface. I discussed this with @clue and maybe there should be something like...

@WyriHaximus good catch, looks very "promising" to me (sorry I'm not sorry) ^^ I talked with @clue about this one and it's a bit inconsistent to the other methods if...

It seems like this ticket is open for quite a while now. I want to avoid issues and pull request laying around for too long, but this depends on each...

It seems like this pull request is open for quite a while now and didn't receive any updates since. Last comment is over a year old and I want to...

Hey @Chrisdowson, thanks for updating the PR :+1: Unfortunately the test are currently failing, could look into that. The [reactphp/dns](https://github.com/reactphp/dns) project has over 20 million installations and we ourselves use...

It seems like this pull request is open for quite a while now and didn't receive any updates since. Last comment is over a year old and I want to...

@Bugophobia I agree that this can be a potential threat, but I don't see the problem in the whole `X-Powered-By` header, only in exposing the used version of Ratchet. Even...