Integrate with aggregator module

cwgordon7 - August 4, 2008 - 00:43
Project:Bot
Version:6.x-1.x-dev
Component:Code
Category:feature request
Priority:normal
Assigned:cwgordon7
Status:needs review
Description

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. :)

AttachmentSize
bot_aggregator.patch5.18 KB

#1

cwgordon7 - August 4, 2008 - 01:22

Kindly ignore last patch. :)

AttachmentSize
bot_aggregator.patch 5.33 KB

#2

cwgordon7 - August 4, 2008 - 01:27

Even better, ignore that one, too.

AttachmentSize
bot_aggregator.patch 5.28 KB

#3

cwgordon7 - August 4, 2008 - 01:35

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

#4

Rob Loach - August 4, 2008 - 03:56

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

#5

Morbus Iff - August 4, 2008 - 12:51

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.

#6

cwgordon7 - August 5, 2008 - 05:39

Rerolled to work.

AttachmentSize
bot_aggregator.patch 5.44 KB

#7

mfb - June 5, 2009 - 17:26

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.

 
 

Drupal is a registered trademark of Dries Buytaert.