Beefy Boxes and Bandwidth Generously Provided by pair Networks
Syntactic Confectionery Delight
 
PerlMonks  

Re: Best post of the (day/week/month/year)

by footpad (Monsignor)
on Mar 29, 2002 at 18:04 UTC ( #155298=note: print w/replies, xml ) Need Help??


in reply to Best post of the (day/week/month/year)

Well, Best Nodes showcases the best nodes of the Day, the Week, and of All Time. (There's a corresponding Worst Nodes, too.) This provides most of what you're looking for, though it might be interesting to tweak things to provide more of a snapshop in time. It would take a bit of work, though.

However, if you really want to see this, I expect that the quickest way to do so would be to do it yourself. I'd probably start by extracting Best Nodes on a daily basis, tracking the appearance of various nodes as they appear, and then managing a database. Then I'd publish the results to an appropriate location (perhaps on the floating server maintained by the statmeister). This type of approach would let you track various appearances over time.

(I'm not sure I'd award additional XP for making it on the lists. That seems like it would arbitrarily inflate the reputation of the node.)

Of course, it might be easier to showcase good nodes using another commonly-used technique. Namely, set aside a portion of your home node for listing nodes of note. Turnstep has done this good effect, as have many others. Nose around various homes nodes and see if you find a style you like.

--f

  • Comment on Re: Best post of the (day/week/month/year)

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://155298]
help
Chatterbox?
[Corion]: ambrus: Hmmm. It makes sense that AnyEvent would implement the push_write itself, but I think I don't have a good idea of where the boundary between AnyEvent and the underlying event system lies... Implementing the timer should give me a better idea
[ambrus]: Corion: push_write is in the higher level abstraction of AnyEvent::Handle, not in the watcher
[Corion]: ambrus: Hmm - rereading Prima::File, that merrily coincides with what Prima does - it tells you "you can read", and you're supposed to read from the fh yourself. I thought it called you with the data already read, which would've been harder to integrate
[ambrus]: you just need an io watcher, created by &AnyEvent::Impl:: Whatever::io(...)
[Corion]: So after talking it through with you even while I'm still not entirely clear on where AE ends and my implementation begins, I think I understand that I only need to implement some smaller parts for each functionality I want to support.
[Corion]: Yeah... and you might even be able to mix and match additional functionality if you have additional async suppliers, like from a separate thread
[ambrus]: You hvae to be careful with the timer, because apparently Prima::Timer insists on being periodic, wheras AnyEvent::Impl:: Whatever::timer should give a one-shot timer watcher

How do I use this? | Other CB clients
Other Users?
Others musing on the Monastery: (6)
As of 2016-12-08 12:23 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    On a regular basis, I'm most likely to spy upon:













    Results (141 votes). Check out past polls.