Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask
 
PerlMonks  

Listing # comments versus # replies

by flyingmoose (Priest)
on Feb 29, 2004 at 16:15 UTC ( #332650=monkdiscuss: print w/ replies, xml ) Need Help??

Ok, this is a very minor suggestion -- but I'll make it just the same -- it seems to me it might be more useful to list "# of comments" on the various front pages, rather than the "# of replies" to a question. A question can have 3 direct replies but 15 comments. This is the way most other message boards work.

The rationale behind this is that it would be fairly easy to figure out if there were more responses to a thread you already read. Often all of the good stuff in a thread is a reply-to-a-reply, which doesn't show up in the main counts. So it's a little hard to tell if there is anything new on a thread without opening it up again...which would increase server load (marginally).

Ideas?

Comment on Listing # comments versus # replies
Re: Listing # comments versus # replies
by davido (Archbishop) on Feb 29, 2004 at 16:43 UTC
    Without knowing much about the site's internals, I would have to speculate that such a feat would require recursively walking the database for each top-level node being displayed, to identify how many total replies and replies to replies have occurred. My guess is that would have an exponential effect on the amount of server load for page loads that contain many top-level nodes with many nth level followups.


    Dave

      Nope. If you can, see for yourself => newlistapproved ( the sql looks like "select count...").

      update: It appears there is some support for this already, but the user setting is missing? I'll investigate.
      update: And patch submitted (The dangerous Signature Settings had it, but User Settings didn't).

      MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
      I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
      ** The third rule of perl club is a statement of fact: pod is sexy.

        Cool deal. As to the grandparent post, I considered that possibility , but I figured the PerlMonks gods were smarter than that given the relatively decent speed at which pages load today... :)

        FYI -- I don't think we have permision to see the nodes you linked, so we will just pretend they had cool stuff on them :)

Re: Listing # comments versus # replies
by PodMaster (Abbot) on Feb 29, 2004 at 16:46 UTC
    I vaguely recall this being suggested before (might be worth checking user settings to see that it's not an option already) and I think it's a fine idea.

    Please don't refer to perlmonks as a message board, because it simply isn't, its so much more :)(I think the monks will agree with me here, including you).

    MJD says "you can't just make shit up and expect the computer to know what you mean, retardo!"
    I run a Win32 PPM repository for perl 5.6.x and 5.8.x -- I take requests (README).
    ** The third rule of perl club is a statement of fact: pod is sexy.

      Yep, it's a Virtual Electronic Exchange for Perl Stuff. It's a VEEPS.

      Please don't turn me into a newt.

        The main difference to a regular messageboard is the availability of permanent links to almost all content, and the availability of markup for convenient linking. It's a bit like a cross between a messageboard and a wiki; the combination here is really quite unique.

        Makeshifts last the longest.

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: monkdiscuss [id://332650]
Approved by kutsu
Front-paged by hsmyers
help
Chatterbox?
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others contemplating the Monastery: (13)
As of 2014-09-16 14:22 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    How do you remember the number of days in each month?











    Results (26 votes), past polls