It’s very annoying that while I can have my tumblelog pick up any rss feed I want, it doesn’t seem to like to pick up the embedded links or image tags within the posts in those feeds. For instance, everything I post here gets picked up, but there’s no way to really see what I’m talking about because the feed is munged. A reader has to click through the “via” link to get to this site, and read it here… Which completely defeats the purpose of an all-in-one “stream of concsiousness” type setup.
Emails to their staff get no response. I really like the concept, but don’t understand this unnecessary weakening of their product. Other feeds (Flickr, etc.,) seem to work… and attribution links can be automatically added to each incoming post… I just don’t understand the disconnect with reading a simple RSS feed.
/gripe.
Update from the fine folks over at Tumblr::
We apologize for the problem. The version of WordPress you’re using is sending two “description” fields in its RSS feed: a plaintext, summarized, tag-less standard version, and a full-HTML version in a custom <content:encoded> tag. Our RSS parser hadn’t yet implemented support for <content:encoded>.
I just added that support, and it will apply to all feed imports from now on.
Now that’s what I call service.
Sphere: Related Content
0 Responses to “Tumblr Gripe”