http://viosym.blogsome.com/2005/12/19/who-moved-my-rss-feed/ Just another WordPress weblog Thu, 10 Dec 2009 22:09:05 +0000 http://wordpress.org/?v=1.5.1-alpha http://viosym.blogsome.com/2005/12/19/who-moved-my-rss-feed/#comment-8 Wed, 21 Dec 2005 16:48:00 +0000 http://viosym.blogsome.com/2005/12/19/who-moved-my-rss-feed/#comment-8 Thanks for the thoughtful post. You can learn more about how to survive a rss-feed hijacking at this article written by my client at Vegan.com: http://vegan.com/issues/2005/podjacking.pdf. Thanks for the thoughtful post. You can learn more about how to survive a rss-feed hijacking at this article written by my client at Vegan.com: http://vegan.com/issues/2005/podjacking.pdf.

]]> http://viosym.blogsome.com/2005/12/19/who-moved-my-rss-feed/#comment-7 Wed, 21 Dec 2005 16:45:16 +0000 http://viosym.blogsome.com/2005/12/19/who-moved-my-rss-feed/#comment-7 Thanks for helping to make the community aware of one of the pitfalls of rss. My client at Vegan.com has also published an article (http://vegan.com/issues/2005/podjacking.pdf) that gives some very practical strategies to dealing with the hijacker. One good tip he offers is to not contact the hijacker until you've announced on your own podcast that some listeners may be listening through an unauthorized feed, and announced the correct feed. Tell listeners that the unauthorized feed(s) may be discontinued any day. Also, it's a good idea to include your copyright notice verbally in the podcast, along with any sort of licensing of your podcast -- like licenses under Creative Commons (www.creativecommons.org). Doing these things will protect you because if the hijacker doesn't agree to work with you to minimize the disruption for the listeners on the authorized feed, you've at least given the listeners some notice that they need to check their feed and subscribe to the official feed. Thanks for helping to make the community aware of one of the pitfalls of rss. My client at Vegan.com has also published an article (http://vegan.com/issues/2005/podjacking.pdf) that gives some very practical strategies to dealing with the hijacker. One good tip he offers is to not contact the hijacker until you’ve announced on your own podcast that some listeners may be listening through an unauthorized feed, and announced the correct feed. Tell listeners that the unauthorized feed(s) may be discontinued any day. Also, it’s a good idea to include your copyright notice verbally in the podcast, along with any sort of licensing of your podcast — like licenses under Creative Commons (www.creativecommons.org). Doing these things will protect you because if the hijacker doesn’t agree to work with you to minimize the disruption for the listeners on the authorized feed, you’ve at least given the listeners some notice that they need to check their feed and subscribe to the official feed.

]]>