From f4b015e273897e0a236ba22ffcd65cae0ab5c96c Mon Sep 17 00:00:00 2001 From: Marcelo Kanzaki Date: Sat, 11 Apr 2026 10:13:19 -0300 Subject: [PATCH 1/2] Fix typo in README about serviceWorker subscription --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 6125b6e..55f378f 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ Sending a web push message to a visitor of your website requires a number of ste 1. Your server has (optionally) generated (one-time) a set of [Voluntary Application server Identification (VAPID)](https://tools.ietf.org/html/draft-ietf-webpush-vapid-01) keys. Otherwise, to send messages through Chrome, you have registered your site through the [Google Developer Console](https://console.developers.google.com/) and have obtained a GCM sender id and GCM API key from your app settings. 2. A `manifest.json` file, linked from your user's page, identifies your app settings. -3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, with creates a `subscription` JSON object on the client side. +3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, wich creates a `subscription` JSON object on the client side. 4. Your server uses the `webpush` gem to send a notification with the `subscription` obtained from the client and an optional payload (the message). 5. Your service worker is set up to receive `'push'` events. To trigger a desktop notification, the user has accepted the prompt to receive notifications from your site. From 2d12bfb1a9ff719b527edcb984f8ddd4f2814fcd Mon Sep 17 00:00:00 2001 From: Marcelo Kanzaki Date: Thu, 16 Apr 2026 11:54:01 -0300 Subject: [PATCH 2/2] Fix typo in README.md regarding push notifications --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 55f378f..9c45e8c 100644 --- a/README.md +++ b/README.md @@ -33,7 +33,7 @@ Sending a web push message to a visitor of your website requires a number of ste 1. Your server has (optionally) generated (one-time) a set of [Voluntary Application server Identification (VAPID)](https://tools.ietf.org/html/draft-ietf-webpush-vapid-01) keys. Otherwise, to send messages through Chrome, you have registered your site through the [Google Developer Console](https://console.developers.google.com/) and have obtained a GCM sender id and GCM API key from your app settings. 2. A `manifest.json` file, linked from your user's page, identifies your app settings. -3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, wich creates a `subscription` JSON object on the client side. +3. Also in the user's web browser, a `serviceWorker` is installed and activated and its `pushManager` property is subscribed to push events with your VAPID public key, which creates a `subscription` JSON object on the client side. 4. Your server uses the `webpush` gem to send a notification with the `subscription` obtained from the client and an optional payload (the message). 5. Your service worker is set up to receive `'push'` events. To trigger a desktop notification, the user has accepted the prompt to receive notifications from your site.