Newest Nodes too big?

[Russ]

Hello again, all.

I've been away in Kansas City, where my connectivity has been worse than atrocious, forcing me to *gasp* abandon Perl Monks for a brief hiatus.

I've missed you.

As I now attempt to return, I find that I cannot access Newest Nodes. It loads (to about 260K of data), then says, "Document Done," but nothing appears. I have left it running overnight (assuming this was just the legendary Netscrape rendering engine at work) to no avail. Further, View Source fails to list the HTML, hanging and refusing to display more than the first few lines.

Of course, this is probably just "Yet Another Communicrater Bug."

So, my questions:

• Have you seen this behavior before?
• Would some enterprising Monk be so kind as to remind me of the HTML params to manually effect "I've seen all of these"?

Thank you for your assistance. :-)

Russ
Brainbench 'Most Valuable Professional' for Perl

[Adam]

This is not a new problem. I tried using the "I've read these" button for awhile, but I didn't like the long lists of nodes if I didn't check in for a couple hours. I posted several solutions for this here. A simillar solution was posted some time prior (and deserves your ++ votes) by maleteen2000 here

Other nodes that raised this complaint are:

• Problem with newest nodes
• Suggestion for Newest Nodes
• Massive Newest Nodes Page
And I'm sure there are more. (Those were just a couple I found searching for 'Nodes Newest') Sigh I suspect that until Vroom gets a chance to look into a solution your best bet is to clear the flag BEFORE going on an extended vacation.

[le]

Yes, I have seen this behaviour, too. I asked vroom to fix it.

I'm not sure if this a Netscape bug, I also considered a server timeout, because my connection was too slow to slurp the whole "Newest Nodes" page fast enough.

[Jouke]

It's of course always possible to write a small LWP::simple script that gets the page and pushes the button for you ;-)

This is Perlmonks after all...

Jouke Visser, Perl 'Adept'

[ar0n]

#!/usr/bin/perl -w

use strict;

use HTTP::Request::Common 'POST';
use LWP::UserAgent;

{
        my $username = "";
        my $password = "";

        my $url = "http://perlmonks.org/index.pl";

        my $www = new LWP::UserAgent;

        my $req = POST $url,
                [
                        user            => $username,
                        passwd          => $password,
                        op              => "login",

                        pageloadtime    => time(),
                        node_id         => 3628,
                        displaytype     => "display",
                        viewedNewNodes  => "I've checked all of these"
                ];

        print $www->request($req)->as_string();
}


[ar0n]

[Russ]

"viewedNewNodes" -- That's what I needed. Thank You.

All is well. One more minor difficulty solved easily and with aplomb by a gracious Monk. Thanks, ar0n.

Russ
Brainbench 'Most Valuable Professional' for Perl

[Russ]

Yeah. All I really needed was the name(s) of the form elements. In specific, "viewedNewNodes." Coulda slurped and parsed it myself, I s'pose...

;-)

Russ
Brainbench 'Most Valuable Professional' for Perl

[redmist]

I have seen this before. My experience was in IE though. It seemed to stop pulling the page about 3/4 the way into it, and then, when I stopped IE from trying to load the page, it rendered the HTML that it had pulled. In the resulting page, there was no "Clear these nodes" button. I forget how I finally fixed it, but it was solvable somehow.

redmist
redmist.dyndns.org
email::redmist

[little]

If you were used to use the button "I've already checked these" on the newest nodes page, you will only get those newest nodes, since you pressed that button last time. So, there are a lot of nodes you havent seen yet. So the only way seems to make the server not to timeout the request while sending you the 260K file :-).
But I don't know if vroom has preserved a way for unchecking in any other way such as an option under your homenode where u set your preferences.
Have a nice day
All decision is left to your taste

[ar0n]

If you were used to use the button "I've already checked these" on the newest nodes page, you will only get those newest nodes, since you pressed that button last time. So, there are a lot of nodes you havent seen yet.

Not true; when you press the "I've checked all of these" button, you'll see two buttons at the top. The "Clear my last checked flag" button will reset your last checked flag and display all the Newest Nodes created in the last n days (where 1 <= n <= 14).

[ar0n]

[turnstep]

(This is just an update, in case anyone reads this thread. I'm writing this almost 4 months after the top node). Anyway, you can now find a magic button on your home node that will reset the Newest Node "seenit" flag for you.