[development] stripping tags during aggregation?

[Larry Garfield]

Importing feeds as nodes would also offer a very clean and flexible way of 
pushing data between sister-sites.  I've never had much luck with pub/sub, 
but a feed-based solution would offer a lot of flexibility.  (Imagine 
building your outgoing feed using Views.  You could export virtually any 
combination of nodes for a sister site to consume into mirrored nodes as 
well.)

On Wednesday 27 June 2007, Ashraf Amayreh wrote:
> I chose to bring items in as nodes because then you can utilize so many of
> the node features like editing an aggregated node, using all modules that
> affect nodes, ability to attach comments, user ownership, categorizing them
> through the taxonomy system, publishing, moderation, revisions (although I
> don't implement revisions yet but it sounds intriguing to play on this
> thought), sticky, etc.
>
> This is what popped to mind in an instant, I could also see integration
> with other node oriented modules such as views and some vague  and
> definitely undeveloped CCK integration, path-auto comes to mind as well.
> Aggregating feeds in a different way would make them a total foreign entity
> that needs special hooks, special handling, new modules that utilize a new
> API, I'm just stating the thoughts I had when I reached the conclusion to
> aggregate them as nodes.
>
> Thanks for the suggestion on how to handle input. Filtering input through
> the node filter system sounds ideal. Never would have reached this on my
> own.
>
> I'll take the opportunity to ask if there are any developers here
> interested in co-maintaining the aggregation module with me, you can drop
> me a line off list. I really need extra skilled people here so as to not
> screw up my module :P Just go take a look at the pending patches and
> feature requests and your going to drool at the beauty ;) You'll also know
> why a
> co-maintainer sounds like a good idea. Sponsors don't need any invitations,
> they're always welcome hehe :P
>
> On 6/27/07, Bèr Kessels <ber at webschuur.com> wrote:
> > Op woensdag 27 juni 2007, schreef Morbus Iff:
> > > I'll support an API that lets me choose
> >
> > feedparser is no more then an API. with pretty good storage of links (I
> > would
> > like to see it coupled to link bundle to allow scheduled checks for
> > linkrot/301s etc).
> >
> > But I don't see why the database model would prevent you from linkrot.
> >
> > In any case: feedparser is an API; you can bolt your own stuff on top,
> > incl
> > the default Drupal feed storage/presentation. But also including nodes,
> > wich
> > hands you all the goodness of nodes, such as, but certainly not limited
> > to,
> > stripping tags based on input filters.
> >
> > Bèr
> > --
> > Drupal, Ruby on Rails and Joomla! development: webschuur.com | Drupal
> > hosting:
> > www.sympal.nl


-- 
Larry Garfield			AIM: LOLG42
larry at garfieldtech.com		ICQ: 6817012

"If nature has made any one thing less susceptible than all others of 
exclusive property, it is the action of the thinking power called an idea, 
which an individual may exclusively possess as long as he keeps it to 
himself; but the moment it is divulged, it forces itself into the possession 
of every one, and the receiver cannot dispossess himself of it."  -- Thomas 
Jefferson