[licq-im/licq] 572393: Added functions to get message from user events th...

Branch: refs/heads/master
Home:   https://github.com/licq-im/licq

Commit: 57239376691bb0e584f9be0d999f89652e71a8bd
    https://github.com/licq-im/licq/commit/57239376691bb0e584f9be0d999f89652e71a8bd
Author: Anders Olofsson <[email protected]>
Date:   2011-04-09 (Sat, 09 Apr 2011)

Changed paths:
  M licq/include/licq/userevents.h

Log Message:
-----------
Added functions to get message from user events that were it was missing.


Commit: 4486a1d5206b59bfa8924eda550d730a6d9b6dc5
    https://github.com/licq-im/licq/commit/4486a1d5206b59bfa8924eda550d730a6d9b6dc5
Author: Anders Olofsson <[email protected]>
Date:   2011-04-09 (Sat, 09 Apr 2011)

Changed paths:
  M licq/cmake/LicqCommonCompilerFlags.cmake
  A licq/include/licq/filter.h
  M licq/src/CMakeLists.txt
  M licq/src/daemon.cpp
  A licq/src/filter.cpp
  A licq/src/filter.h
  M licq/src/licq.cpp

Log Message:
-----------
Added a filter for user events

The filter can match events based on protocol, event type or message contents.
Filter rules can be disabled/enabled without removing them from the
configuration. Message contents is matched with a regular expression.
A match can allow the event, just drop it, or log the event as normal without
notifying the user.
Only events from unknown contacts are filtered, contacts in the list are
always trusted. If no rule applies, the default is to accept the event.

The default configuration is set to drop a few spam messages that I have seen
repeatedly the last months. It will also silence (but log) any authorization
request containing a URL as those are generally also spam.

Limitations:
- Currently there is no GUI, only the daemon logic and a configuration file.
- The filter does not understand non-ascii characters making the rules for
  cryllic characters very unreadable.
- Counters should be added to let the user see which rules get matches.


Compare: https://github.com/licq-im/licq/compare/96ef0f1...4486a1d