This document discusses the creation of a new website and tool called Smoke that automatically aggregates and translates data from different web services. Smoke takes data sources like photos from Flickr, links from Delicious, and projects from GitHub and outputs the combined and transformed data in various formats like JSON, YAML, and XML. It provides a self-documenting API and is intended to make consuming content from various sources easier for users.

3. Starting with a story, this year in March

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

5. Write codes for fun

6. I wanted to use the internet

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

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

9. a mere 46 minutes later, I was effected

11. “I need a new web site”

12. So, I made plans to build something

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

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

17. I really like union, though...

18. and sort...

19. Smoke
Enter, Smoke

20. Take my website, see the circled image?

21. Take my website, see the circled image?

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

23. The links? Delicious

24. The links? Delicious

26. Projects, from github

27. Projects, from github

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

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

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

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

37. What about those front end guys?

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

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

40. You’ll get a self-documenting api

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

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

43. /smoke/twitter.json

44. /smoke/twitter.json
yaml
xml

45. 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

46. Presented at webjam10/11 in Sydney & Perth