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

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/

@kde@lemmy.kde.social

    • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍@midwest.social
      22·
      26 days ago

      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.

      • the tower fairy@chaos.social
        02·
        26 days ago

        @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.

        • 𝕽𝖚𝖆𝖎𝖉𝖍𝖗𝖎𝖌𝖍@midwest.social
          3·
          24 days ago

          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.

    • Bro666@lemmy.kde.socialM
      12·
      26 days ago

      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.

      • the tower fairy@chaos.social
        17·
        26 days ago

        @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.

        • Bro666@lemmy.kde.socialM
          8·
          26 days ago

          KDE is not introducing a new notification framework. It is using something that already exists, so still barking up the wrong tree.

    • unexpectedteapot@social.linux.pizza
      6·
      26 days ago

      @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.