levik
20030608 09:07:53 
500!
Hey, everyone! We're up to 500 problems today! (For those counting, the site's up about 15 months)
Thanks go out to everyone who's contributed, wether by posting comments or submitting problems. The site would not be what it is without you! 
Bryan
20030608 09:18:50 
Re: 500!
Levik, is that 500 problems posted, or just 500 problems in front of my latest submission in the queue? Just kidding  this is a great site; I'm not surprised at all by it's success, or yours. Please keep up the good work :) 
Gamer
20030608 13:35:35 
Re: 500!
Yay... I agree with Bryan. It's like: Your problem is as place 10430953 in the queue. 
Cory Taylor
20030609 06:13:46 
Re: 500!
February 9 marked the 300th problem, and as of that date we had 70 problems in the queue. Today is June 9, only 120 days later, and we have 470 problems in the queue. At this rate, less than 2 weeks from now, there will be as many problems in the queue as there are which have been posted! 
Gamer
20030612 09:03:13 
Re: 500!
Now it's June 12, and there are exactly 500 problems in the queue (at this time), this site really has lots of problems! :) 
DJ
20030625 01:22:49 
Re: 500!
More than two weeks later, still hovering around 500, and slowly increasing... 
levik
20030625 01:58:53 
Re: 500!
Ah, but only because Ravi dropped like 25 overnight.
His problems don't really slow us down, since he's got the top two spots reguardless. 
Bryan
20030625 05:34:31 
Re: 500!
Strictly from my interest in solving problems, I am curious why he has the top two spots regardless. friedlinguini said the same thing before and I never asked. 
Gamer
20030625 06:09:03 
Re: 500!
From what I understand, I don't think it's anything manual. The whole idea is Ravi would have lots of problems in clumps in the queue if it wasn't for queue weight. But, since there is queue weight, only his first 2 problems would appear. But when one of his gets off the queue, another one gets back on because he submitted it before any of the recent problems were submitted. For example:
Suppose the queue only had 6 problems in it. (with only 2 from each person) and RRRARBARACBBC... was the order the problems were in (R is Ravi's problem, ABC are someone else's)
When Ravi drops 3 of them off, they sit in line together. So far the queue would look like this: RRABAC, because you would skip over any of Rs after the first two and any A after the first two.
Then the first R gets approved for the site, so the line looks like this: RRARBARACBBC..., and the queue looks like this: RRABAC. There are still two Rs because out of the 6 next in line, at least 2 are Rs. Then after the next R is taken off the site (RARBARACBBC...), the queue looks like RARBAC. Potentially, if Ravi goes on some long vacation (as seen by the next part of the queue) he could lose his spots in the queue. After the next 3 problems are put on the site (BARACBBC), the queue would look like BARACB, and there would on be 1 R.

friedlinguini
20030625 06:22:41 
Re: 500!
This is why I think owner the top spot in the queue should be rotated. 
Gamer
20030625 08:29:10 
Re: 500!
Why is the "top spot" better than any other spot? Just because it usually gets voted on first? (Note: Ravi doesn't have any problems in the queue as of now... maybe they all got deleted) 
Gamer
20030625 08:30:31 
Re: 500!
I mean the problems in the queue got deleted... so vote on the problems now because by tommorrow 2 of them won't be there for voting (as Ravi's will have taken their place) 