12b5 Trending Us
logo

On March 5, I pulled the trigger on soft launching a new product, jsonip Pro http://getjsonip.com. My core goal failed dramatically, though I had some success around the periphery. There’s a few lessons here, some technical and some ethical. If you just want the summary, just scroll to the bottom.

Background

For some quick background, I have been running a free service called jsonip.com since November 2010. Its a utility service that returns a visitor’s IP address in a JSON object. Supports CORS and JSONP as well.

With literally 0 (zero) dollars spent beyond monthly hosting and just word of mouth via Twitter and Hacker News, jsonip has gone from 10 requests a week to over 10 million requests a day. Over the last couple of months and after many conversations of beer and whisky with friends, people kept saying “and that’s free?” Yeah, I replied. Its a simple utility and I’m happy that people find it useful. But ever since jsonip has crept over the 10 million a day mark, I’ve kept asking myself if there was anything more I could do. Is there any way that I could turn this into a product that people might pay for?

I was talking with a buddy in Seattle recently and telling him about it. He asked if I had considered adding geoip lookup, and that was the pebble that started the avalanche in my brain. I realized that there were different features I had been wanting to add to jsonip for over a year, and that I can bundle all of those together and more, and offer something that will have a lot more value than just basic IP lookup. Hence, jsonip Pro was born.

Going Pro

I’ve built enough products on my own and for various companies, along with studying enough startup literature, to know the value of the MVP. In my case, I already more or less have the MVP. Its http://jsonip.com. Its been running for years, has hundreds of users, and supports millions of requests a day. What I know is that offering a paid product is going to be something different. There are different things to take into account:

  • How many features do I need complete?
  • How much work is required to complete all the features?
  • What are the unknown unknowns? (I’m a single developer. There’s stuff dealing with payments, scaling, etc that I know about. What are the things that I *don’t* know about?)

I gave these questions a lot of thought and came to the conclusion that its going to be a bit of work to get this going. Not insurmountable, but a heavy investment in time for me.

The MVP of MVP’s is interest. Are there going to be enough people interested in the product I’m planning to justify the time and effort to put into building it?

One popular way to handle this is what I term a “soft launch”, though of course that phra 2ee3 se has multiple meanings. To me, it means getting a signup page out that describes your product. Collect emails and comments. Track with Google Analytics. See what the reactions are on Twitter. Post to Hacker News and gauge the responses (if any).

Prep

I have my list of features. They’re posted on http://getjsonip.com. I have a good idea of the total time its going to take to complete everything.

Its the unknown unknowns that bite you in the ass. More on that in a second.

For this launch, I wanted to hit everything perfectly. I spent a few days working on the signup page. Its hosted with LaunchRock. They’re free and work pretty good. Their UI is pretty usable but needs some improvement. Honestly, they’re better than anyone else I found and I didn’t want to host this myself. That would have involved setting up signup capture, integrating email services, etc. Too much work for  a 1-use signup page.

The rest of my launch strategy involved posting on Hacker News, sending tweets to people that were known jsonip.com users, and sending a few emails to people I know (under 10 people).

I got everything ready, did some research on the best time to post to HN (morning or afternoon), then pulled the trigger.

Merde

Some people will criticize me for what follows. I’m kicking myself for it too. Basically, the main community I know about and have been a part of for years that deals with launching products and startups is Hacker News. I have a fairly high karma level there and frequently interact via comments and submissions. I don’t have a huge Twitter following nor do I have an extensive email list of interested parties. Hacker News is basically the main target at this point for me.

Since my main goal at this stage was to gauge interest, I needed eyeballs. I wanted at least a few hundred people to take a look at getjsonip.com, signup if they were interested, leave a comment, or send me an email, or just go away. Any combination of those actions provides me with information I need about whether to proceed or not.

My strategy was executed like this:

  1. Post on Hacker News in the morning, http://news.ycombinator.com/item?id=5326491
  2. Go on Twitter and look for people that had talked about it at some point. Send them an @ reply of the form, “@<person> launching jsonip Pro. Take a look news.ycombinator.com/item?id=5326491″.
  3. Send an email to my tiny contact list with roughly the same message, again linking to the Hacker News post.

