Projects/Snorenotify: Difference between revisions

From KDE TechBase
(Fix lists)
Line 1: Line 1:
= Backends =
= Backends =


- [[Projects/Snorenotify/Windows-Toast-Notification | Windows Toast Notification]]
* [[Projects/Snorenotify/Windows-Toast-Notification | Windows Toast Notification]]
 
* OSX Notification Center
- OSX Notification Center
* Free Desktop Notifications
 
* Growl
- Free Desktop Notifications
* Snarl
 
* [[Projects/Snorenotify/Integrated-Notification-Backend | Integrated Notification Backend]]
- Growl
* System Tray
 
- Snarl
 
- [[Projects/Snorenotify/Integrated-Notification-Backend | Integrated Notification Backend]]
 
- System Tray


= Secondary Backends =
= Secondary Backends =


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


= Screenshots =
= Screenshots =
Line 34: Line 28:
Basically all backends when used locally (some support forwarding) should be relatively safe.
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.
* 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.
* Windows Toast, SnoreToast is a command line application and the information is passed as arguments.
- Freedesktop, local inter process communication (dbus) is used.
* Freedesktop, local inter process communication (dbus) is used.
- Snarl, local inter process communication is used.
* Snarl, local inter process communication is used.
- Growl, local network communication, [http://www.growlforwindows.com/gfw/help/gntp.aspx#security MD5 encryption is supported].  
* Growl, local network communication, [http://www.growlforwindows.com/gfw/help/gntp.aspx#security MD5 encryption is supported].  




Line 44: Line 38:
== Secondary Backends ==
== Secondary Backends ==


- Toasty is **UNSAFE**, it is using http to communicate with a server.
* Toasty is **UNSAFE**, it is using http to communicate with a server.
 
* Notify My Android is using https to communicate. [http://notifymyandroid.com/privacy.jsp Notify My Android Privacy]
- Notify My Android is using https to communicate. [http://notifymyandroid.com/privacy.jsp Notify My Android Privacy]
* Pushover is using https to communicate. [https://pushover.net/faq#security Pushover Security ]
 
- Pushover is using https to communicate. [https://pushover.net/faq#security Pushover Security ]

Revision as of 14:07, 24 August 2015

Backends

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