Can we get a candy cane if our favorite porn performer has posted in a thread?

[Link]

It's a terrific feature, now that we have it. More useful than I'd have thought.

[Link]

I tried it out, but I didn't get it to update very well when existing threads got bumped. New threads work fine.

[Link]

I've done some tests on this with Google Reader. New Posts in new topics or to existing topics end up hitting the reader in 10 - 25 minutes. I've had them happen in as little as 6 minutes.

[Link]

MyYahoo is a little better with party @AEE 2007 being listed as 2 hours old.

I wonder if there are some user-definable settings I've missed.

BTW, I know about the glitch yesterday. Google and Yahoo have worked like this whenever I've tried them out with ADT forum feeds.

[Link]

As an example, my previous post was placed into the ping queue at 3:26 PM and the ping went out to the various blog search indexes at 3:39pm. So we'll see how long it takes to show up.

[Link]

Google Reader still dates the Post your controversial opinions... as "Dec 29, 2006".
But the feed contents are not Neech's original post from that date, but my post from a little while ago.

A guess would be that Google Reader doesn't update the timestamp if it still has an older entry from the same thread in its cache.

[Link]

BTW, the TTL is 30 minutes so they should only be caching it for 30 minutes but I bet they consider it more of a suggestion than an actual time to live.

[Link]

I have changed the feed to see if that matters.

[Link]

I got a little curious and rummaged around for some info and stumbled on this:

Looking through the code of Akregator, I found that, if the "guid" is already present, a hash value, calculated from "title", "description", "link", "wfw:comment" and "slash:comments", is used to check for updates. If the hash differs, the old entry is removed from the cache, and the new one appended instead.
(Disclaimer: I've never looked at any of this code before, but this is how it seems to work, judging from a cursory glance.)

If I've interpreted the source code correctly, and if Google Reader works the same, a simple fix might be to have "slash:comments" indicate the number of replies (and perhaps even have "wfw:comment" link directly to the last reply, if possible).
Another solution could be to have "description" or "title" contain the timestamp of the last change.

If this doesn't do the trick, changing "guid" everytime the thread is bumped may be necessary.

Of course, I could have it all wrong. Unlike yourself, I've never looked at any of this before.

[Link]

BTW, the feeds for individual threads do update whenever there's a new post. That's how I watch specific threads in Google reader.

[Link]

It was never a bug, but a feature. How very Microsoft of you.

So, only use the forum feeds to look for new threads, and then subscribe to each thread that interests you?
I never did that because I figured I'd get a lot of leftover feeds when the threads fizzled out but I still kept them active in case of late posts.

Anyway, I recently started using Rawdog as my main entry point to ADT. It builds an HTML page from a list of RSS feeds, and I got it to re-list threads with new posts.
I'll consider patching Akregator to get it to bump threads with new timestamps.

[Link]

The change that I made earlier appends a last updated section to the description to trigger that hash value change. It should accomplish what you're looking for without patching.

I didn't want to start creating new GUIDs for each new post in a thread because it would start generating tons of duplicate articles for the same thread.

[Link]

Not to worry, Rawdog works very well as an "Active Topics" replacement, and Akregator's source code is only about half a megabyte of CPP and H files, so I can figure out how patch it easily enough, if I really want ADT listed like my other RSS feeds.

Thanks for trying. Much appreciated.

[Link]

Now it think all articles are new every time. ::chuckle:: If it's not one thing it's another.
Ah, well. Nevermind. I guess it's back to "Active Topics" for me, until I get around to patching Akregator.

[Link]

::sigh::
Why can't the various readers agree on how to interpret a damn RSS feed?
I mean, even Google and Yahoo's on-line efforts can't quite agree on what's hot and what's not.

I guess there's a reason for there being so many RSS readers out there: everyone has their own ideas of how it ought to work.
I'll just have to whip up my own Krss.

[Link]

If the multiple articles thing leads you to return to the old guid system, which I'll perfectly understand, I think I will write that patch to bump on pubDate changes.

[Link]

I just need to make a change so that the user is properly redirected to the individual post instead of just the beginning of the thread.

[Link]

BTW, is it just for me that, when clicking on a link in a list of search results, and the destination post is not on the last page of the thread, an incorrect page is shown?

Example.
My pagesize is 50, and the link is automatically changed to this link with "whichpage=27", but page 28 is shown.

[Link]

Excellent. You have been busy with that forum code lately.

[Link]

I think the feed may miss the occasional thread update.
Matchmaker's post in When ADT'ers Vanish never made Google's (or my reader's) list.

[Link]