gbelote

FYI: It looks like there's a rendering bug in Chrome that pushes most of the interesting content below the fold: https://skitch.com/gbelote/r12ay/breakup-notifier

Your last point is very creepy, and something I've never considered before. I hope I never become a computer's computer.

This is gorgeous, nicely done. I find myself wanting a better way of going to the next story, because some articles are very long. Maybe you could add controls? For example, keyboard shortcuts or a floating "next" button (anchored with fixed position CSS).

My guess is yes. I think it's worth trying, at least.

There may exist zillions of sites, but that in and of itself doesn't matter. If they can build a better product that can draw a large enough audience, that's important. I have personally looked around for tools like this, but haven't found anything that really kicks ass. Playing with their tool makes me optimistic -- they may be on to something.

I don't think they have to worry much about duplication. Building the product isn't the hard part, getting users is. Not sure if they'll be successful here, but if they fail it'll probably not be because of a clone.

Good point with the money, that almost certainly be tough. However if their product is useful enough and enough people use it they'll have an opportunity at making serious money.

Once you sign up you can find an upgrade page: http://img.skitch.com/20101011-jgpkhbquapptemp64ggajwhuxx.pn...

Adding an SSH key was part of the sign up page on the website. Leaving blank only prompted me for it again.

Running "curl -k -u user:pass http://api.no.de/heart -X POST" gave no output. I'm noticing in my history that I didn't use https, I guess that's why it didn't work.

Why should I even have to jump to curl to request a coupon?

This sounds like it might be a useful (will pay money for) service, but I have to say my first experience here was weird and slightly obnoxious. Why do I need to give you an SSH key when I first sign up? Why are coupon codes masked behind the API? When I first started it said I could request one, then I saw nothing.

I did figure out that I can request through your API via command line, but it seems like a have to use a weird unicode heart (/heart doesn't work). After futzing with that I discover all coupons are gone. Awesome.

One (arguably important) unknown here is how likely is a 640x480 user to scroll the page vs a 800x600 user.

You can point out to your client that a more real quality is user engagement -- it's not enough to just show content. This is affected by ATF, but a newpaper-like design of cramming content together may not be the best approach.