Revision as of 14:46, 24 August 2015

Support

If you need support on how to use Snorenotify you can reach out to the developers using the mailing list or IRC joining #Snorenotify on freenode or using the Web chat .

The current API documentation can be found here.

Backends

Windows Toast Notification
OSX Notification Center
Free Desktop Notifications
Growl
Snarl
Integrated Notification Backend
System Tray

Secondary Backends

Windows Phone - Toasty
Android - Notify my Android
Android and IOS - Pushover
Playback of sound filles

Screenshots

Windows Toast Notifications

Windows 10

Integrated notifications backend

)

Security

Backends

Basically all backends when used locally (some support forwarding) should be relatively safe.

Snore is build in and no information is passed to outside applications.
Windows Toast, SnoreToast is a command line application and the information is passed as arguments.
Freedesktop, local inter process communication (dbus) is used.
Snarl, local inter process communication is used.
Growl, local network communication, MD5 encryption is supported.

Secondary Backends

Toasty is UNSAFE, it is using http to communicate with a server.
Notify My Android is using https to communicate. Notify My Android Privacy
Pushover is using https to communicate. Pushover Security

@@ Line 1: / Line 1: @@
+= Support =
+If you need support on how to use Snorenotify you can reach out to the developers using the [https://mail.kde.org/mailman/listinfo/snorenotify mailing list] or IRC joining [irc://irc.freenode.net/snorenotify #Snorenotify] on freenode or using the [http://webchat.freenode.net/?channels=snorenotify Web chat] .
+The current API documentation can be found [http://api.kde.org/playground-api/libs-apidocs/snorenotify/html/index.html here].
 = Backends =