-
Website
http://www.scobleizer.com/ -
Original page
http://scobleizer.com/2005/10/31/wordpress-rss-feeds-suck/ -
Subscribe
All Comments -
Community
-
Top Commenters
-
danja
44 comments · 4 points
-
polizeros
52 comments · 1 points
-
AndyBeard
69 comments · 4 points
-
Zachary Adam Cohen
35 comments · 8 points
-
dbarefoot
40 comments · 3 points
-
-
Popular Threads
-
The best and worst thing Twitter did in 2009: RT
10 hours ago · 19 comments
-
World-brand-building mistakes France’s entrepreneurs make
1 week ago · 181 comments
-
A 2010 real-time app development platform from Kynetx
8 hours ago · 2 comments
-
2010: the year SEO isn’t important anymore
6 days ago · 66 comments
-
iPhone developers abandoning app model for HTML5?
6 days ago · 51 comments
-
The best and worst thing Twitter did in 2009: RT
I'm cool with doing a super-dooper Atom feed too, but don't mess up my RSS feed. That MUST work like my old feed.
http://feedvalidator.org/check?url=http://scobl...
And I get the full articles in NetNewsWire as well...
I got that feed from the big blue RSS button that pops up in the URL bar in safari.
I haven't had any trouble at all with Feedburner, and as far as I can tell, the feeds aren't 'funky' either. You might want to give it a whirl.
Drumsnwhistles: you are giving up a LOT by going with Feedburner: control of your destiny. Here's something to think about: what if Feedburner goes out of business? You're screwed cause all your readers are on Feedburner.
Or, what if they decide to start putting ads in your feeds? You're screwed. I'm not ready to do that yet.
IMHO, you're making a mountain out of a molehill with this. Seems you like you have two very easy and effective solutions here:
1) Ditch RSS and go with Atom. Seriously. I can't think of a single major newsreader that can't handle Atom without blinking.
AND/OR
2) Go with Feedburner. I LOVE this service. Great tracking, easy to set up, and shows human readable xml feeds.
Frankly, I'd avoid going with a Wordpress.com blog for the same reason I think a zillion others have noted in the past: why tie you blog's stability, brand, and hamper your movability to a third party? Heck, even Feedburner lets you use your own domain URL (albeit for a small extra fee).
Seriously, why would anyone with technical prowess want to go with somename.3rdpartysite.com when they can have somename.com or .net? It just doesn't make any sense to me. What possible value could you be deriving from a hosted Wordpress solution?
And no, I'm not trying to pick on Matt here. I've not used WordPress, but I respect the tool and the people behind it... and I know it's a really fine blogging app. I just don't get the hosted thing in your context.
There are TONS of people who don't want to do any work when starting up their blogs. I want to be more like the 98% than the 2%. By using the same services that other people will be using I will have something to say. And, I'll learn about those services in an intimate way.
This new feed is getting complaints.
So, yeah, I suppose that I was a bit too brusque to simply suggest that this wasn't a problem at all... but I stand by my assertion that it's likely to be easily solvable.
(and for the record... I use NewzCrawler, and I never noticed any problems at all with your WordPress feed)
http://scobleizer.wordpress.com/feed/
I don't know that to be the case. I don't use Atom feeds. I use RSS. I still don't understand what the Atom feed buys me that my old feed didn't. And, are you saying there is no aggregator out there that doesn't work with Atom? I think that's a pretty bold statement since there are hundreds of aggregators.
Your feed has been working fine in my GreatNews reader (which you pointed out a few months ago - thanks btw :) ) and has been working fine since you moved to wordpress.
The problem is not you using a hosted solution, it's the .wordpress.com part. Why can't you use scobleizer.com, and have it powered by wordpress.com? I just don't see why anyone who's serious about keeping your readers, which you seem to be, would tie yourself to a service.
Better point: what the hell is your problem with atom? You seem really anti it here. End users shouldn't care about which format it is. End users don't look at the source.
Those things? It's all about keeping your text safe in the XML pipeline from your keyboard to the end users viewer. Think of it like a tag that says "inside me you'll find no XML, so don't try parsing it as that".
Even if you don't like feedburner itself, have a think about how they handle this: they put some javascript and an xslt stylesheet into the (atom or rss) feed, and magically the feed looks pretty in browses when clicked on. But really, if Internet Explorer just downloads the file, then that is Internet Explorers problem.
"you are giving up a LOT by going with Feedburner: control of your destiny. Here’s something to think about: what if Feedburner goes out of business? "
Wait a minute, so why aren't you hosting you blog on your own server at your house or at least at a professional hoster? Before you had a "weblogs.com" url. good thing you were friends with Dave when he shut off that server. (not that he didn't have good reasons, but if you weren' Doc or Scoble you were pretty bad off and had to move quick). Now you have a Wordpress.com url. You can't even follow your own bad advice Robert. :)
With WordPress, you just gotta dig around for the RSS 2.0 feed
Regarding Atom it is a far more versatile and regulated standard than RSS has ever been and is supported by all major feedreaders out there - can you perhaps show one that doesn't support it? Atom is always my choice when choosing between it and RSS.
Why should you be able to read the contents of a feed in a web browser? How's that helping the technically illiterate out there?
WordPress corrected the problem and now produces valid RSS 2.0 feeds. Perhaps this has nothing to do with Atom vs. RSS, and is simply a matter of something invalid that needed to be corrected.
Before you had a “weblogs.com” url. good thing you were friends with Dave when he shut off that server. (not that he didn’t have good reasons, but if you weren’ Doc or Scoble you were pretty bad off and had to move quick).
No one was bad off. Weblogs.Com sites moved to Buzzword.Com after a couple of days. Sheesh.
Patrick: cause I’m a user and it’d make it more consistent. The Web got popular because of “view source.” RSS got popular because normal people who aren’t rocket scientists can look at it and figure out what it’s doing (and how to do it on their own sites).
Uh. No. The web got popular because... well... it was pretty easy for anybody and everybody to setup a site. I dispute view source as being the main thing behind it. And for crying out loud, the source back then was not exactly what you'd call great, or consistent. Personally, if the [CDATA[] helps a newbie to put properly formed XML up, and have it work rather than randomly error, then that's all good.
RSS got popular because normal people who aren't rocket scientists have software that reads the feed and shows it to them all pretty like (be it netnewswire, yahoo's rss reader, or even my.netscape, back in the day), and they have software (like wordpress, or movabletype, or livejournal, etc.) that makes those RSS/Atom feeds for them.
Patrick: I love how geeks argue with users when they point out inconsistencies in user experiences. How is that focusing on making it easier?
What does the way the source code of an rss/atom/etc. feed look have anything to do with the user experience?
The http://scobleizer.wordpress.com/feed/ stopped working on October 29 and began working again today. I always got full text before the 29th and again today.
RSSwowl does give the error as to why a feed isn't validating. Though, I'm afraid that I didn't note the error message at the time.
It does sometimes happen. I would guess that very few users or sites hand generate the RSS, RDF or Atom XML for their feeds. The author publishes the post, and some script generates the feed automagically for them. Even SF Gate wasn't validating for a few hours this morning. BBC screws up about once a week. No doubt better script debugging is the answer.
Robert, glad to have you back in my RSSowl.
For the technically inclined it's easy to see that I serve all the feeds as Atom 1.0. I believe it's important to have that transparency - we don't go around and call web pages html-pages or even php-pages or asp.net-pages, do we?
We use so little of the resources of the server, that we're running a hosting service: open source software for small businesses, including b2evolution. ;-) Hey, it's cheaper than what XO's additional "resource units" were costing us, but it's still a lot of money per month for the machine.
At any rate, my point is that unless you're willing to dedicate a lot of your time to maintaining the underlying software, a service, be it Typepad, LiveJournal, WordPress.com, ours, or any other can be fine. Though, I do have to admit that I shudder whenever I want to pick up someone's feed, and my only option is feedburner. Something just doesn't feel right there. Also, a service should allow a user to have their own domain [or subdomain like blog(s).domainName.TLD], as well as an exit path that preserves their look and all archived posts if they should wish to move to another service or self-hoting.
Oh, and on the other point in these comments, I haven't seen a feed reader yet that doesn't support RSSv0.92, RSSv1 (a.k.a RDF), RSSv2 and Atom 0.3. Few support Atom 1.x yet.
I do agree with Marc Canter: the user is best served when the services support as many standards as possible.
Availability of full-feeds is one of the most important issue to be addressed. After reading the comments I see there is a solution but I think it should be the default view in RSS readers if that's what the author intended.
> domain [or subdomain like blog(s).domainName.TLD], as
> well as an exit path that preserves their look and
> all archived posts if they should wish to move to
> another service or self-hoting.
1) Feedburner lets you (for a small fee) use yourdomain.com/feed or whatever (while still taking advantage of their cool services).
2) Even on free Feedburner accounts, if you decide to ditch FB, they'll kindly redirect accesses to your FB URL to whatever URL on your own server you'd like for 30 days (likely enough time for feedreaders to note the 301 redirect and react accordingly).
Note that I am not affiliated with FB in any way except as a happy user.
Oh, and Robert... it's certainly possible that there's SOME feed reader out there that can't handle Atom 0.3, just like there are still some browsers out there that can't handle proper CSS (and lots of other stuff), e.g., Netscape 4. I don't know about you, but I gave up on those folks ages ago.
A few other thoughts:-
- We should be way past people handcoding RSS. It should be transparent and just work. If you need to read the XML to work out what's going on, then you can also read specs and do research.
- There's nothing funky about CDATA. It's a part of the XML spec and has been for years. It's one solution to the double encoded & and it does just work.
- Your RSS feed doesn't have full text in the item.description and some html tags have been removed. Putting the full text into a content:encoded RSS2 extension tag is ok, but it assumes (wrongly) that most aggregators will be able to read it.
- Inventing new MIME types is a pain in the neck. (people who serve OPML and RDF-XML like this, please note). My browser has a perfectly good XML reader and it can handle stylesheets in XML. If I click on a link to an XML file I want to be able to read it. Not get some dialog forcing me to make a choice I may not understand.
- I'm not sure if you've started in MS word or used an MS system to cut and paste or what but you've got high order versions of ', "" and a few other characters in there. Character sets are a PITA, and while UTF-8 handles it, the feed may not end up in something that does. I do wish that when the content is basically aasci-7, all the systems involved would use aasci-7 for characters that exist in it. Microsoft please note, your smart quotes hurt developers because we frequently have to write code to convert them.
And finally, does anyone know who is reponsible for making & a reserved character in XML? Because shooting is too kind. I want to poke them with pointy sticks for eternity! And the same goes for the person who chose \ instead of / in Microsoft systems for folder path delimiters.
BTW I've had the same problem with RSS2 on my standard Wordpress blog (via Fantastico). I set it to full text, but nothing happened for a few days, then a partial feed arrived in tha aggregators. So it's a generic problem, not just Wordpress.com.
I seem to remmeber I had to do some hacking to get full posts in RSS2 - initially I kept getting the summaries, NOT the post. There are two different WP functions, one for summaries and the other for posts, never the twain shall meet.
It's annoying, and a shame because WP is a great blogging platform...but for podcasting and for out-the-box it's got a long way to go...atm I can't really tell non-techy types to go WP when I know techy people have issues - WP's loss is Blogger's gain, sadly.
Actually just checked my feed and I have the same issue - truncated post...I remember now I tried the full post WP function and got nada...it's very odd. Let us know if you find a solution...
It's odd because aggregated sites from my feed, such as Podcastalley et al show the full post? Curiouser and curiouser...
You know this, of course. So I'm left wondering why you'd waste time with virtiol instead of simply asking how to tweak the default.
"I just tried my Atom feed and I couldn’t even get it to load up in the browser. That certainly is not good usability..."
Agreed. That means your aggregator is broken.
When you request a properly-served Atom or RSS file, your desktop aggregator should launch and help you subscribe to it. Unless you use a web-based aggregator, in which case you should be clicking your autodiscovery bookmark instead of playing "hunt the feed".
Way to miss the point RC.
is this true?
It's an open option in the Wordpress Admin Panel.
No hacking involved besides clicking a radio button, and clicking submit.
"Error reading URL: The underlying connection was closed: The server committed an HTTP protocol violation."
I also run a WordPress-powered site but I have never seen this error on my own feed (mind you, I'm running WordPress on my own server, not as a hosted solution).
Scoble Sucks (and WordPress RSS)
(We don't think he sucks of course, just continuing the hyperbole.)
Here is what the post is supposed to have said:
Why does WordPress insist on putting the full text in content:encoded tags? Dave Winer’s site has full text in description tags; so isn’t that the right way to do it? I mean, come on, it’s self-evident. Drupal does not see the full text because it is looking at the description tags. Unless you go back to full text the way it use to be Robert, I will be pulling you out of my news feeds. Keep pushing WordPress
My feed is at http://www.door2doortechsolutions.com/blog/wp-r...
On mine it kuts off the description after a certian number of charters, it is somewere around 300 charters with spaces. I want ot use it so i can jsut update my blog, so i can grab that feed for my web page on my business.
Please email me back at salesdoor2doortechsolutions.com
Greg Caulder
Please email me back at salesdoor2doortechsolutions.com
http://wordpress.org/support/topic/113579
There's a fix there that helped me - maybe it will work for you too.