KDEOct 19, 2024

KUnifiedPush: KDE's efficient way of delivering notifications to your apps

KUnifiedPush, KDE's client library for the UnifiedPush protocol, has reached version 1.0.0. KUnifiedPush provides a way to deliver notifications instantly to multiple apps on your devices even if the apps are not running.

Ideal for social media, weather and instant messaging apps, it will also contribute to improving the battery life on your mobile devices.

https://blogs.kde.org/2024/10/19/kunifiedpush-1.0.0-is-out/

@[email protected]

KUnifiedPush 1.0.0 is out!

KUnifiedPush provides push notifications for KDE applications. Push notifications are a mechanism to support applications that occasionally need to receive some kind of information from their server-side part, and where receiving in a timely manner matters. Chat applications or weather and emergency alerts would be examples for that. More technical details about KUnifiedPush are available on Volker's introduction post about KUnifiedPush.

KDE Blogs
Show threadthe tower fairyOct 19, 2024
@kde @[email protected] I'm sorry to see you've gone the "14 + 1 standards" XKCD way. Is there any reason why?
Show threadBro666
If you bothered to read the linked article and Volker’s blog post (linked from the article), which you obviously haven’t, you would see how this is not the case.
Oct 19, 2024 at 1:32pmWeb
Show threadthe tower fairyOct 19, 2024
@Bro666 I came to post this Just after reading Mr Krause's post and the background of UnifiedPush. My gripe is because there are already existing frameworks like w3c's Web Push (which is not addressed in UnifiedPush, as far as I could see) and the native push frameworks of each mobile OS (which are disqualified on privacy reasons). Hence why I said "14 push frameworks", because KDE is aiming to serve both desktop and mobile with a new standard, inducing even more fragmentation.
Show threadBro666Oct 19, 2024
KDE is not introducing a new notification framework. It is using something that already exists, so still barking up the wrong tree.
Show threadVladyslav Marchenko ⛨Oct 19, 2024
@crystalmoon Ok, so you've said that there is "14 push frameworks" really meaning only one — Web Push.
So let's see if there is a thing at all.
According to the Push API spec (https://w3c.github.io/push-api/) the Abstract already gives us a main idea: it is designed for WEB applications, not mobile or desktop at all, and actually requires a running app instance. It's a lightweight, limited part of the app that runs in background (called Service Worker) and may be stopped/removed by browser.
Push API

Show threadVladyslav Marchenko ⛨Oct 19, 2024
I have implemented ones before and can say for sure: even if it's called Push API, it's actually about PULLing notifications from a remote server using a "special" part of your app, not about PUSHing the notification to your app by external system (which is required on mobile for power saving reasons).
So... yeah, there is still 0 standards for mobile/desktop push notifications except UnifiedPush. And if there is none, where the fragmentation you're talking about is?
Show threadS1mOct 20, 2024

@crystalmoon @Bro666 Server to server is specified with RFC8030+RFC8291+RFC8292 (aka web push) \*, so we're far from xkcd 14+1 protocols

\* This clarification is being merged to spec