How does feedburner track RSS stats any differently than typo could? Don't
they still have the issues of knowing who is actually reading, dealing with
counting automated pulls from feedreaders, etc?
If feedburner has solved the problem, it may be the way to go (instead of
reinventing the wheel). But I don't know that they have.
-Ryan
On 8/29/05, Waylan Limberg <waylan at gmail.com> wrote:
>> I've been reading this list for a couple weeks now, and found the
> stats on rss reeds dicussion interesting. Then this morning I was
> reading something elsewhere and it hit me. Perhaps the best sotution
> is to not create a half-working product but suggest that those who
> really want to track stats on feeds use feedburner. Have typo generate
> the feed as normal, but only let the feedburner bot through,
> redirecting everyone else to the feedburner feed. Then check into your
> feedburner account and get the stats whenever you want.
>> Just a thought.
>> On 8/24/05, Ian Holsman <lists at holsman.net> wrote:
> > William A. Carrel wrote:
> > > I imagine you'd achieve this by fitting some magic javascript or image
> > > into the article in the RSS feed. Really this would track the same way
> > > as article views and probably could be implemented fairly easily (and
> > > non-invasively) using the filter framework that Scott Laird has been
> > > working on.
> >
> > there are a couple of issues with RSS feeds.
> >
> > 1. some don't show HTML, they just do text
> > 2. most don't pass cookies, or Referrers.
> > 3. most are on a periodic schedule so your not actually tracking people
> > viewing
> > 4. people's IP numbers change
> > 5. multiple people may be viewing your RSS feed (bloglines for example)
> > 6. some/most of them don't run javascript (intentionally)
> >
> > so in order to start tracking things you can't just use the typical
> > webbug/1x1 gif you would normally.
> >
> >
> > my only suggestion is that you change the URL you offer to include the
> > cookie of the viewer
> > so the URL displayed in the HTML/page would change from
> > http://feh.holsman.net/xml/rss/feed.xml> >
> > to
> > http://feh.holsman.net/xml/rss/A1231BC01231.xml> >
> > would (via a rewrite rule ) would get mapped to feed.xml
> > and aritcles in the actual RSS feed would have similar encodings.
> > (meaning they would be dynamic)
> > this would help with 2,4 and 6.
> >
> > your Stat generator would need to also look at people's useragents, as
> > they have subscriber numbers in them as well.
> >
> > >
> > > On Aug 21, 2005, at 8:08 PM, Jeff Casimir wrote:
> > >
> > >> Are you saying that you want to track when users access your RSS
> > >> feed? That sounds like an interesting challenge. I think the
> > >> tracking would have to come from the controller that renders the XML.
> > >> For Typo applications, this would mean adding a method call within
> the
> > >> controller if you want to use railstat. Of course first I'll have to
> > >> figure out the railstat side of things. It shouldn't be hard, but I
> > >> haven't had much dev time in the last week. I will keep it at the
> > >> forefront of my to-do list this week.
> > >>
> > >
> > >> Kevin Ballard wrote:
> > >>
> > >>
> > >>> RailStat sounds cool, but since it works by having the browser load
> > >>> a resource (either JS or image), it seems to me it can't track RSS
> > >>> feeds. Do you have any sort of solution for that?
> > >>>
> > >>> On Aug 19, 2005, at 7:01 PM, Jeff Casimir wrote:
> > >>>
> > >>>
> > >>>> I've been working with Luben, the guy who started railstat, to make
> > >>>> it...ummm...better. It needs a lot of work before I would call it
> > >>>> ready for widespread deployment. Since his 0.1 gem creation I have
> > >>>> done a lot of work on the code to...
> > >>>> - Support Windows
> > >>>> - Support PostgreSQL (aka anything not-MySQL)
> > >>>> - Support a server running as local host
> > >>>> - Optimizing some of the SQL queries
> > >>>> - Refactoring. Refactoring. Refactoring.
> > >>>>
> > >>>> I took a day off to go to the beach, but I should be back to work
> > >>>> on it tonight or tomorrow. Expect release(s) next week.
> > >>>>
> > >>>
> > >>>
> > >>>
> ------------------------------------------------------------------------
> > >>>
> > >>> _______________________________________________
> > >>> Typo-list mailing list
> > >>> Typo-list at rubyforge.org> > >>> http://rubyforge.org/mailman/listinfo/typo-list> > >>>
> > >>>
> > >>
> > >> _______________________________________________
> > >> Typo-list mailing list
> > >> Typo-list at rubyforge.org> > >> http://rubyforge.org/mailman/listinfo/typo-list> > >>
> > >
> > > _______________________________________________
> > > Typo-list mailing list
> > > Typo-list at rubyforge.org> > > http://rubyforge.org/mailman/listinfo/typo-list> > >
> >
> > _______________________________________________
> > Typo-list mailing list
> > Typo-list at rubyforge.org> > http://rubyforge.org/mailman/listinfo/typo-list> >
>>> --
> ----
> Waylan Limberg
>waylan at gmail.com>> _______________________________________________
> Typo-list mailing list
>Typo-list at rubyforge.org>http://rubyforge.org/mailman/listinfo/typo-list>-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/typo-list/attachments/20050829/ef47cd0b/attachment-0001.htm