Since I have limited eyeball-getting-resources, the idea was to use multiple channels, but focus everyone to HN with the hope that if even a couple of folks thought it was an interesting idea, they might spare an upvote. I’m sure by now you’re starting to see the problem.

If anyone remembers back a few years to Digg’s heyday, they had a massive problem with voting rings. Groups of users, or more often groups of accounts controlled by bots, would all vote for the same story in order to push it to the front page. Digg had lots of traffic and making it to the homepage was valuable at the time.

Hacker News is a *very* popular site these days. We face similar issues. Of course, this didn’t even occur to me the morning of as a problem. Like I said earlier, unknown unknowns.

“Soft” Launch

Over the course of 1.5 hours, I executed. HN Post, done. Tweet, tweet, tweet. Email.

As I made breakfast, I immediately start getting feedback on Twitter. All positive!

I got a couple of email replies, also positive.

I would occasionally check the Hacker News post. After a couple of hours, it was up to 8 votes. That’s often, but not always, enough to at least make it temporarily to the bottom of the front page which is all I needed anyway. But then a funny thing happened on the way to the Forum.

The more votes the post got, the further down the http://news.ycombinator.com/newest page it got. When it was 300+ and I realized that 300 new stories hadn’t been posted in 2 hours, I started realizing what was going on. After a couple of searches and getting a hint from a friend, it became obvious.

Since the votes were coming from visitors that had hit the link directly, their votes weren’t being counted. And while I can’t confirm it, I suspect each additional vote just accelerated the downward process in /newest.

I had inadvertently created a voting ring.

I *detest* spammy shit. One of my favorite scenes is in the book Daemon where the daemon geo locates the main email spammers in the world and then hires hit men to assassinate them all in the span of a few minutes. Global spam drops to near nothing overnight. I’m not sure how HN does it, but the way I would do it is that any votes coming from users on pages with no news.ycombinator.com referer get sent to the special level of hell reserved for voting rings. Yet here I had done one of the very things I hate the most. Merde.

If not a voting ring mechanism, then lots of users were flagging the post. That’s possible too, though I think unlikely.

Aftermath

Lets see. I screwed up my mini-launch.

Using what limited resources I have, I tried formulating a plan that would get the most feedback I could reasonably expect. I did get a lot of positive feedback in proportion to the sample size that actually saw http://getjsonip.com, but near 100% positive feedback isn’t actually that useful at this stage. Its a little like showing something to your friends and family and them all saying what a smart cookie you are.

What I was hoping to get was a scale of interest, or indeed no interest. I value the commentary of fellow HN users, but sometimes you even end up with lots of “awesome +1″ comments from well-meaning people. That’s very encouraging, but what you really need to see are critiques in combination with the good stuff. In your analytics, you need to see that you had X overall visitors, they stayed for N time, Y percent signed up, etc.

I had less than 10 visitors, 8 upvotes from people I know or that use jsonip.com, 2 signups from unknown people, and 1 signup from a friend of mine. (Love ya buddy, but you don’t count!)

There’s a lot of encouraging signals in that data, but the sample size is too small to be really useful at this point.

Saving it

You might have guessed by now, but there’s an ulterior motive for writing this post.

My friend with the most excellent hints was the one that initially alerted me to the possible direct-link-voting problem. He also said something that prompted me to write up this experience, “HN readers would like that blog post.”

What I’m hoping is that by drawing attention to how I screwed up my soft launch, I might still be able to garner enough attention to complete the study I started with. Its also to describe my experience, and hopefully provide a road sign for other people working on their own products.

