RSS

This is a concept that hit me last night.

One of the issues we have with current Aggregator is that after a certain number of feeds, it starts to have problems finishing its cron cycle.

Part of this is caused by the fact that Aggregator does three actions during cron:

• Get feed
• Validate feed
• Parse feed

Really, aren't only the first two necessary during the cron run? Couldn't we save some cycles and boost performance by delaying the parsing stage until the data was requested by a user-initiated function (like an Aggregator block load)?

Space is open! If you're interested in presenting please add a comment or contact Boris or myself. It can be as informal as a 15 minute review of your experience with a module. We encourage non-technical presentations on how Drupal did or didn't meet expectations, as well as the presentations only a developer could love.

May 2007 Meeting

The May Drupaliers meeting will either Thursday May 24th or Thursday May 31st.
Tentative Speakers are:
- rickvug: Design Implementation

Has anyone had any success getting bloglines to read the myunread feed (or any of the personalized tracker feeds)? I understand authentication is needed, and I have tried the form:

http://myaccount:mypass@groups.drupal.org/group/myunread/feed

but no luck. It just says "No feeds were found. Please verify that the website publishes an RSS feed."

Anyone´s knows what´s the module used to get these < ahref="http://drupal.org/node/63589">feeds?

ie:
http://drupal.org/security/rss.xml
http://drupal.org/taxonomy/term/14/0/feed

There are different formats of the feed...

Thanks!

Rosamunda

Hello, all,

Is anybody familiar with an app named Gregarius? It's a standalone app that describes itself as a"Free, Web-based feed aggregator"

From the Features List:

*  Completely web-based and runs on your web server
* Supports RDF, RSS, ATOM feeds
* Imports and exports OPML
* Simple, password-protected, web-based administration and configuration
* AJAX powered tagging of feeds and items
* Supports themes and plugins
* Search in your feeds
* Basic i18n support

http://www.iptc.org/NAR/

Greetings, fellow standards junkies:

I stumbled across the site above while looking to see what was being done with aggregation these days. For anyone who's ever given any thought to how much IE6 is to CSS like RSS 2.0 is to aggregation, it might make sense if I admitted I originally bookmarked the site above for future review and subconsciously repressed the memory as a hoax intended to torment me.

If it was some big deal, why wasn't anybody talking about it? Little did I know...

To be completely serious, though, I've been thinking a lot these past couple of months about what could be done to make Drupal more attractive to publishers looking to convert their operations to the web or folks looking to create web-based publications, and there's been growing interest in the subject. Given the spike in growth seen in the community following the DeanSpace/CivicSpace project and how popular Drupal has become with non-profits and the like, I've been thinking a complimentary project to the ecommerce suite aimed at publishers might both increase Drupal's popularity as a commercial platform and drive new business to contractors.

Is it just me, or is RSS broken? First Wizz RSS 2.1.4 (Firefox) wouldn't read my feeds, but then I tried to set them up in a new drupal installation via aggregator and they aren't working, there, either. (The RSS-feed from Views Developers seems to be broken, due to "401 Unauthorized".) -- If this had been mentioned elsewhere, I hadn't seen it, so I figured I should say something, even if it seems a little wierd that I'm the only one who's noticed...

For newcomers to the RSS topic I dug out an old thread from the Drupal mailing list which discusses the use of MagpieRSS library in Drupal. Interesting read - it was before my time.

http://lists.drupal.org/archives/development/2004-07/msg00400.html

Drupal currently lacks any easy way for contributed modules to access the additional fields found in "enhanced" RSS feeds. Such fields include the enclosure tag which is used for podcasting and videocasting.

It has been suggested on IRC #drupal that the aggregator.module should be broken down to form a feedparser.module which does the grunt work and the aggregator.module which handles the management of the feed items.

The feedparser.module would simply accept a feed url, fetch the feed XML, parse it and normalize the data, then finally return an array of items.

An initial suggestion for the feedparser library can be found here in Ber Kessels's sandbox.