Projects/Snorenotify

From KDE TechBase
  1. Backends

- Windows-Toast-Notification

- OSX Notification Center

- Free Desktop Notifications

- Growl

- Snarl

- Integrated-Notification-Backend

- System Tray

  1. Secondary Backends

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

  1. Screenshots
    1. Windows Toast Notifications
      1. Windows 10

[![Windows 10](http://patrick.von-reth.de/other/snore/wiki/screenshots/windows-toast-win10.png)](http://patrick.von-reth.de/other/snore/wiki/screenshots/windows-toast-win10.png)

    1. Integrated notifications backend

[![Integrated notifications backend](http://patrick.von-reth.de/other/snore/wiki/screenshots/snore-win10.png)](http://patrick.von-reth.de/other/snore/wiki/screenshots/snore-win10.png)

  1. Security
    1. 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](http://www.growlforwindows.com/gfw/help/gntp.aspx#security).


    1. 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](http://notifymyandroid.com/privacy.jsp)

- Pushover is using https to communicate. [Pushover Security](https://pushover.net/faq#security)