Disqus - Latest Comments for jeremyfelt

Re: OPML for Twitter lists (Scripting News)

jeremyfelt — Tue, 03 Nov 2009 19:27:35 -0000

Nicely done! I can't wait to see how smoothly this ends up including other pieces of a distributed 140 character system... and more! Then the fun really happens. :)

Re: On pubsubhubbub (Part 2) – Get with it, PuSH, you’re supposed to be realtime.

jeremyfelt — Wed, 30 Sep 2009 20:02:25 -0000

Hi Brett, thanks for stopping by.

This comment stream aside, the original post was written more as my perception than science. Rereading, it's a pretty unorganized perception. Ahh, late nights. There's more too the rambling, but if you come away with one thing from the above, it's that I don't see the FeedBurner stuff being real time as I thought it would.

I'll be grinding through the data more closely as the week goes on. The initial conclusions are based on a snapshot look at the initial 24 hours or so of use.

I can't answer to the latency yet, but I also can't imagine it being too high. Not a perfect answer, I know, but the server is on Amazon's EC2 and overall latency (network and system) seems low. Almost the only traffic coming in is from rssCloud and PubSubHubBub notifications. From watching Dave's rssCloud log (light pings), the time posted is usually less than .300 seconds.

The feeds that I've noticed the most issues with are from FeedBurner. My guess is that the delay and re-pushes are due to the ping scheduling between publisher->FeedBurner->PuSH. Once publishers start pinging directly to the hub instead of relying on a middle man, I would think that these issues clear up. See previous post directed at publishers.

The feeds that I've noticed the best response with are from Google Reader shared items. Again, perception, but things seem to run pretty smoothly here.

My generated twitter-link feeds seem to be sporadic when done in quick succession. @mmastrac pointed out after I posted last night that this could be a "race" between the feed writing and the hub reading if things are happening quickly enough. I still need to explore that.

You've given me a bunch of stuff to look at. I'll do what I can to start logging and parsing all of it and then provide the results. Hopefully I find a few problems with my code to fix along the way. :)

Re: On pubsubhubbub (Part 2) – Get with it, PuSH, you’re supposed to be realtime.

jeremyfelt — Wed, 30 Sep 2009 18:02:33 -0000

Google did make announcements though.

http://adsenseforfeeds.blogspot.com/2009/07/wha... - Google announces PubSubHubBub support in FeedBurner feeds for AdSense, notifying a "Google-run Hub".

http://googlereader.blogspot.com/2009/08/pubsub... - Google announces PubSubHubBub support for shared items in Reader.

http://buzz.blogger.com/2009/08/blogger-joins-h... - "All blog post feeds now contain a "hub" element, and will ping Google's hub on every post update."

http://googlecode.blogspot.com/2009/08/towards-... - "we have gone a step further and added PubSubHubbub support to Google Alerts."

I'm not trying to push any blame on Brett. Google owns this now and should help any issues along. I've written about some of the issues I'm seeing with Google's PubSubHubBub Hub.

Constructive discussion about the issues I've been seeing is definitely welcome.

Re: On pubsubhubbub (Part 2) – Get with it, PuSH, you’re supposed to be realtime.

jeremyfelt — Wed, 30 Sep 2009 14:03:31 -0000

Cool, I'm not a big AppEngine guy. Not trying to argue the architecture. My perception is that it's stable and stays up.

Plugging the hub into many feeds is a great way to test. But, two things.

1) When you're big like Google and you announce the implementation, the perception given to me, the developer, is that you're ready.

2) When I, the developer, do start using it, I'll get a perception on how it's working and I'll share it.

If others have details on how it's working for them, I'd love to share examples. I'm having fun working with both rssCloud and PubSubHubBub and coding > arguing.

Re: On pubsubhubbub (Part 2) – Get with it, PuSH, you’re supposed to be realtime.

jeremyfelt — Wed, 30 Sep 2009 12:03:07 -0000

Yes, referring to the official PubSubHubBub server that Google employee Bret Slatkin wrote and deployed. The one that Google then Pushed to their Blogger feeds.

