Skip to content

Releases: stwalkerster/eyeinthesky

Version 2.4

11 Apr 18:02
v2.4
Compare
Choose a tag to compare
  • Regular expression nodes (including user, page, summary, etc) now have the ability to be set case-insensitive. This is only currently configurable by XML.
  • It's now possible to unsubscribe from an individual stalk when subscribed to the whole channel.
  • stalk clone #source source-tag dest-tag clones source-tag in channel #source to a new stalk dest-tag.
  • It's possible to store parts of stalk trees in Phabricator Pastes now with the external node.
  • Added multi-channel watches, meaning it's now possible to watch another wiki on the same IRC server's RC feed, settable with the stalk watchchannel command. Specifying the API for this is possible in two different ways in config - either by pattern or a mapping.
  • Basic numeric nodes - diffsize returns the delta size of the revision, pagesize returns the absolute size of a page, number returns a static number, and the infix compares two numbers with an operator returning the boolean result of the comparison.
  • Email notifications now contain the last update time and the watch channel in the stalk configuration section.
  • Expiries can now be configured with a specific duration from now instead of an absolute end timestamp.
  • Dynamic expiry - stalks can be configured to instead expire a specific period of time after the last trigger.
  • Stalk creation time is now tracked.
  • AbuseFilter hits now generate a URL to the AbuseLog for rapid investigation
  • New email header including stalk data

Bug fixes

  • Various parse fixes for log events.
  • Fix some exceptions which occur when running a command on missing stalks
  • Allow unsetting the stalk expiry date from the IRC interface

Maintenance

  • Updated libraries:
    • Stwalkerster.IrcClient (8.0.30-beta => 8.1.40-beta)
    • Stwalkerster.Bot.CommandLib (10.0.19-beta => 13.0.45-beta)
    • Split MediaWiki code into Stwalkerster.MediaWikiLib (2.6.17-beta)
  • Updated to .NET 4.5.2

Version 2.3

11 Apr 17:59
v2.3
Compare
Choose a tag to compare
  • Specifying XML for stalks has changed. The new xml command will cache the provided xml and store it. The stalk set <flag> xml command now takes no arguments, but reads from the XML cache
  • Multi-channel has arrived! It's now possible to set up the bot to join several channels with a distinct configuration in each.
  • User registration has arrived! It's now possible for users to register themselves to be assigned flags in channels, and to receive alert emails for activations of those stalks. Users can be assigned flags locally in a single channel, or globally across all channels.

Minor new functionality

  • Add the option to customise the prefix of email subject lines
  • Add "enable", "enabled", "disable", and "disabled" to allowable boolean keywords
  • New configuration option to hold a privacy policy URL

Maintenance

  • Updated libraries:
    • Stwalkerster.IrcClient (7.0.17-beta => 8.0.30-beta)
    • Stwalkerster.Bot.CommandLib (9.0.13-beta => 10.0.19-beta)
  • Performance tweaks to RC Handler
  • The mail flag on stalks has been removed in preference of subscriptions

Version 2.2

23 Apr 20:05
v2.2
ef6888a
Compare
Choose a tag to compare
  • Add stalk templates, with dynamic commands for instantiation
  • Remove acc command
  • Remove quick command
  • Split out alerting templates to separate configuration file
  • Add trigger count to stalks
  • Add email threading for stalk alert emails
  • Add log event parsing
  • Convert and and or nodes to support any number of children
  • Add page-is-in-category stalk node incategory
  • Add log type stalk node log
  • Add x-of stalk node, matching between a minimum and maximum number of children
  • Support more values of boolean

v2.1

22 Mar 01:12
v2.1
Compare
Choose a tag to compare

New <usergroup /> stalk node

v2.0

17 Mar 01:08
v2.0
688692e
Compare
Choose a tag to compare

This release is an almost-complete rewrite of the bot.

A new IRC library and command framework has been brought across from helpmebot/helpmebot, and a lot of the EITS-specific code has been refactored to be more testable.

The result is a more-easily configurable and easier to maintain bot that has a more general use.