Projects/Snorenotify: Difference between revisions
< Projects
TheOneRing (talk | contribs) |
TheOneRing (talk | contribs) |
||
| (6 intermediate revisions by the same user not shown) | |||
| 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://hannah.von-reth.de/snorenotify/doc/latest/ here]. | |||
= Source Code = | |||
* [https://phabricator.kde.org/diffusion/SNORENOTIFY/repository/master/ Git Repository] | |||
* [http://download.kde.org/stable/snorenotify/ Tarballs] | |||
- | = Projects using Snorenotify = | ||
* [http://www.quassel-irc.org/ Quassel IRC] | |||
* [http://www.tomahawk-player.org/ Tomahawk] | |||
= Backends = | |||
- [[Projects/Snorenotify/Integrated-Notification-Backend | Integrated Notification Backend]] | * [[Projects/Snorenotify/Windows-Toast-Notification | Windows Toast Notification]] | ||
* OSX Notification Center | |||
* Free Desktop Notifications | |||
* Growl | |||
* Snarl | |||
* [[Projects/Snorenotify/Integrated-Notification-Backend | Integrated Notification Backend]] | |||
* System Tray | |||
= Secondary Backends = | = Secondary Backends = | ||
* Windows Phone - Toasty | |||
* Android - Notify my Android | |||
* Android and IOS - Pushover | |||
* Playback of sound filles | |||
= Screenshots = | = Screenshots = | ||
| Line 34: | Line 42: | ||
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. | |||
* 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, [http://www.growlforwindows.com/gfw/help/gntp.aspx#security MD5 encryption is supported]. | |||
| Line 44: | Line 52: | ||
== Secondary Backends == | == Secondary Backends == | ||
* 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] | |||
* Pushover is using https to communicate. [https://pushover.net/faq#security Pushover Security ] | |||
Latest revision as of 18:49, 26 January 2016
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.
Source Code
Projects using Snorenotify
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