Recent searches
Search options
Administered by:
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 This sounds super efficient and convenient. It's also great that KDE hosts the necessary server to make this work out of the box.
@kde@floss.social @kde@lemmy.kde.social This is a really nice and welcome development! Congrats :D
@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
@noodlejetski @kde@floss.social @kde@lemmy.kde.social
Molly-Socket is a thing because Signal doesn't support WebPush upstream in their server.
If they did, Molly-Socket wouldn't be required, and UP would work directly with Signal :)
But...Signal Desktop doesn't use Push to begin with 
@cyrus but... I don't see anything that would stop someone from using the server with a mobile app
@noodlejetski it's DESIGNED for the mobile app
@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?
@crystalmoon what do you mean?
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.
Home assistant uses it for notifications now? I’ve got the f droid version but don’t see that.
@sxan @timbuck2themoon This is new to me too 
I'd love it if this were the case but so far I see no evidence of it.
I meant the server can deliver notifications via ntfy:
docs.ntfy.sh/examples/#home-assistant
Yeah, I don’t think the mobile app communicates with the server over anything but the web API.
Oh OK. Yes I’ve had this going for a while. If Anyone wants some configs I’ll paste them.
@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.
ntfy is in the app store, so you don’t have you side load it. I don’t know how many iOS apps use ntfy, but many Android OSS apps will ask you over which notification system you want to work.
I was just clarifying that this isn’t one of the XKCD proliferation cases. Apple and Google’s push notifications are proprietary and give them full access to your notifications. Unified Push is the OSS alternative, and this KDE enhancement doesn’t createa another one: it uses the defacto standard OSS push notification specification.
The fact that ntfy is in the Apple app store makes me suspect there must be some number of iOS apps that can be configured to use Unified Push.
@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
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.
KDE is not introducing a new notification framework. It is using something that already exists, so still barking up the wrong tree.
@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.
@crystalmoon @kde@floss.social @kde@lemmy.kde.social which exisiting standards are you talking about then?
@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 Great Job!
But not a huge fan of the missing auth parameters for ntfy - at least I was not able to get it to work with auth.
Can this be self-hosted, so you’re not sending data to a third party service?
@kde is it possible for flatpak'd/sandboxed applications to subscribe to push notifications?
if not, is a portal for this going to be added?
@BasiqueEvangelist @kde IIUC as it uses D-Bus it should be enough to allow the corresponding address.
@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?