Slashdot Mirror


Best Practice For Retiring RSS Feeds?

GBJ writes "I work for an organisation that runs seasonal online competition events. Each event has its own news feed which becomes obsolete shortly after the event finishes. We're still getting RSS requests for some events as far back as 2004. I'd like to close a few thousand old feeds and remove the resource hit they cause, but I'm not sure what is the best approach. Currently I'm considering just returning a 404, but I have no idea if there is a better way to handle this. Uncle Google hasn't turned anything up yet, but sometimes it's hard to find something when you don't know what it's called ..."

12 of 71 comments (clear)

  1. 301 by hansamurai · · Score: 5, Insightful

    You should be able to do a 301 redirect to maybe some generic feed that just has one entry that says "This feed is out of date, please use try these feeds instead." Or whatever you want to let them know.

  2. Something simple by IMarvinTPA · · Score: 4, Insightful

    The most appreciative thing you could do for the preservation of history is to place static simple RSS files at those addresses that include a link to your archives for the event.

    IMarv

  3. HTTP 410 Gone, possibly with archives elsewhere by Millennium · · Score: 2, Insightful

    HTTP 410 is better than HTTP 404 in this case; Uncle Google and the like have a better understanding of what it means.

    If you have a version of the feed that covers the whole event from start to finish, you might also want to offer a static version of that for download as an archive (but if you do this, put it on a different URL from where the feed used to be). This isn't strictly necessary, but I can see scenarios where people might appreciate being able to get at the feed's contents again.

  4. Aggregate? by Redfeather · · Score: 3, Insightful

    Are there more than one contest going at once, that there's a need for multiple feeds? Or, more appropriately, can some of this content not be removed completely? Keeping a full feed archive seems a bit of overkill, especially for closed events from five years ago. Why not PDF the event archive for downloading and keep a single feed for active items? Overpreparation is a growing problem I'm seeing on the web. Far too few people/events/businesses are prepared to minimize anything for the sake of optimization.

    --
    Those things you're doing with that stuff you just bought? That's not what it's for! -
  5. Re:reuse? by Albanach · · Score: 2, Insightful

    Why not reuse the same feed over and over again each year?

    He mentioned a couple of thousand old feeds. Either he's been serving feeds since the days when RSS was chiseled by hand into stone tablets, or he has distinct feeds which run concurrently - in which case reusing isn't going to work.

  6. Redirect to a 'new events' feed by Rix · · Score: 2, Insightful

    This seems like more of an opportunity than a problem. People haven't deleted the feed, so they obviously still want to hear from you. Redirect requests to the 'dead' feeds to a general feed that announces new events.

  7. Re:but then you loose the traffic by Razalhague · · Score: 3, Insightful

    Dumping them with a 410 is a great way to loose your traffic.

    I'd like to close a few thousand old feeds and remove the resource hit they cause...

  8. Re:Discontinued Notice Increased Traffic by Yaur · · Score: 3, Insightful

    This seems like the way to go. Assuming that your website drives revenue somehow, throwing away traffic is not smart.

  9. Re:but then you loose the traffic by Blakey+Rat · · Score: 2, Insightful

    Anyone who runs a website would be extremely short-sided to discourage traffic in any way. What I'd do is create a new, more generic, news feed and redirect all the other feeds to it. The few people who simply forgot they were subscribed to the 2004 feed will either realize their mistake and drop off, or be still interested in your new events and stay on. If you just make the feeds disappear, those users disappear as well.

    Despite what the summary says, I severely doubt that hits on old feeds are any kind of huge traffic drain. If it *truly* is, you could also redirect them to FeedBurner, save the traffic, and possibly monetize them at the same time.

  10. Re:Retiring feeds by Larryish · · Score: 3, Insightful

    Forward them to a page listings current feeds, possibly with custom tailored advertisement-style links to events or other websites in your network.

    Never waste traffic. At the end of the day, traffic is KING.

  11. Well by coryking · · Score: 2, Insightful

    This is Slashdot, and I guess some here view the world in some kind of mechanical way free from the constraints of the real world. So yeah, if he wants to tell them to fuck off and feed their newsreader streaming crap from /dev/urandom, by all means do so. But that is a child's thing to do. Adults view the world different.

    A mature adult would see that the cost of bandwidth is minimal and the untapped potential in all those people sitting on ancient feeds outweigh the potential costs. A mature adult who strives to have a successful website would find a way to tap that potential, possibly by redirecting the feed to something that nudges them to the good stuff.

    But no, go ahead and stream your fucking mp3s to their newsreader. That will teach them to ever cross path your mad skillz. It will teach them so good they'll never visit your site again, never click your ads and never buy your services. Who needs their money, right? After all, rent is cheap living in the basement!

    (ps: booya)

    1. Re:Well by Zerth · · Score: 2, Insightful

      Interesting that you associate blind commercialism with maturity and bandwidth that has no evidence of human attention with "untapped potential". Sometimes the bandwidth use is just the result of automated feedgrabbers who, like you, believe bandwidth is so cheap as to be free at any magnitude and so continue to download anything that is available in vague hope of hitting paydirt instead of using analytics to guide them to efficient use of capital.

      The article made it clear the feeds have been dead, any possible readers unwanted, and the bandwidth could be put towards current feeds that demonstrate ROI(possibly even of a *gasp* nonfinancial nature). Bandwidth, while minimally expensive is not infinitesimally so. If there are no eyeballs there is no chance for ROI, move your capital elsewhere.

      PS Did somebody DDOS your unmonitored feed aggregator after asking you to knock it off, or are you merely angry at your lack of interest in those expired domains you got at auction?