Why did adding notification support in my app label it potentially unsafe?

Dec 3, 2025 Closed
A

I recently added notification support (to warn against extreme weather events) in my app using the freedesktop protocol update to version 1.3 · flathub/io.github.archisman_panigrahi.typhoon@b2f17f7 · GitHub

"--talk-name=org.freedesktop.Notifications"

Since then, flathub labeled [my app](https://flathub.org/en/apps/io.github.archisman_panigrahi.typhoon) as “potentially unsafe, uses non-portal services”. Previously it was “Probably safe”.

I don’t see why enabling notifications will make the app unsafe.

Am I missing something? It would be very helpful if someone can clarify.

I would like to know what all changes I should make so that the app is percieved as safe by flathub, while retaining the notification feature.

C

Applications should use the Notification Portal instead of talking to the notification server directly.

I assume that using the notification DBus is treated like any other DBus access, since a proper portal exists.

A

In that case, is "--talk-name=org.freedesktop.Notifications" not necessary anymore?

C
Replying to #3

If you use the portal, the you shouldn’t need that permission anymore.