Lessons

  1. If you’re starting from scratch, build a minimal viable product. Often that’s just one feature. Other times, its just a signup page to measure interest. Don’t waste time on building lots of stuff that people end up not wanting anyway. Engage and measure.
  2. If you have a successful MVP, iterate and measure. Add feature B and see how users user or like it. Repeat for C, and so forth.
  3. If you’re in a situation like mine and you have a successful product, but it has a narrow focus, you can’t just add feature B. In my case the new product adds lots of extra information but it will take me time to build and test everything. Not a lot of new features, but they require a lot of work. Start with a signup page with your existing user base and see if they will be interested. This is also hard in my case because most of my user base is anonymous to me.
  4. Know your audience. For me, my audience is developers and engineers. They frequent Hacker News, so that is my target.
  5. When you have limited “eyeball resources” as I call them, focus your resources towards one target. In my case, I would get the most views if I was able to get to page 1 or 2 of Hacker News for a couple hours. Your target may be completely different.
  6. If you’re going to do what I did, don’t tweet/email people to the direct link. Ask them nicely to find your post on the /newest page and vote from there. Its a bit gamey, but if someone actively goes out of their way to find your post and upvote you that’s a really positive indicator even if you don’t make it to the front page. Otherwise, your post is going to go down down down. Also, don’t do this to game Hacker News with your spam. I hate even advocating this technique, so use it with care and respect.
  7. If your launch fails to meet your expectations/needs, consider following up with a detailed post about what you did. It might work. (I don’t know yet if this one will.)

Summary

For those who skipped directly to this point, let me summarize for you.

I am working on launching a paid version of http://jsonip.com. Its called Pro. It has lots of additional features. Check out http://getjsonip.com for the details.

In order to first determine if there would be enough interest to invest the time to build the Pro service, I decided to do a soft launch using just a signup page to gauge interest. This went spectacularly wrong.

I don’t have a lot of resources in terms of Twitter followers and email lists to promote things. To get the data I want, I was hoping to use a post on Hacker News to get perhaps a few hundred views to get some commentary, signups, or no interest at all. Any combination of those would tell me whether I should proceed or not.

I directed the handful of tweets and emails I was able to send to the HN post. Turns out this seems to have activated a voting ring detector and pushed the post so far down Satan wouldn’t find it. I inadvertently created something I hate passionately, spam.

On the plus side, the feedback I *did* get was all positive and resulted in 2 signups, but the sample size was too small to be conclusive.

I’m writing this post for several reasons. To document this process, to help others working on their own products, and possibly to get enough feedback on the idea, http://getjsonip.com, to determine whether or not to move forward.

1ff8

I started a utility service in November 2010 called http://jsonip.com. At its core, all it does is return your IP address as a json object. Simple, right?

Its now close to serving *10 million requests a month.

* For the last month, there’ve been 9.3 million requests to the site and that’s increasing fairly steadily. I don’t know when it’ll breach 10 million, but it will soon.

It had occurred to me one afternoon that there should be a way for javascript running on a website to get the user’s IP address, if needed. Javascript can’t do this on its own because of how the browser sandbox is built. Implementing this on your own server is very easy, and is often done that way. There were other sites that did it too, like jsonip.appspot.com, but they were often down or in this case, “Over Quota”.

It was an easy weekend project. I wrote it in node.js and put it up on my Slicehost server, then posted a link on Hacker News. It got 10 votes, and that was it. I forgot about it for a while.

A few months later, imagine my vast surprise when someone else posted about the site on HN again. At almost 160 votes, I’d say that made the site get noticed.

At various times over the last 2 years, I’ve watched on Twitter as someone finds out about it and tweets it, then a veritable Cambrian explosion of re-tweets start spreading out. One of the most fascinating things I’ve seen in the last 2 years was watching one such occurrence as eventually hundreds of re-tweets were sent out over several days. If I knew more about data visualization techniques, it would have been very interesting to graph and watch how it happened. I feel quite privileged to have seen one of my projects go viral like that, as its never happened before.

Since then, I’ve made a few improvements and traffic has steadily climbed. It supports CORS, parameter requests, and a little /about info too. I’m eventually going to add IPV6 support, but that’s been tricky to figure out and the need has been low, so its been low priority. (If you are a reader that happens to know more about how to detect IPV6, ping me.)

