However, about a half hour ago, the author posted a script update to userscripts which made things work here again. Guess this a case of playing keep-up with the Google developers, and why directly manipulating internal variables can be tricky on active projects.

Anyway, try uninstalling the old version and installing the latest version, changing the list variable to a high number as before. See if that makes things work for you now.

The script appears to directly twiddle Reader internals and consequently goes out of date more often, but the author is actively supporting the script judging by the feedback.

Neat hack. I haven’t had to time to look it over in detail and see how it works yet, but the basic idea is one I’d like to look more closely at before implementing more intensive and messy measures to load all unread messages. I’ll try to incorporate the basic idea, if viable, in the dupe-removing script within the coming week, and do a new version release.

P.S. That one WSJ news link does generate a heck of a lot of entries for testing.

If not all new entries are loaded, a script can automatically open the last loaded entry, mark it unread, and close it, scan to the new end of entries, open the (updated) last entry, mark unread, close, and so on until full new entry load is detected. And the script would need to make sure it didn’t outrun the Google Reader event driver. Nasty ugly stuff, but a workable concept, though it would require quite a bit of new code and logic.

Looks like it’s also possible to hook up code to make the remove duplicates button work with feed entries displayed in expanded mode, as well as the current list mode. At least that is a relatively straightforward enhancement, since it uses the same basic idea as the existing list mode dupe check and could share some code.