KUnifiedPush Web Push Update

[Konqi]

Since the 24.12 KDE Gear release we are shipping the client-side push notification infrastructure for applications such as NeoChat and Tokodon. For 25.08 this is receiving a major update to catch up with the evolving underlying specifications and standards.

---

This is a companion discussion topic for the original entry at https://www.volkerkrause.eu/2025/04/18/kde-kunifiedpush-webpush.html

[rokejulianlockhart]

@Konqi

Mozilla Autopush

Thanks to the alignment with Web Push we can now use Mozialla’s Autopush push server as a backend, both their instance as well as a self-hosted one.

Note though that at least Mozialla’s own instance requires applications to use VAPID, which for example isn’t implemented in Tokodon yet. Additional compatibility considerations are listed here.

@vkrause, “Mozialla”?

- Thanks to the alignment with Web Push we can now use Mozialla’s [Autopush](https://github.com/mozilla-services/autopush-rs) push server as a backend, both their instance as well as a self-hosted one.
+ Thanks to the alignment with Web Push we can now use Mozilla’s [Autopush](https://github.com/mozilla-services/autopush-rs) push server as a backend, both their instance as well as a self-hosted one.

- Note though that at least Mozialla’s own instance requires applications to use VAPID, which for example isn’t implemented in [Tokodon](https://apps.kde.org/tokodon) yet. Additional compatibility considerations are listed [here](https://codeberg.org/UnifiedPush/specifications/pulls/1#issuecomment-2281675).
+ Note though that at least Mozialla’s own instance requires applications to use VAPID, which for example isn’t implemented in [Tokodon](https://apps.kde.org/tokodon) yet. Additional compatibility considerations are listed [here](https://codeberg.org/UnifiedPush/specifications/pulls/1#issuecomment-2281675).