Ok, it would be completely awesome if, on IRC, we could syndicate content from sources such as recent drupal core CVS commits or recent drupal planet posts. This patch allows the bot to integrate with the aggregator module in this way - you can choose which categories get displayed through IRC, as well as the channels they get displayed in.

Credit for the idea goes to RobLoach. :)

CommentFileSizeAuthor
#6 bot_aggregator.patch5.44 KBcwgordon7
#2 bot_aggregator.patch5.28 KBcwgordon7
#1 bot_aggregator.patch5.33 KBcwgordon7
bot_aggregator.patch5.18 KBcwgordon7

Comments

cwgordon7’s picture

cwgordon7 commented
StatusFileSize
new bot_aggregator.patch5.33 KB

Kindly ignore last patch. :)

cwgordon7’s picture

cwgordon7 commented
StatusFileSize
new bot_aggregator.patch5.28 KB

Even better, ignore that one, too.

cwgordon7’s picture

cwgordon7 commented

Actually, as RobLoach pointed out, he does not deserve any credit for this, it was Sirkitree's idea.

robloach’s picture

robloach
he/him
commented

This is 100% awesomeness. I wish we could tag Drupal issue queues.....

morbus iff’s picture

morbus iff
they/them
commented

As mentioned to a few folks on IRC, I'll consider this patch (for core, certainly) once I see the results of Aron's GSOC 07 aggregator rewrite.

cwgordon7’s picture

cwgordon7 commented
StatusFileSize
new bot_aggregator.patch5.44 KB

Rerolled to work.

mfb’s picture

mfb
they or he
commented

I just wrote a tiny bot_aggregator module to get search.twitter.com atom feeds into IRC via aggregator and bot modules. There's just a couple of extras this patch would need to support that use case:

  1. Option to use cron_fastest hook for updates every 15 seconds (note, aggregator module doesn't make it easy to get a refresh time of 0 seconds into the aggregator_feed table),
  2. Assemble the bot_message via a themeable function so I can customize the message to add the twitter user's name,
  3. And, to avoid problems with channel flooding for busy conference hashtags I had to limit the messages to N per cron_fastest run. In my case I used a LIMIT clause on the db query, and then some way to record which items have already been sent, e.g. saving the timestamp of the last sent item.
morbus iff’s picture

morbus iff
they/them
commented

A revised version of this has been committed:

* bot_aggregator.module added (thanks cwgordon7/snufkin). Additions:
- Configuration has been moved to the feed config form, not our own.
- Different feeds can now be sent to different channels, based on config.

mfb: 1) and 3) are done. 2) isn't currently possible.

morbus iff’s picture

morbus iff
they/them
commented
Status: Needs review » Fixed

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.