Hi Michael, The option to enable or disable the track downloads feature is found on the Analyze Tab -> Standard Stats (for free users) or Total Stats Pro (for pro users) by clicking the checkbox "Item enclosure downloads (podcast downloads)" It's a new option that we added with our Stats redesign at the beginning of the month and, like all of our services, is an opt-in feature by the publisher.
Just to make sure, I also verified that Fireant was included in the list of podcatchers that were tested during QA. But if you see an outstanding issues, we'd be glad to look into it and do whatever we can to assist in resolving it. For this particular feed, we just tested on the latest version of Fireant on Mac and Windows XP and were able to subscribe to the feed and receive the media downloads just fine. Let us know if you see anything different. We definitely understand your concern on the format of the rewritten urls. Primarily, we always want to make sure that everything we do is standards compliant. This particular convention is same one that we've used for tracking clickthroughs on items for the last couple of years. Historically, it has worked well but we can definitely see where this can be confusing (even to us at times :) in the sense of url's that link to media files. On the other hand, manipulating the query parameters to meet logic that depends on the extension at the end of a link can also be considered to have a negative impact as it masks deeper problems in client code that prevent it from working correctly with standards based urls. Testing revealed that most clients handled things correctly and the couple of issues we received were followed up with close work with the client software author to make sure the issues are understood and resolvable. Nevertheless, we definitely give the feedback we receive either way much importance and will take it into account. I hope this explains the thinking behind the way its working now and look forward to any suggestions. Thank you so much for using feedburner and we're always open to your ideas. Jessie Chavez Feedburner Engineering Team --- In videoblogging@yahoogroups.com, "Michael Sullivan" <[EMAIL PROTECTED]> wrote: > > josh, i did in my message. i have been referring to this example: > http://feeds.feedburner.com/spainfulfilms > > > On 3/16/06, Joshua Kinberg <[EMAIL PROTECTED]> wrote: > > > > Could you give me a RSS URL that uses this? > > I have never encountered this issue here. We should still be able to > > download the files using that URL convention. > > > > -Josh > > > > > > On 3/16/06, Andreas Haugstrup <[EMAIL PROTECTED]> wrote: > > > On Thu, 16 Mar 2006 15:17:15 +0100, Michael Sullivan > > > <[EMAIL PROTECTED]> wrote: > > > > > > > ie. http://feeds.feedburner.com/spainfulfilms.mp4?d=25 > > > > via: > > > > http://feeds.feedburner.com/spainfulfilms > > > > > > > > This feed doesnt work in FireAnt or any aggregator that currently uses > > > > typical file extention detection of media format (since often mime > > types > > > > in > > > > feeds are not accurate). > > > > > > > > Should'nt we get feedburner to modify it so its more cross-compatible > > > > (such > > > > as ending the url with .ext)? This is annoying and even though not > > > > technically wrong to do on feedburner's part, they should have taken > > this > > > > issue into consideration before breaking direct media urls like > > this. I > > > > dont want to write new code to handle 'special' direct media url > > formats. > > > > > > The file name still has a .mp4 extenstion. The ?id=25 is the query > > string. > > > Without knowing for sure I'm guessing that FireANT fails because it > > > doesn't follow redirects (the URL responds with a 302 header that points > > > to the original video URL. > > > > > > So Feedburner has a correct filename ending in .mp4 and they are even > > > sending the correct mime type (video/mp4). If an aggregator doesn't work > > > with these URLs the aggregator needs to use a proper HTTP library. > > Setting > > > up limitations like "video files must have a file extension" and "you > > > cannot use redirects" are more than a little silly. > > > > > > This isn't a case of having to write special software to handle these > > > special URLs. These are normal URLs and if the software was using HTTP > > > correctly (following redirects, breaking apart filename from query > > string > > > before checking for file extension) there would be no problems. > > > > > > -- > > > Andreas Haugstrup Pedersen > > > <URL: http://www.solitude.dk/ > > > > Commentary on media, communication, culture and technology. > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Yahoo! Groups Links > > > > > > > > > > > > > > > > > -- > Sull > http://vlogdir.com > http://SpreadTheMedia.org > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/videoblogging/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
