...to paraphrase a vroom-ism.

A few minor updates to the infamous stats pages: (this actually turned out longer than I expected, so please excuse...)

I'm looking for opinions on adding cookies. Most everyone hates cookies, I know. However, if I added them, I could allow customizing of what fields are displayed in the stats pages, so you could prune off the fields you don't care about, and narrow the display down, possibly causing Netscape to work. I *really* don't want to get into supporting user profiles, by logging into the stats pages. That's more trouble for you, and for me. Would cookies be permissable? Or would I be hunted down and shot, like the dog that I am? If we add cookies, I can also support a default page when you come to the stats site.

Remember to check the news section periodically. Any time any changes are made (fixes, additions, whatever), I put a comment in there.

Stats are generated at two different times. The typical XP related stuff is once an hour, at approximately 13 minutes past the hour. Location, birthday, email, and GeekCode processing is done at about 3:50 AM in the morning, EST/EDT. To minimize the server load, only the homenodes of people that have logged in within the last 25 (yes, 25) hours are checked for tags.

I'd like to thank everyone for such an interest in the pages, all the people who've made suggestions, and particularly footpad and mikfire. mikfire (and his wife Tory) did some of the original graphics, and HTML. footpad has done all the new buttons, and without him, there would be only HTML-type submit buttons, because I can't draw a straight line with a CAD package. And I'd like to thank vroom for being so accomodating for adding fields to the stats, and making the data available.

For those who have asked, the stats pages are written in PHP4. PHP was chosen because I needed (OK, wanted...) a project to compare PHP and Perl. The hourly and daily scanners are written in Perl. The machine hosting the stats is a Abit KT7-RAID motherboard, with a 1Ghz Athlon, 256MB PC133 memory, and two 27 GB Maxtor drives, hanging out the end of a 144K IDSL line.

As usual, when you find the bugs, please email or /msg them to me, and I'll try to take care of them, or at least cover them up with a lot of handwaving, smoke & mirrors, and pointing out that it's really someone elses fault.

--Chris

e-mail jcwren

In reply to More tasty stats goodness by jcwren

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.