Since its a simple service and only deserves a simple post, I’ll wrap it up here.

If you’ve read this far, check out my other project Popped At. Its an on-going experiment in visualizing real-time images being shared on Twitter that got its start as a “What’s happening on the ground” tool during the tsunami that hit Japan in March, 2011. It might warrant its own post at some distant point in the future.

Thanks for reading.

- Charles

TLDR: In summary, the original post is entirely accurate. Javascript running in web apps in Mobile Safari are roughly 2x faster than running in fullscreen mode via saving a web page to the home screen. Additionally, javascript is marginally faster in a custom UIWebView running in fullscreen, but still much slower than Mobile Safari.

There was a post on Hacker News earlier today that demonstrated the new Nitro javascript engine for Mobile Safari only appears to be used when a web app is running in Mobile Safari, but not when that page has been saved as a home screen object and then runs in fullscreen mode.

The post is here: IOS 4.3 Nitro JS engine disabled for full screen apps and uiwebview and the Hacker News post is here: http://news.ycombinator.com/item?id=2317804

I’ve run some numbers using the page from the HN post. The test embeds v0.9.1 of the Sunspider javascript test, which can then be run from the device.

I ran the following tests using a GSM iPhone 4 and iPad v1 32gb w/ 3G, both upgraded to IOS 4.3.

My tests included 3 uninterrupted runs of Sunspider in each of the following situations:

  1. Mobile Safari, native browser
  2. Page saved as home screen icon, full screen
  3. Custom iPhone app using a UIWebView that directly loads the Sunspider test linked to originally

Numbers:

ipad v1 (browser):
page1: 8145.2
page2: 8149.6
page3: 8166.3
avg: 8153.7ms
iPad v1 (fullscreen):
page1: 8383.7
page2: 8374.0
page3: 8201.7
avg: 8319.8ms
iPhone 4 (browser):
page1: 3981.3
page2: 4110.1
page3: 4087.5
avg:4059.33333
iPhone 4 (fullscreen):
page1: 10383.4
page2: 10594.6
page3: 10572.7
avg: 10416.9
iPhone 4 (fullscreen, custom UIWebView app)
page1: 9400.0
page2: 9422.8
page3: 9431.4
avg: 9417.6666

iPad v1 (browser):

  • page1: 3320.3
  • page2: 3248.5
  • page3: 3241.8
  • AVG: 3270.2 ms

iPad v1 (fullscreen):

  • page1: 8383.8
  • page2: 8375.4
  • page3: 8397.2
  • AVG: 8385.4666 ms

iPad (fullscreen, custom UIWebView app)

  • page1: 7689.7
  • page2: 7656.7
  • page3: 7703.9
  • AVG: 7683.4333 ms

iPhone 4 (browser):

  • page1: 3981.3
  • page2: 4110.1
  • page3: 4087.5
  • AVG: 4059.33333 ms

iPhone 4 (fullscreen):

  • page1: 10383.4
  • page2: 10594.6
  • page3: 10572.7
  • AVG: 10416.9 ms

iPhone 4 (fullscreen, custom UIWebView app)

  • page1: 9400.0
  • page2: 9422.8
  • page3: 9431.4
  • AVG: 9417.6666 ms

Finally my original tests were incorrect for the iPad. I had started the upgrade from IOS 4.2 to 4.3 but it had not completed. So, the following numbers are recorded for the iPad v1 using 4.2. Basically, in Mobile Safari javascript is more than 2x as fast javascript run in fullscreen mode.

iPad v1 4.2 (browser):

  • page1: 8145.2
  • page2: 8149.6
  • page3: 8166.3
  • AVG: 8153.7ms

iPad v1 4.2 (fullscreen):

  • page1: 8383.7
  • page2: 8374.0
  • page3: 8201.7
  • AVG: 8319.8ms
