I don't really see how this fits the request. It lets you add (and delete) nodes to be tracked and list nodes that are being tracked, but the only way (as far as I can tell) to check if a "tracked" node has changed is to cycle through the nodes one at a time (and I don't see an interface to make that possible without me retyping each node ID).

I thought the point of building a list of nodes to be tracked was so that one could be told "here are the new replies to any of your tracked nodes" (either with one page load or via notifications sent out by some cron job).

Using your current technique of grabbing information, adding such a feature would not be an efficient use of the server. It would refetch the entire thread list for each interesting thread (and fetch that separately for each user who wants to track the same thread) every time someone wants to check.

To do something like this efficiently, you'd want to use the newest nodes ticker to fetch info about any new nodes since the last time you checked for updates (and not per user). If it becomes popular, then you'd want to not try to fetch info about new nodes if you just did that a short time ago.