marketer

Try again - and sometimes it helps to refresh the page after generating the report. If you think there's a bug shoot me an e-mail hoisie@gmail.com .

Thanks for the suggestion, this is a great idea. I couldn't decide on a link structure for reports, so I just decided to use ids. But more meaningful links would be a useful feature.

Cool, that's actually what I'm building next. A simple deploy hook mechanism. Want to shoot me a quick e-mail? hoisie@gmail.com

Wow, 98 is a great score (higher than Google!)

You're right, there's a lot of noise in the results. If the size reduction is small, like a few bytes, there's no need to show that.

I looked it up, and it says heyo.com is hosted on EC2.. http://whois.arin.net/rest/nets;q=174.129.212.2?showDetails=...

Maybe Rackspace is hiding something :)

Webpagetest is useful - it's the best place to get an IE speed report. The reports can take a while to generate, though.

Awesome, thanks for the suggestions :)

Gomez is probably the largest competitor. They do a lot of enterprise sales, which isn't something I'm planning any time soon.

The long-term goal is to have a subscription service that tracks performance issues. There are other possibilities, like ads, referral programs, consulting, etc..

My goal is to focus on performance, I haven't thought about branching out to other areas yet :) Seems interesting though..

Thanks, the server is heavily loaded right now, so some of the ajax effects aren't showing.

The forward link should work. The report page has a lot of content, and forwarding is done with a lightbox. Try again?

Yeah I've seen them. There are a few tools that do similar things. My long term goal is to be a full stack tool (both client and server side). I'm not sure where Yotta is going.

What's the report URL? I can take a look.

Awesome, glad you found it useful!

Most of that crap is from the Facebook and Twitter buttons :/

The site's getting a lot of traffic right now, but reports should work. I'd try again..

Keep in mind this is the first version, it's the result of a couple months work. There's a lot of features I want to add.

Webkit inspector is a great tool, but it doesn't track performance over time, which is the goal of Slowcop.

YSlow is a great tool - I've used it a lot.

The main problem with using YSlow is it doesn't show performance trends over time. One of my goals for Slowcop is to give a dashboard where you can track performance across deploys.

Also, there are a bunch of other tools and features I'm planning to add, like measurements from different regions and tools that track lower-level HTTP issues.

This is what you have to deal with as a developer on the Twitter platform. Their policies have become so bloated and far-reaching that most apps are in violation.

The scan takes too long, I already backed out. Maybe add an e-mail field that sends you results?

What are some common questions are people asking with this?

It is an unfair advantage, and it's frustrating to watch. For most of the answers, both Ken and Brad were trying to buzz in, but Watson always had better timing and buzzed in first. I'm sure that Jeopardy's buzzing system didn't take robots into account when it was designed, so it technically isn't against the rules. But it does give Watson a huge tactical advantage.

Twitter needs to stop fucking around and charge for their API (with metered pricing). Currently, their incentives are to restict access to save money and bandwidth. If they charge money, their incentives will be the opposite: encourage as many developers to use as much as possible. It'll suck for the casual developer that wants to build a free app on the Twitter platform, but it's clear that there's enough demand for the platform that is has some value.

I think Cheddargetter is friendly to bootstrappers - they have a free plan for up to 20 customers.

Make it a concierge service. Manually match people and set them up on dates (maybe even pay for the dates). It's a lot more work but it's the only way to create incentives to join an empty dating site.

Nobody really uses the non-blocking channel receive operations. I didn't even know it existed until now.

Selecting on multiple channels is, however, is used very often, so this fits that paradigm quite well.

They only seized the DNS. They haven't shut down the site.

Try http://88.80.11.29/

This article is old (from 2009).

The guy needs to read the first chapter in the Ruby on Rails tutorial where it goes over generating models and creating database migrations. There's a very nice api for it.

I though this was a dating site! It wouldn't be a terrible idea for one..

The interface is a little overwhelming -- maybe it's more natural on a mobile device, though. From the video I saw there are too many features. I'm not a musician, but I know a couple and they're not the meticulous type that want to track everything.

It seems Google is deprecating the http resource, though. If you visit http://code.google.com/apis/libraries/devguide.html#jquery, all paths are listed as HTTPS.

This seems like a good solution -- just encourage everyone to use HTTPS to avoid the cache fragmentation.