Skip to content

Instantly share code, notes, and snippets.

@superfeedr
Created March 2, 2010 06:12
Show Gist options
  • Save superfeedr/319193 to your computer and use it in GitHub Desktop.
Save superfeedr/319193 to your computer and use it in GitHub Desktop.
<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
<channel>
<title>Disqus - Latest Comments for julien51</title>
<link xmlns="http://www.w3.org/2005/Atom" rel="http://api.friendfeed.com/2008/03#sup" href="http://disqus.com/sup/all.sup#usercomments-71cbfce4" type="application/json"/>
<!-- Discovery for the hub -->
<link xmlns="http://www.w3.org/2005/Atom" rel="hub" href="http://disqus.superfeedr.com/" />
<!-- End Discovery for the hub -->
<link>http://disqus.com/people/julien51/</link>
<description>
</description>
<language>en</language>
<lastBuildDate>Mon, 01 Mar 2010 17:30:53 -0000</lastBuildDate>
<item>
<title>Re: Implementing PubSubHubbub subscriber support: A step-by-step guide</title>
<link>http://josephsmarr.com/2010/03/01/implementing-pubsubhubbub-subscriber-support-a-step-by-step-guide/#comment-37515642</link>
<description>Also, I'd insist on the fact that subscribers should use unique callback urls for each feed (with the inclusion of query params for example). It makes it incredibly easier to debug subscriptions. Also, I wrote a blog post about getting started with PubSubHubbub a few weeks back : &lt;a href="http://blog.superfeedr.com/API/pubsubhubbub/getting-started-with-pubsubhubbub/" rel="nofollow"&gt;http://blog.superfeedr.com/API/pubsubhubbub/get...&lt;/a&gt;&lt;br&gt;&lt;br&gt;It's not as detailed as yours though!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Mon, 01 Mar 2010 17:30:53 -0000</pubDate>
</item>
<item>
<title>Re: Implementing PubSubHubbub subscriber support: A step-by-step guide</title>
<link>http://josephsmarr.com/2010/03/01/implementing-pubsubhubbub-subscriber-support-a-step-by-step-guide/#comment-37509427</link>
<description>Joseph, we (superfeedr!) can probably help #Plaxo get any feed in realtime, (PubSubHubbub or not!)... Who should I get in touch with @ Plaxo?</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Mon, 01 Mar 2010 16:39:56 -0000</pubDate>
</item>
<item>
<title>Re: Fast Just Got Faster</title>
<link>http://blog.dlvr.it/2010/02/fast-just-got-faster/#comment-36889705</link>
<description>I hope you guys use &lt;a href="http://superfeedr.com" rel="nofollow"&gt;http://superfeedr.com&lt;/a&gt; for this feed polling :D</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 25 Feb 2010 21:41:12 -0000</pubDate>
</item>
<item>
<title>Re: Consuming RSS feeds with PubSubHubbub - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Consuming-RSS-feeds-with-PubSubHubbub#comment-36510877</link>
<description>Yeah, authenticated content distribution has been live for a little over a month, but the docs didn't mention it until earlier last week. Not a big deal :)</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 25 Feb 2010 17:01:19 -0000</pubDate>
</item>
<item>
<title>Re: Consuming RSS feeds with PubSubHubbub - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Consuming-RSS-feeds-with-PubSubHubbub#comment-36470145</link>
<description>Also, actually, we support "authenticated content distribution"! Please use https and hub.secret... Also, for the subscriptions renewal, we do not expire subscriptions, unless your callback consistently returns a 404 status for a long time.</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 25 Feb 2010 13:02:53 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : On Outsourcing</title>
<link>http://blog.superfeedr.com/outsourcing/startups/validation/on-outsourcing/#comment-36284681</link>
<description>Yes indeed! But even in that case (like Superfeedr!) you have to use smaller bricks to build the bigger bricks =D</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 24 Feb 2010 09:16:33 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : Redis at Superfeedr</title>
<link>http://blog.superfeedr.com/datastore/memcache/mysql/performance/redis/redis-at-superfeedr/#comment-35727538</link>
<description>So it's actually each of our redis servers running that... so you can multiply that :) Also, as @antirez said, we do not use simple key/value, but a more complex data type, where we indeed query with ranges.</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Sun, 21 Feb 2010 12:32:54 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : Redis at Superfeedr</title>
<link>http://blog.superfeedr.com/datastore/memcache/mysql/performance/redis/redis-at-superfeedr/#comment-35727451</link>
<description>So, we also use mongo for another part, our stats: &lt;a href="http://blog.superfeedr.com/analytics/mongodb/publisher/pubsubhubbub/tutorial/how-we-built-analytics/" rel="nofollow"&gt;http://blog.superfeedr.com/analytics/mongodb/pu...&lt;/a&gt; but we certainly don't push it as lmuch as redis (yet!).&lt;br&gt;&lt;br&gt;Yes, it's a 64-bit distro running 32-bits compiled redis. So far no issues.</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Sun, 21 Feb 2010 12:31:31 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : PubSubHubbub : security</title>
<link>http://blog.superfeedr.com/API/PubSubHubbub/secure/secure-pubsubhubbub/#comment-35624529</link>
<description>You're right... I'm currently revising the whole doc for all the hubs we host. Thx, I won't forget.</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Sat, 20 Feb 2010 08:57:26 -0000</pubDate>
</item>
<item>
<title>Re: Blogger and Google Reader Speed Up, Suggestions Improve</title>
<link>http://blog.louisgray.com/2010/02/blogger-and-google-reader-speed-up.html#comment-35471886</link>
<description>It's indeed an awesome piece of news!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Fri, 19 Feb 2010 08:29:20 -0000</pubDate>
</item>
<item>
<title>Re: Has Google Reader Just Gone Real Time?</title>
<link>http://thenextweb.com/apps/2010/02/19/google-reader-real-time/#comment-35471700</link>
<description>That's awesome! Indeed... Everyone should now have their very own hub :D Come to &lt;a href="http://superfeedr.com/publisher" rel="nofollow"&gt;http://superfeedr.com/publisher&lt;/a&gt; for this!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Fri, 19 Feb 2010 08:26:37 -0000</pubDate>
</item>
<item>
<title>Re: Bulk updates with cursors - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Bulk-updates-with-cursors#comment-34860318</link>
<description>Hum... maybe this is not the right place to help :) Try to the google group of superfeedr : &lt;a href="http://groups.google.com/group/superfeedr" rel="nofollow"&gt;http://groups.google.com/group/superfeedr&lt;/a&gt;&lt;br&gt;&lt;br&gt;I'm not sure I understand. You use the same feed (a buzz feed) and subscribe to it with 2 different callbacks on the same hub? &lt;br&gt;&lt;br&gt;If that's it it, then, it's really really weird, because, obviously we consider feeds (and not subscriptions)), so if we've been able to find an update for the feed we'll push it to _all_ the callbacks and then, when we fetch the feed again (a few minutes later), then, obviously we won't see anything new.</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 17 Feb 2010 11:09:47 -0000</pubDate>
</item>
<item>
<title>Re: Bulk updates with cursors - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Bulk-updates-with-cursors#comment-34847744</link>
<description>My pleasure :)&lt;br&gt;&lt;br&gt;So yeah, we're probably slightly slower to respond to pings (but that should stay below 30 seconds). It's due to various reasons, including the fact that we don't have Google's infrastructure just yet :D&lt;br&gt;The goog thing about our hub though, is that it works with _any_ feed :)&lt;br&gt;&lt;br&gt;As for the fact that you'll want a hub, well, if your app publishes any RSS feed, you'll want a hub, but you're right, in the case of Buzz2Twitter, that doesn't makes much sense!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 17 Feb 2010 09:05:47 -0000</pubDate>
</item>
<item>
<title>Re: Bulk updates with cursors - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Bulk-updates-with-cursors#comment-34843806</link>
<description>Nick is right :) We use PubSubHubbub as much as we can to avoid polling. Also, if you don't see instantaneous updates, then, yes, please let us know too... We're committed to improve things!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 17 Feb 2010 08:18:23 -0000</pubDate>
</item>
<item>
<title>Re: Bulk updates with cursors - Nick's Blog</title>
<link>http://blog.notdot.net/2010/02/Bulk-updates-with-cursors#comment-34841019</link>
<description>Hey,&lt;br&gt;&lt;br&gt;Well, we (superfeedr) are a real hub! The fetching will happen _only_ if the feed isn't pushed to us, so in fact we a real hub + a hub that works with any feed, pushed or not.&lt;br&gt;&lt;br&gt;So, for any feed that support PubSubHubbub, RSSCloud, XML-RPC ping (to us or pingomatic), SUP, it will be realtime! For the others, you may have a dealy of up to 15 minutes. (we also use a lot of APIs and different techniques to make sure we fetch in less than 15 minutes.&lt;br&gt;&lt;br&gt;Also we host a lot of hubs, including Tumblr, Postrous, ReadWriteWeb, Gawker and a lot more to come. I'd be glad to host one for your app too if you want.&lt;br&gt;&lt;br&gt;And yes, if you eventually use a hub (self made, or hosted) and link it from your feeds, Reader and Buzz will susbcribe to it. &lt;br&gt;&lt;br&gt;I hope this helps :)&lt;br&gt;&lt;br&gt;Cheers</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 17 Feb 2010 07:19:49 -0000</pubDate>
</item>
<item>
<title>Re: Staying Young (Turning 43)</title>
<link>http://continuations.com/post/383782835#comment-33843564</link>
<description>Herzlichen Glückwunsch zum Geburtstag :p</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 11 Feb 2010 09:36:21 -0000</pubDate>
</item>
<item>
<title>Re: FriendFeed Sale Influenced by Google Buzz?</title>
<link>http://thegongshow.tumblr.com/post/383715861#comment-33841837</link>
<description>More than that (it seems clear that he knew!), I'd love to know if Facebook knew about Buzz too?</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 11 Feb 2010 09:19:30 -0000</pubDate>
</item>
<item>
<title>Re: Every time an engineer joins Google, a startup dies</title>
<link>http://cdixon.org/2010/02/11/every-time-an-engineer-joins-google-a-startup-dies/#comment-33841695</link>
<description>Well, the startups need Google to buy them! And Google need the engineers to continue innovating (even if it's not the same rate!). When Google says "we're going to bring fiber to your home", they're also fostering innovation on the tens of thousands of homes where the kids will be able to access invaluable information or "invent" new uses with a faster internet.&lt;br&gt;&lt;br&gt;Most startups don't have the "power" that Google or other big cos have when lobbying or financing open-source projetcts, research projects in universities... etc&lt;br&gt;&lt;br&gt;This is a whole eco-system. What's usually lost somewhere is gained somewhere else!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Thu, 11 Feb 2010 09:17:55 -0000</pubDate>
</item>
<item>
<title>Re: Some Thoughts on Google Buzz</title>
<link>http://continuations.com/post/381846212#comment-33406783</link>
<description>That would be very interesting (specially since you use a specific domain, it's kind of an edge case, but that should work no matter what)! And if you ever expose RSS feeds for DailyLit, please let me know so I can prepare a hub for you guys :)</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 10:15:21 -0000</pubDate>
</item>
<item>
<title>Re: Some Thoughts on Google Buzz</title>
<link>http://continuations.com/post/381846212#comment-33405455</link>
<description>Yes, that's how you describe it. Generally, if your DailyLit allows users to add a "site url" (like twitter or else does), you want to add the rel="me" property to these links, it tells anybody (including robots) : "hey, if this page your currently browsing is mine, then, this other page is mine to". Then on the google profile : &lt;a href="http://www.google.com/profiles" rel="nofollow"&gt;http://www.google.com/profiles&lt;/a&gt; you can add any link to any site. If you link to your dailyLit page, then, Google will see the reprocity and will conclude that you're indeed the owner of the dailylit page... &lt;br&gt;&lt;br&gt;You're right, it _is_ complicated to describe, but if every service our there adds the rel="me" to the user links you provide, then, it all works perfectly, and very transparently :)</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 10:05:30 -0000</pubDate>
</item>
<item>
<title>Re: Some Thoughts on Google Buzz</title>
<link>http://continuations.com/post/381846212#comment-33403816</link>
<description>You need a Google profile... And yes, you can add any RSS feed. See Brad's instructions there : &lt;a href="http://www.google.com/buzz/bradfitz/PPjHXDhANAC/Want-to-connect-your-blog-or-some-other-feed-to" rel="nofollow"&gt;http://www.google.com/buzz/bradfitz/PPjHXDhANAC...&lt;/a&gt;</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 09:45:20 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : Google's Buzz is PubSubHubbub in, and out</title>
<link>http://blog.superfeedr.com/google/pubsubhubbub/use-case/google-buzz/#comment-33403559</link>
<description>A lot of people criticize the fact that this happens in Gmail. The fact that&lt;br&gt;it uses the same technologies for in and out content, is a proof that this&lt;br&gt;cna be consumed anywhere else.&lt;br&gt;We've seen in the past LinkedIn integrating the content of Twitter, Facebook&lt;br&gt;allowing me to import my other web activities... etc. I think eventually all&lt;br&gt;these network will endup just being the place where I consume my friend's&lt;br&gt;social activities, where-ever they happen. To that regard, I think apps like&lt;br&gt;Tweetdeck and Seesmic will have a great role to play...</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 09:42:05 -0000</pubDate>
</item>
<item>
<title>Re: Some Thoughts on Google Buzz</title>
<link>http://continuations.com/post/381846212#comment-33403148</link>
<description>The most interesting point for me is the fact that Buzz gets PubSubHubbub content in and pushes pubsubhubbub out... eventually Gmail is just the place where we can consume the data, but we can hope to consume it somewhere else soon as well :)&lt;br&gt;&lt;br&gt;And we (superfeedr)'re pretty excited to be providing hubs for a lot of sources : all tumblr blogs, for example :). If you add your blog into your profile, it will show up in realtime in your buzz and your "gmail followers" will get that too...</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 09:36:08 -0000</pubDate>
</item>
<item>
<title>Re: Superfeedr Blog : Google's Buzz is PubSubHubbub in, and out</title>
<link>http://blog.superfeedr.com/google/pubsubhubbub/use-case/google-buzz/#comment-33398526</link>
<description>Yes it is. Event hough, "invented" is probably not the good word here. These are just HTTP POST requests originating from a server rather than from a client. Paypal, for example, had that for a decade... But Jeff made them way more popular, for sure!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 08:36:02 -0000</pubDate>
</item>
<item>
<title>Re: Another day, another year</title>
<link>http://bijansabet.com/post/381704640#comment-33380845</link>
<description>Happy Birthday Bijan!</description>
<dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">julien51</dc:creator>
<pubDate>Wed, 10 Feb 2010 08:08:42 -0000</pubDate>
</item>
</channel>
</rss>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment