RSS summaries

Message Bookmarked
Bookmark Removed
Hey!
I'd love for the rss summaries to be the entire message. This would allow me to set my feedreader to summaries only, and i could see each message in the thread.

At the moment, i only get part of each message (the message "summary") so then i have to load the whole thread to be able to see it. Not only does this take ages for long threads over dialup, but it costs you guys a heap of bandwidth.

I'd even be happy if this were an option (GET param) in the threadrss script and i had to add it myself to the url if this is the behaviour i wanted.

Anko Painting (Anko2), Thursday, 27 October 2005 23:35 (twenty years ago)

the ilx rss feeds are very standard - there is a summary which is a truncated version of the content, but the content is also there in the right <content:encoded> node, so it could be that your RSS reader of choice is just being a bit rub at not letting you read the whole content.

(You can see this by clicking an RSS feed, like below, in a regular WWW browser and looking at the source)

quite ready to believe i've got this ass-backwards tho if others can help?

Britain's Obtusest Shepherd (Alan), Friday, 28 October 2005 12:16 (twenty years ago)

On my reader, it does indeed show the entire message. Although I do wish that, on the RSS feed for a board, clicking on the thread link would take you to either the #unread or the exact message in the RSS feed, rather than just to the thread. (I'd probably prefer the #unread, but either would make more sense than how it currently works.)

I hope that's clear.

Casuistry (Chris P), Tuesday, 1 November 2005 06:20 (twenty years ago)

But the RSS 2.0 spec does not support content:encoded.

http://blogs.law.harvard.edu/tech/rss

only description is standard.

Anko (again), Thursday, 3 November 2005 00:37 (twenty years ago)

I didn't think we were using 2.0.

Rufus 3000 (Mr Noodles), Thursday, 3 November 2005 03:00 (twenty years ago)

yeah you're right, the header is

but besides version 0.91 being depreciated, it does not have content:encoded as a valid section either!

http://my.netscape.com/publish/formats/rss-spec-0.91.html

I know some feed readers adopt content:encoded but we should be coding to standards, not browsers/readers to promote interoperability.

Anko (again), Thursday, 3 November 2005 05:21 (twenty years ago)

the code is probably not 100% conformant - when the code was written RSS was still quite fluidly defined. however WRT "content", the content module IS declared with xmlns:content="http://purl.org/rss/1.0/modules/content/", though i do think that these modules (and that is a common, even standard module to declare/include) are not strictly part of 9.1, and maybe are only to be checked at rss 2.0.

i will check to see if the current code can be declared to be 2.0 and then change it to do so if it doesn't take much coding up.

Britain's Obtusest Shepherd (Alan), Thursday, 3 November 2005 11:03 (twenty years ago)

http://feedvalidator.org/check.cgi?url=http%3A%2F%2Filx.wh3rd.net%2Fthreadrss.xml%3Fmsgid%3D6383037

Casuistry (Chris P), Thursday, 3 November 2005 15:29 (twenty years ago)

yeah, i already tried that, but thanks

Britain's Obtusest Shepherd (Alan), Thursday, 3 November 2005 15:32 (twenty years ago)

that valildator is only objecting to the content:encoded within the channel tags - inside the items is where content should be. i've tried changing the version to "2.0" and removed the guid and content nodes from inside the channel and it validates ok.

http://feedvalidator.org/check.cgi?url=http%3A%2F%2Ffreakytrigger.co.uk%2Fscripts%2Ftest_ilx.xml

so i'll make that a change when i remember.

Britain's Obtusest Shepherd (Alan), Thursday, 3 November 2005 15:52 (twenty years ago)

i just need to make a new item node for the question - as it stands its part of the channel description, which is obv what's screwing it up

Britain's Obtusest Shepherd (Alan), Thursday, 3 November 2005 15:53 (twenty years ago)

FEED ME

RSS ENTERPRISE, Thursday, 3 November 2005 16:40 (twenty years ago)

thread rss should now validate ok, even though i've not changed the declaration from 0.91 the content module is still being parsed ok.

er, all i did was remove the guid and content nodes from the channel node outside of item nodes. if that's clear.

Britain's Obtusest Shepherd (Alan), Tuesday, 8 November 2005 23:32 (twenty years ago)


This thread has been locked by an administrator

You must be logged in to post. Please either login here, or if you are not registered, you may register here.