Projects/Snorenotify: Difference between revisions
TheOneRing (talk | contribs) m (TheOneRing moved page Snorenotify to KDE TechBase:Projects/Snorenotify) |
TheOneRing (talk | contribs) m (TheOneRing moved page KDE TechBase:Projects/Snorenotify to Projects/Snorenotify) |
(No difference)
|
Revision as of 11:33, 24 August 2015
- Backends
- 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
- Windows Toast Notifications
[![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)
- 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)
- 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](http://www.growlforwindows.com/gfw/help/gntp.aspx#security).
- 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)