Support for the official PWA plugin is required for implementing Web Push in the ActivityPub plugin.

[Jiwoon-Kim]

When developing a plugin that includes a Service Worker, it must rely on the PWA plugin to ensure proper integration and compatibility.

• https://wordpress.org/plugins/pwa/
• https://github.com/GoogleChromeLabs/pwa-wp

[Jiwoon-Kim]

Personally, I think it would be useful if instance profiles or application profiles could also handle notifications such as plugin auto-updates. I don’t really want to receive those by email.

[obenland]

This plugin does not include a Service Worker, unless I missed something.

[Jiwoon-Kim]

@obenland That’s strange. The plugin’s tags clearly indicate Service Worker support, and the GitHub repository also explicitly states:
“If you are developing a plugin or theme that includes a service worker, consider relying on this PWA plugin, or at least only use the built-in implementation as a fallback for when the PWA plugin is not available.”

https://github.com/GoogleChromeLabs/pwa-wp/wiki/Service-Worker

[Jiwoon-Kim]

Ah, if “this plugin” in This plugin does not include a Service Worker, unless I missed something. refers to the ActivityPub plugin, then I understand.
However, for implementing Web Push, shouldn’t a Service Worker be included?

[obenland]

#2216 proposes compatibility with the Perfecty Push plugin, which handles the Service Workers.

[Jiwoon-Kim]

In that case, I understand #2216 as an approach where the ActivityPub plugin does not include its own Service Worker, but instead relies on an existing plugin like Perfecty Push that already implements Web Push. The key points are:

• Only one Service Worker can be active in the browser at a time.
• If multiple plugins each try to register their own Service Worker, they will conflict, and only the last one registered will remain active.
• This is why the official guidance is to rely on the PWA plugin for Service Worker management.
• Therefore, if ActivityPub wants to support Web Push, it should not include its own Service Worker but extend the framework provided by the PWA plugin instead.

👉 So while the approach in #2216 of ensuring compatibility with Perfecty Push is not necessarily wrong, I believe that in the long run it is more stable and recommended to extend a unified Service Worker based on the PWA plugin.

[Jiwoon-Kim]

Ah, I see. Using Perfecty Push may allow Web Push to be implemented immediately, but it will eventually run into the Service Worker conflict problem. In the long run, it seems that the ActivityPub plugin will need to extend the Service Worker provided by the PWA plugin in order to implement Web Push directly.