Niels Abildgaard

This blog post with the correct cURL requests might come in handy: https://medium.com/appunite-edu-collection/notifications-d7df385b0ff4

It is! Let's close this.

Woops! Looks like I spoke too quickly. While the `notification_key` field is deprecated (should use `to` instead) the generation of notification keys (representing a group of devices) is still something...

I think this probably calls for some better abstraction than just the `Sender`. It does not really have anything to do with sending :smile: I mean, it would be easy...

Hey @brianbowden, that sounds absolutely awesome! We would love to see and hear your thoughts :smile:

Yes! That's what made me realize we had forgotten to do this for a while. But we need a bit more detail, and to make sure that we include all...

Quoting the relevant section: > Errors in the 500-599 range (such as 500 or 503) indicate that there was an internal error in the GCM server while trying to process...

Quoting [the RFC](http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html): > The Retry-After response-header field can be used with a 503 (Service Unavailable) response to indicate how long the service is expected to be unavailable to the...

I realize that this _may_ break backwards compatibility. Since we're in sub-1.0 this might be acceptable ... How many people actively depend on the error code returned on error? (My...

This PR has been marked with the v1 milestone (https://github.com/ToothlessGear/node-gcm/milestones/v1), becasue it contains breaking changes. I use it to collect ideas for breaking changes that would make for a nicer...