1.
Starting with a story, this year in March

2.
I’d missed lunch, it was late. What do you do?

3.
Write codes for fun

4.
I wanted to use the internet

5.
Yahoo pipes is pretty awesome and does some crazy stuff for data manipulation

6.
Also, @lachlanhardy had convinced me that YQL wasn’t pure evil

7.
a mere 46 minutes later, I was effected

8.
“I need a new web site”

9.
So, I made plans to build something

10.
Not me, but what I felt like I did about it.

11.
Yahoo pipes relook - Too hard to do what I want quickly.

12.
I really like union, though...

13.
and sort...

14.
Smoke
Enter, Smoke

15.
Take my website, see the circled image?

16.
Take my website, see the circled image?

17.
I grab all those photos from flickr using a special tag to choose relevant images

18.
The links? Delicious

19.
The links? Delicious

20.
Projects, from github

21.
Projects, from github

22.
It takes all your sources and auto-magically translates them based on their content-type

23.
Its like a fucking awesome monster for web services... that shits.. ouu.. well. You get the idea

24.
Its like a fucking awesome monster for web services... that shits.. ouu.. well. You get the idea

25.
You can output your sourced data as...

26.
What about those front end guys?

27.
A rack adapter to drop on top of your app, or simply deploy straight to the clouds that
exposes smoke sources.

28.
/smoke
So, once you’re running, you can hit /smoke

29.
You’ll get a self-documenting api

30.
/smoke/twitter
Say you want to know about the twitter source

31.
It’ll tell you that you need to supply a username for the stream and the formats that smoke-
rack will translate it to.

32.
/smoke/twitter.json

33.
/smoke/twitter.json
yaml
xml

34.
Work only on the value of your mashup. Not the supporting crap. If you’re a content
producer, write API’s and give your users something to consume. Content consumers - Use

35.
Presented at webjam10/11 in Sydney & Perth