Comments on: Has Feedburner Snubbed Megite? http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/ Thoughts on Web 2.0, Social Media, Marketing. Thu, 26 Jan 2012 17:30:48 +0000 hourly 1 http://wordpress.org/?v=abc By: links for 2007-02-03 at Baron VC http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12903 links for 2007-02-03 at Baron VC Sat, 03 Feb 2007 00:37:38 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12903 [...] Has Feedburner Snubbed Megite? Feedburner blocking Megite raises interesting questions. Isn’t their business to provide feeds? I depend on them for mine and would rather they don’t make such calls on my behalf. Hope they work it out. (tags: megite feedburner) [...] [...] Has Feedburner Snubbed Megite? Feedburner blocking Megite raises interesting questions. Isn’t their business to provide feeds? I depend on them for mine and would rather they don’t make such calls on my behalf. Hope they work it out. (tags: megite feedburner) [...]

]]> By: Eric Olson http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12819 Eric Olson Fri, 02 Feb 2007 16:38:01 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12819 Hey all, Eric from FeedBurner here. Just wanted to explain why Megite was blocked. We always look for a handful of things in each request/useragent we receive to determine how to handle it and whether or not we need to block it. The Megite requests has the following characteristics 1) The reverse DNS looked like it was coming from a home DSL user (netblock-66-245-250-218.dslextreme.com) 2) Megite is not using If-Modified-Since requests or compression 3) The identifying User-Agent (from our sampling) was a generic 'libwww-perl/5.805' rather than something that identified itself as Megite Matt sent me a note this morning at 1am central time which I received when I got into the office this morning at 9am central. By 9:55am central time Joe Kottke, our Director of Network Operations, had unblocked Megite and sent an explanation to Matt including the info above. So that's the deal. No snubbing has taken place. :-) All is well in feed land now. If anyone has any questions about this (or anything that comes up in the future) please feel free to follow up with me any time (contact info below). Have a great superbowl weekend guys! Cheers, Eric ---- Eric Olson Publisher Services - FeedBurner E-mail: erico@feedburner.com Office: 312.756.0022 x2034 Mobile: 508.335.9221 Skype/AIM: EricJohnOlson Hey all,

Eric from FeedBurner here. Just wanted to explain why Megite was blocked. We always look for a handful of things in each request/useragent we receive to determine how to handle it and whether or not we need to block it. The Megite requests has the following characteristics

1) The reverse DNS looked like it was coming from a home DSL user (netblock-66-245-250-218.dslextreme.com)
2) Megite is not using If-Modified-Since requests or compression
3) The identifying User-Agent (from our sampling) was a generic ‘libwww-perl/5.805′ rather than something that identified itself as Megite

Matt sent me a note this morning at 1am central time which I received when I got into the office this morning at 9am central. By 9:55am central time Joe Kottke, our Director of Network Operations, had unblocked Megite and sent an explanation to Matt including the info above.

So that’s the deal. No snubbing has taken place. :-) All is well in feed land now. If anyone has any questions about this (or anything that comes up in the future) please feel free to follow up with me any time (contact info below). Have a great superbowl weekend guys!

Cheers,
Eric

—-
Eric Olson
Publisher Services – FeedBurner
E-mail: erico@feedburner.com
Office: 312.756.0022 x2034
Mobile: 508.335.9221
Skype/AIM: EricJohnOlson

]]> By: Matthew Chen http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12814 Matthew Chen Fri, 02 Feb 2007 16:26:37 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12814 Update: FB guys works really fast and they removed the blocking of Megite. We still need to work out some details on how to crawl. Thanks all. Update: FB guys works really fast and they removed the blocking of Megite. We still need to work out some details on how to crawl. Thanks all.

]]> By: Matthew Chen http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12806 Matthew Chen Fri, 02 Feb 2007 15:04:40 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12806 What is more, for some blogs's feeds, they also change the link for each post inside the feeds. That means, Megite crawler needs to check FB first to get the original url for a post. What is more, for some blogs’s feeds, they also change the link for each post inside the feeds. That means, Megite crawler needs to check FB first to get the original url for a post.

]]> By: Matthew Chen http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12805 Matthew Chen Fri, 02 Feb 2007 14:44:10 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12805 Marshall, we don't say FB is not good, maybe it is their software that makes the decision. But since FB hosts other bloggers' RSS feeds, "Currently feeding 328,504 publishers who've burned 554,266 feeds", and most of famous bloggers, such as this blog, techcrunch, are using their service, FB should give a clear and reasonable guidelines on crawlers that are different from a normal site's crawling policy because they host many different blogs' feeds. Otherwise Megite like service sites can not get up to date or real time feeds if they say that they can only be crawled every 10 seconds. But anyhow, it would be nice that they can notify us and give us guidelines before blocking, Megite is willing to following their reasonable guidelines. Marshall, we don’t say FB is not good, maybe it is their software that makes the decision. But since FB hosts other bloggers’ RSS feeds, “Currently feeding 328,504 publishers who’ve burned 554,266 feeds”, and most of famous bloggers, such as this blog, techcrunch, are using their service, FB should give a clear and reasonable guidelines on crawlers that are different from a normal site’s crawling policy because they host many different blogs’ feeds. Otherwise Megite like service sites can not get up to date or real time feeds if they say that they can only be crawled every 10 seconds. But anyhow, it would be nice that they can notify us and give us guidelines before blocking, Megite is willing to following their reasonable guidelines.

]]> By: Marshall Kirkpatrick http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12766 Marshall Kirkpatrick Fri, 02 Feb 2007 09:06:39 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12766 This sounds awful. I like the FB folks a whole lot though and reserve judgement until hearing their side of the story. Seems to me that Matt Chen is a good guy too, but gotta hear both sides of this story. This sounds awful. I like the FB folks a whole lot though and reserve judgement until hearing their side of the story. Seems to me that Matt Chen is a good guy too, but gotta hear both sides of this story.

]]> By: Muhammad Saleem http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/comment-page-1/#comment-12753 Muhammad Saleem Fri, 02 Feb 2007 08:13:46 +0000 http://www.deepjiveinterests.com/2007/02/02/has-feedburner-snubbed-megite/#comment-12753 Talked to Matt Chen a few hours back, this really is shitty of FB. Talked to Matt Chen a few hours back, this really is shitty of FB.

]]>