Apple’s introduction video for the new iPad has undergone some changes, quietly.
When Steve Jobs demoed Safari on the iPad on stage, it was obvious that Flash wasn’t on there. Several sites he visited had the now-traditional blue block in place of the Flash player.
In the introductory video that was previewed and later put online, around 2:11 you see the New York Times homepage. A section of the page that uses Flash is clearly visible in the video. This has led to speculation that the iPad will indeed support Flash. No such luck for those that want it.
In an un-announced update to the video, that section has been re-edited to show the blue block.
View the videos yourself and compare. Right around 2:11.
Original: http://www.youtube.com/watch?v=h-aVbSmfTFs
Updated: http://www.apple.com/ipad/
(On a side note, I am on the side of *not* wanting Flash on the iPhone OS (iPhone, iPod Touch, iPad). Its slow, buggy, and just a bad experience overall.)

Apple’s introduction video for the new iPad has undergone some changes, quietly.

When Steve Jobs demoed Safari on the iPad on stage, it was obvious that Flash wasn’t on there. Several sites he visited had the now-traditional blue block in place of the Flash player.

In the introductory video that was previewed and later put online, around 2:11 you see the New York Times homepage. A section of the page that uses Flash is clearly visible in the video. This has led to speculation that the iPad will indeed support Flash. No such luck for those that want it.

In an un-announced update to the video, that section has been re-edited to show the blue block.

ipad

View the videos yourself and compare. Right around 2:11.

Original: http://www.youtube.com/watch?v=h-aVbSmfTFs

Updated: http://www.apple.com/ipad/

(On a side note, I am on the side of *not* wanting Flash on the iPhone OS (iPhone, iPod Touch, iPad). Its slow, buggy, and just a bad experience overall.)

VirtualBox is a free, lightweight virtual machine simulator from Sun. The current version is 3.0.10.

One of the uses of VirtualBox is to run a web server or other application from a virtual operating system on your computer, whether it be Windows, Linux, or Mac.

So, the point of this short post is to describe how to access your web server from your host machine. For whatever odd reason, I simply could not find this documented *anywhere* that was simple. This requires no installation of extra software or configuration of anything on your computer or on your virtual server.

Ok, I’m assuming that you already have your server installed.

  1. Shut it down if its running.
  2. Open up Virtual Box. In the left panel, select your VM and then click the yellow Settings button above it.
  3. In the new view, click on the Network button off to the right along the top.
  4. By default, Adapter 1 should already be selected. If not select it, or if you are configuring a different adapter, select that one.
  5. You should see menus called Adapter Type, Attached To, and Name. Name is probably greyed out.
  6. Under Attached To, select Bridged Adapter. The Name menu should now be clickable.
  7. Under the Name menu, select the network adapter that your computer is using for its internet connection. I am on a Mac on wireless, so my network adapter is en1: Airport. Yours might be one of the others if you are connected via ethernet.
  8. Hit OK, and this window will go away.
  9. Now start your VM image and log in.
  10. Once it is started up, you have to find the IP address that the VM is now using.
  11. If you are running a Linux server like Ubuntu, type “ifconfig” on the command line. Look for “eth0″ and the “ifnet addr” near it. In my case, it is 192.160.0.7.
  12. If you are running Windows, open your command prompt and type “ipconfig”. Look for a similar type of IP address.
  13. The IP address you found will be the one that you use to contact your virtual web server.
  14. Open a browser and type that number in as the address. If your server is up and running, you should now see a web page from it.

As an added bonus, its easy to configure a local name that points to this IP address and makes it easy to access your web page in the future. The steps are nearly identical for Mac, Linux, and Windows users. Since I am on a Mac, I will describe the process for us. For Windows users, do a quick search on where to find your Hosts file. The information I describe here applies, but your hosts file is in a different location.

  1. Mac users: Open a terminal.
  2. Type ’sudo pico /etc/hosts’ and enter.
  3. Somewhere at the end of the file, add something like “localubuntu 192.168.0.7″. Of course, “localubuntu” is the address I want to use. Feel free to name it whatever you like. Also, the IP address has to match the one that you found in the earlier steps with “ifconfig” or “ipconfig”.
  4. Hit control-o and enter to save the changes. Closing the terminal window will save the changes system wide. No reboot should be necessary.
  5. Now go back to a browser and try going to “localubuntu” or whatever you named yours and you should now be hitting your web server.

