[henrybb]

Damn!

There’s no filter for get_thread()!

Is there any design decision behind not allowing people to hook into that?

As I said, for a full page of posts (30), I’m updating my readlog 30 times, when all I really need to do is get things upstream at the get_topic() and just take the last dimension of the array and make that the last read post in that given topic for the user.

It’d save 29 SQL updates per pageload in busy topics.

So until there’s a hook there, or an epiphany for another spot I could hook into, Unread Topics 0.4 stands as the best I can do solution for indicating what the user has read so far.