Re: [push-api] Rename (un)register to (un)subscribe (#98)

I don't feel very strongly about subscribe and subscription vs register and registration. The churn in spec, implementations, and demos seems hardly worth it.

Subscribe may seem nice when phrased as "subscribing to a source of push messages" but it also seems a little weird as you don't even specify the source that you are subscribing to. You're acquiring an endpoint to which any number of apps can send messages, and it has an id. It seems like "register" and "registration" cause very little confusion as a name for these concepts.

In favor of sticking with register: it retains consistency with the Service Worker, Sync, and Geofencing APIs.

CC @jakearchibald for the Service Worker perspective

---
Reply to this email directly or view it on GitHub:
https://github.com/w3c/push-api/issues/98#issuecomment-68889898