Feel free to leave comments, suggestions, or questions about any of this.

Why I use a Mac and not Windows

By Geuis on November 8th, 2009
I’m a front-end engineer with a side hobby in video production. I have a Macbook for personal use. I use a high-end Mac desktop at work. For my video editing, I use a high-end machine I built myself that has Windows 7 on it. Read the rest of this entry »

I ran into a problem today with UTF-8 encoding on my Mac(10.5.8), running a Java/Tomcat6 environment. It took a while to figure out, so I’m posting here in the hopes it helps others in the future.

Mac OS uses its own variant of the Java SDK. The default character encoding is MacRoman. (Read this page, scroll to “Character Encoding”). This can cause problems, such as my situation, where we are consuming a service that encodes its data as UTF-8, operates or transforms the data within our application, then outputs it again as UTF-8. The original UTF-8 data was being converted to MacRoman and then back out to UTF-8. Corruption ensued.

Depending on exactly what your problem is, I identified 2 general f 1115 ixes. I only needed the first one, but I want to document the 2nd as well.

  1. Add URIEncoding to both the Java HTTP and AJP Connectors
  2. Add “-Dfile.encoding=UTF-8″ to your JAVA_OPTS environment variable.

Fix #1:

  1. Edit your server.xml file. This is typically in /apache-tomcat/conf/server.xml.
  2. Look for the HTTP Connector, mine looks like this: <Connector port=”8080″ protocol=”HTTP/1.1″ connectionTimeout=”20000″ redirectPort=”8443″ useBodyEncodingForURI=”true”/>
  3. Add the uriencoding to it: <Connector port=”8080″ protocol=”HTTP/1.1″ connectionTimeout=”20000″ redirectPort=”8443″ useBodyEncodingForURI=”true” uriencoding=”UTF-8″/>
  4. Look for the AJP Connector: <Connector port=”8009″ protocol=”AJP/1.3″ redirectPort=”8443″/>
  5. Add the uriencoding to it: <Connector port=”8009″ protocol=”AJP/1.3″ redirectPort=”8443″ uriencoding=”UTF-8″/>

Fix #2:

  1. In my setup, I have added my JAVA_OPTS and other environment variables to my ~/.bash_profile. I am assuming that you already have your dev environment setup and know where your JAVA_OPTS are. This is my setup.
  2. From the terminal: sudo pico ~/.bash_profile and find the line with your JAVA_OPTS. Again, this is my config line and yours may be different.
  3. Add “-Dfile.encoding=UTF-8″ to it: export JAVA_OPTS=”-Xmx768m -XX:MaxPermSize=256m -Djava.awt.headless=true -Dfile.encoding=UTF-8″

It took me a few hours of searching around and it seems like these are the general settings that most people recommend. For me, it was the combination of both Connectors that made it work. It will probably be different for other people depending on your setup.

For extra info, visit these links for more info:

Tomcat and UTF-8

Apple’s Java Docs

The Goal – Get Page Speed Running on Firefox3.5 Beta I’ve been using Firefox3.5b as my primary browser more frequently because its just damned faster than FF3.0. I’m also a front-end engineer and my life online isn’t complete without Firebug. So I inst ee3 alled that, and on a whim wanted to install Google’s Page Speed Firebug extension. Except it wouldn’t. You probably aren’t reading this unless you know what Page Speed is already, but if you don’t and want to know more visit http://code.google.com/speed/page-speed/. Needless to say, I got this running. Kinda. Page Speed has some “bugs” in FF3.5 right now. This is simply a write-up on how to get it installed right now. This document will likely be out of date in a couple months.

