November 17, 2003

Every 11 Seconds A Person Creates A Weblog

...we've got to locate that person and stop him.

For the last few weeks I've noticed that Technorati has been crumbling, but I didn't know why. On my 3rd or 4th email to them I must admit I got a bit testy. But then I hadn't heard about what they were up against. Dave Sifry lays it out in Technorati Growing Pains:

Allow me to give you some growth statistics: One year ago, when I started Technorati on a single server in my basement, we were adding between 2,000-3,000 new weblogs each day, not counting the people who were updating sites we were already tracking. In March of this year, when we switched over to a 5 server cluster, we were keeping up with about 4,000-5,000 new weblogs each day. Right now, we're adding 8,000-9,000 new weblogs every day, not counting the 1.2 Million weblogs we already are tracking. That means that on average, a brand new weblog is created every 11 seconds. We're also seeing about 100,000 weblogs update every day as well, which means that on average, a weblog is updated every 0.86 seconds.
Fairly stunning numbers. I just want to say that I apologize for sending Dave a "What Is Happening!?" flame and promise to ease up on his servers by posting less. Except for this one which will now consume .86 seconds of update time.

Posted by Vanderleun at November 17, 2003 8:00 AM
Bookmark and Share

Comments:

HOME

"It is impossible to speak in such a way that you cannot be misunderstood." -- Karl Popper N.B.: Comments are moderated and may not appear immediately. Comments that exceed the obscenity or stupidity limits will be either edited or expunged.

Not a problem - and no need to letup on the posting, I think we can take it. :-)

Thanks for the support.

Dave

Posted by: David Sifry at November 17, 2003 8:22 AM

Adhere to System Appearance. Does your application use all the sweetly colored buttons, delightfully shaded windows, and all the other "bells and whistles?"

Posted by: Juliana at January 12, 2004 3:12 PM

Due to the positioning of the Dock, remember that when you build an application, you have to be sure that new document window sizes and positions do not violate the Dock's space. Dock is temperamental and Dock loves his space. If you default to a window size that expands behind the dock, users will have a difficult time reaching the navigation and resize areas at the bottom of the screen. I can personally say that more than once I have been rather peeved that I couldn't get to an area of the window to resize because the default window settings always pop up behind the Dock. In addition, the new Dock in 10.1 will allow users to position their Dock location on either side of the screen as well.

Posted by: Jocosa at January 12, 2004 3:13 PM

Adhere to File Locations. Make sure that when your users save documents, your application knows where to put them and also gives users flexibility.

Posted by: Jennette at January 12, 2004 3:13 PM

For example, if you see an AIM window peeking out from behind your browser and you click on it, that window will come to the front, but the main application window will not. The Mail.app/Activity Viewer is another example. The Aqua system of layers works well in many instances, but not in all. Thank goodness that the Dock is always there to come to the rescue. I know that clicking on an application icon in the Dock will always result in not only the application coming to the front, but also any non-minimized windows associated with it. And if the application is active but no windows are open, clicking on the Dock icon should create a new window in that application.

Posted by: Quivier at January 12, 2004 3:13 PM

Whether native or not, this is obviously one of the first steps on your way to OS X. Keep in mind that often, the functionality of your code has a lot to do with how your interface is designed. How many developers have come up with great functional ideas from working with their interface or looking at their competitors'? Start working on your Aqua compliance from day one. Don't wait until the last minute.

Posted by: Osmund at January 12, 2004 3:14 PM

At WWDC, I listened to Apple representatives make some excellent points about taking the time to build a 100%-compliant Aqua application, and I think all developers need to look beyond the code and listen to what the folks at Apple have to say

Posted by: Ciriacus at January 12, 2004 3:14 PM

Adhere to Window Models. Document windows, Utility windows, Click-through, Layering, Drawers, Controls. How do users open windows, how do you properly title windows?

Posted by: Erasmus at January 12, 2004 3:14 PM

Dock Animation. Sometimes animating icons in the dock can be useful in communicating the status of the system or application.

Posted by: Annabella at January 12, 2004 3:15 PM

The simple fact is that, when all other factors are equal, where will consumers spend their money? I believe that in the long run, the best looking, easiest-to-use applications will also be the most successful. I think that's why Apple encourages developers to write programs that are 100 percent Aqua-compliant.

Posted by: Venetia at January 12, 2004 3:15 PM

Adhere to System Appearance. Does your application use all the sweetly colored buttons, delightfully shaded windows, and all the other "bells and whistles?"

Posted by: Holland at January 12, 2004 3:15 PM