Projects/Snorenotify: Difference between revisions

From KDE TechBase
 
(4 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 =
= Backends =



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

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