If This Then That- Simplifying the Web?

I started playing with it because I always thought Yahoo Pipes was cool but a bit heavy-handed for light things - and I've found myself going back to add more and more tasks. Plenty of services provide some of the functionality (Twitter alerts, etc), but require a separate signup or new login, while ifttt is flexible enough to take care of tons of different cases.

Some of my recently created tasks and the holes they plug:

* RSS feeds that aren't fine-grained enough for my needs (if there's a new item in The Atlantic's Entertainment RSS feed that matches "Game of Thrones," then email it to me)

* RSS feeds that I want to be updated about ASAP, but don't want to have to sign up for (if there's a new item for an eBay search I care about, then send me a message via GTalk)

* Lightweight Twitter alerts (if there's a new tweet that mentions X, then send me a message via GTalk)

Other cool examples of ifttt flows:

http://craigt.co.uk/blog/?p=146

http://web-mastered.de/post/4748705681/iffft-dropbox-update

http://blog.christineyen.com/2011/05/how-i-use-ifttt/

tl;dr - really lightweight, well-designed version of yahoo pipes that is genuinely fun to use.

I have no idea what this is about. Can someone enlighten me?

And before you ask, yes, I know what event driven programming is, and how to tie callbacks to actions. I've written large (>1M process) systems that work by callbacks, events, and message passing.

This seems like a really ingenious way to simplify programming for both programmers and non-programmer-but-still-technically-savvy-people. For instance, this service provides a dead simple way to get an email or text alert for anything you can "trigger" on the available web services.

For programmers, this is also a simple way to hook into external services without having to download/learn their API.

I have been thinking about how to make web services more easily connectable for a while but all of my ideas required some participation from each service. Ifttt still requires a thin wrapper to expose a web service as a channel but after that everything has the same interface.

This is an awesome idea, I'm curious to see what they come up with. Tying things together loosely is exactly what I've been wanting to do for a while (looking at you, Google Reader and Twitter).

i wish more sites were triggered/triggerable in this manner. too many sites assume that they are the only part of someone's workflow, when they aren't.

Interestingly my company Internet proxy blocks you site, how can that be if it's new?