I'm going to have to do something about this soon. Feed Digest has experienced a traffic boom. I've just had to turn the wick up on the servers a bit as now 65 digests per second are hammering their way through the system. This would average out at about 165-170 million requests per month at peak, but in reality is somewhere about 120-140 million.

When you're dealing with numbers in the hundreds of millions you try to see if you can monetize those numbers properly. Even 0.01 cents (100th of a penny - a mere 10 cents CPM) per request would yield $13,000 of gross income per month, if I charged per impression.

I already know the current price structure of Feed Digest is totally wrong, not to mention way too low, but I've learned the lesson the right way. The scheme that will replace it will be a lot simpler and make more sense to everyone, although it'll peeve the bargain hunters.

Just a ramble, I've been up too long and need to sleep. It's just a little scary that my homebrew Perl daemon is serving over 100 million dynamic requests per month with the few resources I have at my disposal. In one way it's great that I've managed to pull it off, but on the other.. it's dreading getting those warning text messages that it's down and I'll have a gang of FeedDigest-reliant customers banging at my Inbox within minutes :) (as they should, I admit) I'll also try to have some sympathy for FeedBurner, who are serving some 7.5 billion requests per month! Still, there's a massive gang of them, and there's only little old me.