• Like
  • Save
How To Reinterpret The Web In 180 Seconds
Upcoming SlideShare
Loading in...5
×
 

How To Reinterpret The Web In 180 Seconds

on

  • 2,509 views

My presentation from webjam10/11

My presentation from webjam10/11

Statistics

Views

Total Views
2,509
Views on SlideShare
2,492
Embed Views
17

Actions

Likes
5
Downloads
12
Comments
0

1 Embed 17

http://www.slideshare.net 17

Accessibility

Upload Details

Uploaded via as Adobe PDF

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

    How To Reinterpret The Web In 180 Seconds How To Reinterpret The Web In 180 Seconds Presentation Transcript

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