Got it, no multiple hubs. But by using multiple IPs from the AppEngine network, a distributed network and uptime is inferred.

My point is - if you're going to push yourself into millions of feeds as a solution, then you are ready to go.

BTW, I'm not arguing against PubSubHubbub here. I want it to work. That's all that I'm getting at.

Re: On pubsubhubbub (Part 2) – Get with it, PuSH, you’re supposed to be realtime.

jeremyfelt — Wed, 30 Sep 2009 11:02:13 -0000

The two circumstances are different. There are always rough edges, but....

The rpc.rsscloud.org server you are probably referring to is maintained by Dave with no promise of uptime (correct me if I'm wrong, obviously) as a place to test your implementation. It is possible that the server can be rebooted for changes at any time. No big company is providing a constant connection here.

The WP plugin for rssCloud creates a server on every blog that installs it. Problems have been few and far between with this.

The pubsubhubbub server hosted by Google has been pushed into every blogger feed and implemented heavily in FeedBurner feeds by Google. It pushes updates from multiple IPs, indicating a network of hubs that they are using to guarantee uptime. By doing this, they have told me that they are ready for real time.

Re: A question for DNS gurus out there in InternetLand (Scripting News)

jeremyfelt — Wed, 23 Sep 2009 22:13:03 -0000

Looks like it's still propagating. When I do a "nslookup r2.ly" from my Windows machine, I get my openDNS resolver, which returns 208.69.36.132 when I ping it.

But when I use this (http://network-tools.com/nslook/Default.asp) to do an nslookup, it sees that slicehost has it. Should probably fix itself soon. Assuming that you've gotten word within the last few hours, of course. If it's been a day, then I'd start to wonder.

Re: Hooking the lizard brain up to the cerebral cortex (Scripting News)

jeremyfelt — Mon, 21 Sep 2009 09:37:36 -0000

I'm probably confusing things by not being completely finished with it yet. :)

That subdomain didn't exist until last night. I added "rss" as a TXT record first, and then later as an A record.

I didn't get around to doing the redirect - was having too much fun with other things. Right now it goes to a "tesT" page on the server, but will redirect later to my feed.

Re: Hooking the lizard brain up to the cerebral cortex (Scripting News)

jeremyfelt — Mon, 21 Sep 2009 09:24:56 -0000

The main purpose is to eliminate confusion, which came up quickly in the previous DNS post. We all plug the address in our browsers to see what happens because seeing the TXT record isn't as easy.

Re: Hooking the lizard brain up to the cerebral cortex (Scripting News)

jeremyfelt — Sun, 20 Sep 2009 23:48:29 -0000

Awesome! Just tried it and it works on my previously registered supercloud already. Good, good stuff. I'm going to go add an A record for rss.jeremyfelt.com that I setup a TXT record for after your earlier post.

I probably overstate this, but I have so much fun with tech that slides together well.

Re: DNS for RSS feeds (Scripting News)

jeremyfelt — Sun, 20 Sep 2009 21:39:52 -0000

I like that idea, hadn't thought of a combo deal. :)

Anything where the user only needs to know one thing (their address) and the technology (browser/cloud app) figures the rest out seamless is a good way to start.

Re: DNS for RSS feeds (Scripting News)

jeremyfelt — Sun, 20 Sep 2009 14:14:58 -0000

It doesn't make a website or redirect to your feed, it only adds a DNS TXT record for the feed specified.

Once you have this, an application that is looking for TXT records will know how to translate connectme.supercloud.org to whatever feed is stored as TXT.

Re: DNS for RSS feeds (Scripting News)

jeremyfelt — Sun, 20 Sep 2009 14:03:49 -0000

The practical applications are pretty clear to me.

You can store your feed in a TXT record under a domain name. If you move from 140char Client1 to 140char Client2, you can change your TXT record from feed1 to feed2 and the aggregators that are paying attention won't be required to notice the change. They'll just deal with it. You can change services without your friends having to follow around manually.

As for handling situations where other TXT records exist under that domain... It's up to the aggregator to know what a feed is/isn't and if it is/isn't cloud enabled. We'll just grab them and check.

Re: Someone give Om an award (Scripting News)

jeremyfelt — Tue, 08 Sep 2009 18:20:56 -0000

Interesting, while the main Salon blogs don't seem to be supporting rssCloud yet, there are a few that appear to be running Radio UserLand still and they have it enabled (probably since they fired up).

Haven't tested to see if it works yet as I'm still working on my xml-rpc implementation. Going to try it soon though. :)

List here: http://blogs.salon.com/

Re: Someone give Om an award (Scripting News)

jeremyfelt — Tue, 08 Sep 2009 11:08:41 -0000

Looks like all/most of CNN blogs might be updated. 3/3 so far..... Anderson Cooper: http://rss.cnn.com/rss/cnn_ac360blog.rss :)

Re: Someone give Om an award (Scripting News)

jeremyfelt — Tue, 08 Sep 2009 10:26:31 -0000

Yeah, I loved it when I added them to my river last night.

I actually started randomly going through blogs I found here-- http://botd.wordpress.com/ -- and adding what I could find.

Was surprised by some of the bigger names.

Re: HowTo: Implementor's guide to rssCloud

jeremyfelt — Tue, 08 Sep 2009 10:20:20 -0000

No problem. I did the same thing for my first many attempts before I understood the message about not being behind a firewall. You're right, the log is very useful.

Re: Someone give Om an award (Scripting News)

jeremyfelt — Tue, 08 Sep 2009 10:09:17 -0000

CNN wire is here: http://rss.cnn.com/rss/cnn_wire?format=xml

I had to find the very small icon, then click on "View as XML" in FeedBurner. Not too friendly. :)