Also, I am not providing a download for my modified Page Speed extension because:

  1. It will be out of date soon.
  2. I don’t want to deal with hosting it.
  3. And I don’t want to deal with comments from people who just install it and get any of the errors that result. This is just a how-to.

What’s Needed

You need Firefox 3.5 Beta. Go here.

You need Firebug 1.4 Beta. Go here.

You need Page Speed. Go here.

Install the Firefox 3.5 Beta. When you get that going, install the Firebug 1.4 Beta extension.

STOP HERE. READ ON FIRST.

The Problem – Page Speed Isn’t Designed For Firefox 3.5 Beta

After I got this going, Page Speed was giving some errors. Basically, it looks like the page performance tab works just fine, but the page speed activity tab doesn’t. And it produces some errors. Oh well, lets continue.

What we’re doing is increasing the “maxVersion” value in the page-speed.xpi extension to allow FF3.5 to install it.

Steps

  1. Download the page-speed.xpi and save it locally on your machine. Direct Link
  2. Rename the file from “page-speed.xpi” to “page-speed.zip”.
  3. Un-archive the zip, aka unzip. This creates a directory called “page-speed”.
  4. Navigate to “page-speed” directory.
  5. Edit “install.rd” with your favorite text editor.
  6. Search for “3.0.*”
  7. Change to “3.5.*”
  8. Save the “install.rdf” file.
  9. On a Mac, select all of the contents of the page-speed directory, right-click and choose “Compress 6 items”. This creates “archive.zip” in the page-speed directory.
  10. Are you on Windows? I’m sure the steps are similar. You really should just get a Mac, because “I’m a Megan”, not a piece of under-performing commodity hardware with an over-priced OS and no quality pre-installed software.
  11. Rename “archive.zip” to “page-speed.xpi”.
  12. Drag the new “page-speed.xpi” into any open Firefox 3.5 Beta window and you should get the extension install dialogs. A restart of the browser is required after installation.

If you get an error like: “Error: Firefox could not install the file at because: Install script not found -204″ its because you created the archive wrong. See notes from above.

After Installation

Assuming everything went well, you should now have Page Speed available in Firebug. In my testing, the Page Speed tab works great. However, the Page Speed Activity tab generates some 1ff8 errors and won’t run. I have no idea or ambition to fix this particular problem. Maybe someone more outgoing than I am can come up with a fix for this.

Lots of people have been having problems spoofing their MAC addresses on their Macs with Leopard 10.5.6. The technique has changed just a bit in the last couple of OS updates, but its really, really easy. There’s a couple of gotchas that can make it confusing, so I’m going to lay those out. Make sure you read everything first.

Read the rest of this entry »

Easy jQuery Tooltip

By Geuis on March 6th, 2009

Pretty basic post here. At work the other day, I needed a quick tooltip and didn’t want to install an over-burdened jQuery plugin, so I whipped this up. The usage is pretty basic, in that it uses the the “alt” attribute for the tooltip text. You can change the “x/y” variables to control the position offset from the mouse. Customize the styling in your own stylesheet. A sample is provided below.


var tooltips = { //tooltip to show Alt text
init:function(selector){
x = 10;
y = 10;

jQuery(selector).hover(function(e){
var tip = jQuery(this).attr('alt');
jQuery("body").append("

"+ tip +" ");
jQuery("#btooltip").css("top",(e.pageY - xOffset) + "px").css("left",(e.pageX + yOffset) + "px").fadeIn(250);

}, function(e){ jQuery('#btooltip').remove(); });

jQuery(selector).mousemove(function(e){

jQuery(selector).css("top",(e.pageY - xOffset) + "px").css("left",(e.pageX + yOffset) + "px");

});

}
}

jQuery(document).ready(function(){
//init tooltips
tooltips.init(jquerySelectorHere); //use any kind of normal jQuery selector.
});



You also need some simple styling. The only thing required is for display to be none for the fade-in to work. Here’s a sample.


#btooltip{
display:none;
background-color:#cc0000;
border:2px solid #000;
padding:5px;
}
0