-
Website
http://howto.opml.org/ -
Original page
http://rsscloud.org/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
daniel
4 comments · 1 points
-
Rosenberg
6 comments · 1 points
-
Mason Lee
7 comments · 3 points
-
playerx
5 comments · 8 points
-
Jesse Stay
3 comments · 71 points
-
-
Popular Threads
-
HowTo: Notes on using EC2/Windows
2 weeks ago · 3 comments
-
HowTo: Notes on using EC2/Windows
http://rpc.rsscloud.org:5337/rsscloud/viewLog
One thing's for sure -- we'll need implementations in every language and runtime. I'm doing mine in the OPML Editor, of course. But just think of that as a reference implementation. I think the really scalable versions will be in Python or C.
Also thinking about using Amazon's SimpleDB to store the graph. We'll see...
Are you able to think of a good way to syntactically distinguish 140-char RSS feeds from the more popular "news article" style feeds? This would help for getting the LifeLiner feed into the right style reader client (provided you agree that there's no good one-size fits all reader, and sorting feed "styles" manually into different readers is a problem).
I would suggest having LifeLiner put the 140 chars in the RSS "title" element rather than description, only because an Atom version is going to require "title".
Looking forward to this.
process. Dave
Of course you could put the 140 chars into both the title and the body (which is, I think, what Twitter is doing now, finally). While that works, it seems somewhat inelegant.
Maybe some kind of smart filter to strip things like RT@'s and URLs from the tweet, and use the result as the title, displaying the full content in the body?
And yes, I will be sharing the code.
And it would be great if others would implement the equivalent app in other
environments.
From the output side it will just be putting out RSS with a <cloud> element.
It's the equivalent of Tweetie or Tweetdeck or Seesmic.
Dave
matt.rsscloud.org?
One thing I wonder about in the spec. If a Cloud changes it's IP address. . .well, can it? Oh wait, the cloud is identified by it's domain. The subscriber, though, can't change because it's identity IS it's IP address, right?
That's important to know. So a subscriber that had to change IP addresses would have to resubscribe to all it's subscriptions. Right?
lapse after 25 hours.
http://www.thetwowayweb.com/soapmeetsrss#rssclo...
So the longest you'll have a bad IP address around is 24 hours, 59 minutes
and 59 seconds.
Okay, so that's better. No unsubscribe method or anything, just store and update the time of subscription. Got it.
protocol.
http://cyber.law.harvard.edu/rss/soapMeetsRss.h...
"A has five required attributes: domain is the domain name or IP address of
the cloud, port is the TCP port that the cloud is running on, path is the
location of its responder, registerProcedure is the name of the procedure to
call to request notification, and protocol is xml-rpc, soap or http-post
(case-sensitive), indicating which protocol is to be used."
As does the RSS 2.0 spec.
http://cyber.law.harvard.edu/rss/rss.html#ltclo...
"It specifies a web service that supports the rssCloud interface which can
be implemented in HTTP-POST, XML-RPC or SOAP 1.1. "
I hope we can work together again...
I'm working on an internal project, but there's no reason to think that bits couldn't be released or talked about. I need to relearn how all this was implemented in Manila and Radio Userland. My memory is *not* that good ;)
next guys because you'll have pieces to test with that are already up and
running.
http://rsscloud.org/#httppostProtocol
Dave
But considering a cloud element that is accepting subscription requests via "http-post" is there a standard for naming the required parameters? My guess:
registerProcedure
port
path
protocol
url
writing today.
http://rsscloud.org/walkthrough.html
Dave
Cheers to Matthew Terenzio for securing the @RSScloud on Twitter.
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/><cloud domain='things.thingelstad.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />Now, I'm thinking that cloud servers will see their part and ignore the PubSubHubbub stuff and vice versa. Make sense?
Or, does this thematically just not make sense? Is it one or the other? I see no reason why that would be the case. Comments?
OK, I've read all your documentation and I'm trying to wrap my head around this. So is one of the major goals to be able to build aggregators that can consume "push" messages from rssCloud producers such that microblogging services like Twitter just become another producer? And "following" someone on Twitter would become subscribing to the "push" service pointed to by the <cloud> tag? If so, it seems that one of the value-adds that Twitter provides is the knowledge of who is following you. Have I missed how this information can be transmitted back to Twitter through rssCloud? And what about other features like blocking someone?
Ping me when you have a free moment sometime, I'd love to discuss it with you.
It would be nice to be able to provide a domain to pleaseNotify so that I could fully control the notification. I understand the verification issues. Could a secret also be supplied to pleaseNotify? rssCloud could perform at GET against my web server using the secret. I'd create a file with the same name as the secret on my server. Just a thought.
Here's my experience with rssCloud: http://www.voiceoftech.com/swhitley/?p=773
I was also reading some of the critiques of rssCloud, one of them being that the entire feed will need to be read by the aggregator. Couldn't this be solved by making our feeds smarter? If we provide a guid or pubDate to the feed, the feed could return the latest items instead of the full feed.
http://howto.disqus.com/howto_rebooting_the_rss... (this page Subscribe by RSS link)
through River2: Subscriptions feed to subscribe.
Comes back with the following error:
"Can't get the address of "guid" because the table doesn't have an object with that name."
http://www.ShawnDrewry.com
How does it work with Yahoo! Pipes?
trust me, new bloggers would like this way and understand your explanation.
The problem arises during the periodic resubscription requests. It appears that the "clouds" send an update when attempting to resubscribe. Aggregators could ignore all updates during a resubscription, but this could cause some valid updates to be ignored.
It would be great to have an additional parameter that would indicate that the "update" is just validation of a subscription request.