KUnifiedPush: KDE's efficient way of delivering notifications to your apps
KUnifiedPush: KDE's efficient way of delivering notifications to your apps
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.
@kde@floss.social @kde@lemmy.kde.social ooooh I would love for it to also use molly-socket so that I could use it for Signal notifications https://github.com/mollyim/mollyim-android-unifiedpush?tab=readme-ov-file#unifiedpush
@kde@floss.social @kde@lemmy.kde.social This is a really nice and welcome development! Congrats :D
@kde@floss.social @kde@lemmy.kde.social This has been on the back of my mind for a while and seeing this being implemented in KDE makes me want to try it.
@kde@floss.social @kde@lemmy.kde.social Will this be part of future KDE Gear?
@kde@floss.social @kde@lemmy.kde.social @gnome Something similar (hopefully using the same D-Bus interface) for GNOME planned?
@kde@floss.social @kde@lemmy.kde.social I'm sorry to see you've gone the "14 + 1 standards" XKCD way. Is there any reason why?
It turns out, in this case it isn't. This is about a KDE library (service?) that uses Unified Push, which is a standard implemented by servers like ntfy, Nextpush, and Gotify. If you use any f-droid apps, you're probably already using Unified Push. Home Assistant uses it for mobile notifications, too.
It is, probably, the third biggest notification protocol after Google's and Apple's, only it doesn't route through their servers or provide them with more of your data to harvest and sell.
Unified Push is a good thing. It looks like KDE just makes it accessible to KDE application developers through the KDE libraries.
@sxan I have never used f-droid, as I do not use Android.
Regardless, all banks and fintechs in my country will disable your account you if they detect sideloading apps like it.
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.
@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.
@crystalmoon @kde@floss.social @kde@lemmy.kde.social what exactly are the fourteen other push notification frameworks for desktop Linux? Iβve literally never seen one before
@crystalmoon @kde@floss.social @kde@lemmy.kde.social UnifiedPush is the only relevant standard being actively adopted by free software. You need an ecosystem around a push standard for a client and server setup to be useful/practical, and nothing comes close to UnifiedPush. We'll never get rid of the 14+1 problem if we don't focus efforts on a particular open standard, and this IS the one by all means.
@kde@floss.social @kde@lemmy.kde.social @crystalmoon@chaos.social unifiedpush isn't a new standard, it's pretty much the defacto way to get push notifications on Android without google play services