The political ticker was a bit easier, just a small icon: http://rss.cnn.com/rss/cnn_politicalticker.rss

Nudge harder. :) I half expected them to be flipped on already yesterday.

Re: HowTo: Implementor's guide to rssCloud

jeremyfelt — Tue, 08 Sep 2009 10:07:14 -0000

For REST, you make your request through the server specified in the cloud element of the feed you are subscribing to:

http://cloud.domain:cloudport/cloudpath

You pass parameters telling the server how to notify you:

notifyProcedure=na
port=yourport
path=yourpath
protocol=yourprotocol
url[n]=urltosubscribe

The server then notifies you on your public IP address at the port and path specified using the protocol specified.

Re: Someone give Om an award (Scripting News)

jeremyfelt — Tue, 08 Sep 2009 09:54:29 -0000

CNN (hosted on WP) was there right away:

http://politicalticker.blogs.cnn.com/
http://cnnwire.blogs.cnn.com/

From the WP site, NY Times uses WordPress, but I couldn't find any feeds last night.

Re: Tease! Tease! Tease! (Scripting News)

jeremyfelt — Mon, 07 Sep 2009 16:23:06 -0000

This is REALLY awesome. I'm stoked that WP is early adopting.

Re: Add RSS Cloud Element

jeremyfelt — Fri, 04 Sep 2009 13:46:01 -0000

Thanks guys! Should have the second version up this weekend with the most important part - notification.

Re: rssCloud meetup at UC Berkeley, Sept 9 (Scripting News)

jeremyfelt — Mon, 31 Aug 2009 22:07:13 -0000

I wish I could. Any chance of an audio/video stream being available during or after? I'd love to see what everyone else is thinking right now.

Re: 7 years plus 70 days (Scripting News)

jeremyfelt — Sat, 22 Aug 2009 12:28:20 -0000

4 months tomorrow for me! Being told I had pneumonia triggered a switch in my brain and I haven't gone back. Feel wonderful too. Congrats on 7 + 70. :)

Re: An rssCloud Progress Report – Week One

jeremyfelt — Sat, 15 Aug 2009 21:00:02 -0000

Thank you. I've had fun with the rssCloud stuff. So many reasons to keep building on this area, I can't wait for the next corner.