Loading Profile...
No support for content:encoded?
I'm trying to feed http://meyerweb.com/feeds/excuse/rss2... and it fails (see http://twitter.com/excuseoftheday/), apparently because I use 'content:encoded' and not 'description'. The feed validates is claimed to be successfully parsed by Twitterfeed, so I'm left wondering if there is an oversight or bug in the service, or a mistake on my part.
I’m nonplussed
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
-
Inappropriate?Okay, now the feed is valid (with a couple of recommendations) in addition to being successfully parsed by Twitterfeed. Still no updating with 'content:encoded', though. I'll add 'description' to the items but this still seems like a bug. Is it?
