It would be a nice feature, but I rather suspect that the overhead of moving from a simple high-watermark-per-user scheme to one that requires the storage of per-user lists would be excessive in terms of database space and performance.

You'll get a lot of cred if you can offer up code that doesn't cause a performance hit.

I suppose because of the way I use newest nodes, I don't have this problem -- I run through the nodes that look interesting, middle-clicking, which opens up the pages in tabs behind the current one in my browser. That done, I click on "I've checked all these" and page through the tabs. Should I be interrupted, I fall back to the "visited" link color as TomK32 notes.

perl -pe '"I lo*`+$^X$\"$]!$/"=~m%(.*)%s;$_=$1;y^`+*^e v^#$&V"+@( NO CARRIER'

--
Ilya Martynov (http://martynov.org/)

I've never gotten the Tk Newest Nodes Client to work, tho. See Re: Newest Notes by Old Thread vs. New Thread for details. YMMV.

        - tye (but my friends call me "Tye")

I had cookie trouble with the PerlMonks::* modules as well. It was a while ago, but I think these two changes fixed it for me.

• BEGIN {
    # This dir needs to be writable by you (or perhaps your webserver).
    # Your cookie and cache of node information will be stored here
    #
    $ENV{HOME} = $ENV{PERLMONKS_RCDIR} = '/path/to/some/writable/dir';
  }
  [download]

• Using $n->add_pm_cookies() specifically instead of the more general $n->add_cookies().
If nothing else, tweaking the two environment variables -- HOME and PERLMONKS_RCDIR -- might fix the immediate problem.

-Blake

--
paco for president
TomK32 - just a geek trying to change the world

I also find that clearing the clutter is an all-or-nothing proposition annoying. Iexpect, though, that dws is correct in that the overhead might be excessive.

OTOH, the whole voting thing seems to be per-user, per node, isn't it? Given that, how much more overhead could a simple "I've seen it" flag be?

Of course, even so, building the Newest Nodes page might take too long ...

dmm

blakem tried to hack xNN but gave up and wrote his own, and it looks much easier to hack on as a basis for doing all sorts of wonderful and frightening things with the newest nodes.

The newest nodes node on PM is then just a fairly brutal rendering of the raw ticker, and it will probably stay that way. If you want to get fancy, you have to do it off-site, CPU oblige.

g r i n d e r
just another bofh

print@_{sort keys %_},$/if%_=split//,'= & *a?b:e\f/h^h!j+n,o@o;r$s-t%t#u';