“They’re including a nice smallish RSS reader in their Mail app. I had seen it before, and it’s a River of News aggregator.”
Pointing us to TechCrunch:
“Yahoo has deeply integrated RSS into the Yahoo Mail beta experience. Directly below the email folders are â€śRSS foldersâ€?. Clicking on the top folder show all posts in a ‘river of news’ format, meaning all posts for all subscribed feeds are listed in the order they have appeared in feeds.”
This could act nicely as a backup to Rojo when I’m having problems over there, especially if they’re smart and at least account for OPML synchronization (and I mean synch, not import and export – now’s the time to build it in, fellows). Too bad it’s a closed beta…
I’m totally uninterested in Yahoo! mail – I don’t wnat or need another mail account or even another mail reader. But another good web-based RSS reader. That’d be cool. And if it could synch with an OPML that I maintained somewhere’s else, or allowed me to publish the OPML that I maintain there without jumpign through hoops, that’d be the Golden Fleece (or is that the Holy Grail?).
See elliptical for details. Please comment here or there with problems, concerns, or comments.
He‘s getting the same message that I am, but doesn’t have xmlrpc logging turned on, so we can’t verify that he’s having the same precise problem that I am, so I still don’t know for sure that the problem I think I see in my log is caused by the interaction between OPML Editor and WP or whether it’s something on my server. Anyone who’s got xmlrpc logging tuned on (or can turn it on) willing to give it a whirl?
Next step is for me to make OPML Editor skip over some of the whitespace handling that it does to see if something in there is causing the munging.
See my conversation with Dave starting here.
When I step through the code I get what appears to be a valid xmlrpc method call over http, but my xmlrpc log file looks munged.Â If there’s anyone around who uses a WordPress 1.5+ blog and the OPML Editor and woud be willing to try a post, I’m interested to see if you have the same problems or if the issue is on my server.
I tried Dave’s wordPress.root tool or the OPML Editor to create a new post at elliptical this evening, and it seems as though the inplementation of the MetaWeblog API in OPML Editor is different than that in Flock, because Flock’s blogging tool works just fine while the OPML Editor’s tool won’t authenticate me to xmlrpc.php.
Here’s what the log file records from Flock (actual post data removed for clarity):
2005-11-10 19:38:50 Input: <?xml version=”1.0″?>
and here’s what’s recorded from OPML Editor:
2005-11-24 00:28:55 Input: <?xml version=”1.0″?>^M
<value><struct>^M <member>^M <name>description</name>^M <value>^Mwhat’s the log say?</value>^M </member>^M <member>^M <name>title</name>^M <value>test for kinrowan.net</value>^M </member>^M </struct></value>^M
Among the oddities are the presence of the “^M” strings at the end of each line.
Also strange is that OPML Editor is able to communicate just fine with WordPress.com blogs, and so is Flock.
Here’s the error message I get:
Nevertheless the wordPress.root tool is really cool – being able to use the OPML Editor to post here is boon enough!
Dave, I have a question: The spec says nothing about OPML being case-unfriendly, and the OPML Editor doesn’t treat attributes as case-sensitive 1, but the validator fails a file when the attributes “xmlurl” and “htmlurl” are used, but not the same file when “xmlUrl” and “htmlUrl” are used. Is this an oversight?
1 I say this because I have a right-click menu item that looks like this:
if dialog.ask (“What attribute do you want to modify?”, @myatt)
op.attributes.getOne (myatt, @myval)
if dialog.ask (“Enter the ” + myatt + ” for this headline:”, @myval)
op.attributes.setOne (myatt, myval)
When I use it to check “xmlurl” and “xmlUrl” they both return the same value, which indicates to me that it’s treating both strings as equivalent.