How To Reinterpret The Web In 180 Seconds

1,809 views
1,714 views

Published on

My presentation from webjam10/11

Published in: Technology, Health & Medicine
0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,809
On SlideShare
0
From Embeds
0
Number of Embeds
19
Actions
Shares
0
Downloads
14
Comments
0
Likes
5
Embeds 0
No embeds

No notes for slide

How To Reinterpret The Web In 180 Seconds

  1. 1. Starting with a story, this year in March
  2. 2. I’d missed lunch, it was late. What do you do?
  3. 3. Write codes for fun
  4. 4. I wanted to use the internet
  5. 5. Yahoo pipes is pretty awesome and does some crazy stuff for data manipulation
  6. 6. Also, @lachlanhardy had convinced me that YQL wasn’t pure evil
  7. 7. a mere 46 minutes later, I was effected
  8. 8. “I need a new web site”
  9. 9. So, I made plans to build something
  10. 10. Not me, but what I felt like I did about it.
  11. 11. Yahoo pipes relook - Too hard to do what I want quickly.
  12. 12. I really like union, though...
  13. 13. and sort...
  14. 14. Smoke Enter, Smoke
  15. 15. Take my website, see the circled image?
  16. 16. Take my website, see the circled image?
  17. 17. I grab all those photos from flickr using a special tag to choose relevant images
  18. 18. The links? Delicious
  19. 19. The links? Delicious
  20. 20. Projects, from github
  21. 21. Projects, from github
  22. 22. It takes all your sources and auto-magically translates them based on their content-type
  23. 23. Its like a fucking awesome monster for web services... that shits.. ouu.. well. You get the idea
  24. 24. Its like a fucking awesome monster for web services... that shits.. ouu.. well. You get the idea
  25. 25. You can output your sourced data as...
  26. 26. What about those front end guys?
  27. 27. A rack adapter to drop on top of your app, or simply deploy straight to the clouds that exposes smoke sources.
  28. 28. /smoke So, once you’re running, you can hit /smoke
  29. 29. You’ll get a self-documenting api
  30. 30. /smoke/twitter Say you want to know about the twitter source
  31. 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. 32. /smoke/twitter.json
  33. 33. /smoke/twitter.json yaml xml
  34. 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. 35. Presented at webjam10/11 in Sydney & Perth

×