@dkf said:
A more important thing would seem to be to actually go to the first unread post, as opposed to some random other place that appears to be the first post not read by anyone at all.
I think that's the "read tracking" messing up. It seems like it want the top of the post you "read" to be in the middle, or above, of the screen. If you pay attention to the newlevator in the header, sometimes (when the last reply or two are short) you can't reach the last post.
@Maciejasjmj said:
The "go to last unread" toaster has to get the info about the last post from somewhere, so it shouldn't be that difficult to just do the same request it does and emulate the click.
I think that's the best we could do for now, yeah. I buttume that that bit of information is transmitted in a separate block of data you get after the thread has loaded, possibly as some user-related data instead of thread data.
How the hell did we manage to go directly from "software sends too much JSON" to "software doesn't send enough JSON"?