Well, not really, but I was fishing for a good title and “to rank or not to rank: that is the question” didn’t seem nerdy enough.
Today I officially broke the top 300k blogs according to Technorati, landing squarely at #293,775. Am I content with this? NO. I aim to be in the top 100k within the next 3 months. Don’t worry, I’ve got a plan of attack, and specifically some big sites with thank you credits coming out.
I’ve upgraded a couple sites to the new Wordpress 2.1, but I’m hesitant to see how some of my more plugin-dependent sites handle the new code. The AJAX draft saving and updated richtext editor is cool, but is it all worth it? I know for a fact that Coffee2code’s customizable post listing plugin breaks, choosing to list pages instead of posts. My fingers are crossed for “related posts” and other database dependent files.
What else is hitting my geekdar this week?
- yahoo is re-releasing their ad network to the public. watcha gonna do, adsense?
- prototype made a big release. I don’t know what I plan to do with this yet, but believe you me, I will.
- I’ve been using firefox pretty exclusively (firebug rocks my world), but some of its annoying tendencies to hog memory and disable text fields have me looking back at safari with nostalgia. and how about getting inquisitor on there already!
Have you tried Firefox 2 yet? I love the textarea spell-checker.
Firefox has always been a bit of a memory hog, but I’ve never had it behave as bad as you describe. Maybe the Windows builds get more love than the OS X builds? Or perhaps one of your extensions are misbehaving? (Firebug, perhaps?)
The most exciting thing about this release of prototype.js is that this is the first one to include documentation.
Yes, that is correct. The premier JavaScript library that hailed the age we now call Web2.0 has not had ANY documentation for the first 2-3 years of it’s existence.
Is that where it came from? I installed the latest release of Google Toolbar at the same time as FF2 and assumed it was a Mountain View addition.
I think the memory issue could very well have something to do with an OS X setting, considering there are specific OS X 3rd party builds. I’ve just never tried them. I know the text area issue is non-plugin related since Natasha’s bare bones installation does the same thing. AND DON’T TALK SMACK ON MY FIREBUG!!!!
Documentation or no documentation, JS is still more than I’m equipped to tackle. Every once in a while when I’m feeling brave I dip into moo.fx and some of the more user friendly scripts. Now that prototype comes with wp2.1, I can’t wait to request some effects from you.
come on eli, post again already, i’m sick of looking at the same page. for real for real. okay, granted you’re busy fixing all the stuff i mess up on my site…..BUT that’s still no excuse!!