The RSS hijacking is worse than I thought or had been made aware of. It seems the folks over at Splashcast have added a bunch of shows in a new section of their website called channels. Turning their site into essentially another podcast directory. While I have no issue with a service aggregating “aka” listing my content as any exposure is good. All was well untill I look at the RSS button on my splashcast profile and see that they have hijacked my feed.
My first reaction was you have got to be kidding me, with all the negative press around this issue my thoughts where how in the world could they have blown this, but it is much much worse. They have set up links, to eight different services for people to subscribe to my show on their site via this hijacked feed.
At the time of this posting If you looked at my splashcast aggregated show profile here then look at the RSS button on the profiles you will see that it links to http://media.splashcast.net/xml/feeds/SOFC7247UN.xml this this is where they totally lost their way and they need to fix this immediately, so that it links to https://www.geeknewscentral.com/podcast.xml. All of the buttons on that page have the hijacked feed linked to all of those external subscription services.
Sorry but I am not going to stand for that crap. This needs to be switched like yesterday, and if they are going to offer up my feed they need to use my “original” RSS feed and not one that they can use to drive traffic away from my site and skew my stats.
I like both Marshall, and Alex but hey guys this is not good in a big way. When I click on the channel feed you have created it says “Geek News Central Podcast by SplashCast Feed Agent — SplashCast Channel” this is a cheap way of trying to defer the issue you have here. NOT ACCEPTABLE
Every subscriber they get to their new re-purposed feeds is a subscriber taken away from my original feed. SplashCast will use those subscriber numbers to value their business. Its one thing if I had “opted in” but they have created a directory of content producers all with hijacked feeds.
This is the same mistake that Podshow made early on with their site, that I and others gave them so much grief on. It just surprises me that this was missed, their team is experienced enough to know better.
While I expect that they will get this fixed, once again we need to make people understand that this type of activity will get them significant negative reaction in the space.
Update: My response to Marshall’s reply below: Mashall you have not addressed the feed hijacking to my satisfaction. I want to know if your going to fix this today or are you going to ignore what we are saying in the community
Response from Marshall Kirkpatrick
Hi Todd, happy to respond here. We’ve been doing our best to engage with the podcasting community all day about the new feature we released – lots of positive feedback as well as concerns like you’ve raised here. Readers should check out our podcasters FAQ at where the happy news is as well as other details.
The gist of the new feature is that it allows anyone to aggregate their favorite podcasts for their startpages or for sharing on blogs.
We really want to be a positive contributor in the podcasting community.
We’ll be posting in the morning about the lessons learned and future directions based on today’s feedback. We fully intend to respond promptly to all concerns, though, I assure you.
The main things we’ve heard from people who are concerned about what we’re doing are these:
* caching deprives podcasters of traffic reporting.
* do podcasters lose control over their feeds when they are added to the SplashCast directory?
* Attribution and native feed exposure
Some of these problems will be harder to fix than others, but for example, we’re not caching audio files – so hits are getting counted though subscribers aren’t yet. We’ve got attribution but will improve it, we’ll be talking to Feedburner to report subscribers just like every other aggregator does and (this is a big one) we’ll be rolling out the ability to claim your feed like Technorati lets bloggers claim
blogs. There will be more control enabled in this case.
And of course, opting out is easy to do. Just email me at firstname.lastname@example.org. If anyone wants to just discuss the issue, offer suggestions, etc. shoot me an email in those circomstances too.
Like I said, lots of work to do – but we’re doing our best to engage the community about how to offer the benefits of SplashCast’s media syndication tool while getting past the shortcomings at this service’s launch. We created a lot of documentation around this ( ), we’ve been commenting on other blogs and we had a live chat up on our site throughout the afternoon. We hope that this is just the begining of the conversation.
As I said, we’ll be posting about this in the morning – so stay tuned and feel free to drop a line any time.
Director of Content
Update 2: Marshall in the above comment you state
“We’ve got attribution but will improve it, we’ll be talking to Feedburner to report subscribers just like every other aggregator does and (this is a big one) we’ll be rolling out the ability to claim your feed like Technorati lets bloggers claim”
Personally I dont want anything reported to Feedburner I dont do business with them. I have my own stats engine that collects my RSS feed stats. You can simply eliminate the issue by simply replacing the RSS feeds on your channel listings with the RSS feeds links you are using to populate the channel with.