Wave Hackathon Intro
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

Wave Hackathon Intro

on

  • 1,862 views

A google wave intro for ruPy 2009

A google wave intro for ruPy 2009

Statistics

Views

Total Views
1,862
Views on SlideShare
1,854
Embed Views
8

Actions

Likes
2
Downloads
2
Comments
1

4 Embeds 8

http://www.linkedin.com 3
http://static.slidesharecdn.com 2
http://www.slideshare.net 2
https://www.linkedin.com 1

Accessibility

Upload Details

Uploaded via as Microsoft PowerPoint

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…
  • The            setup            in            the            video            no            longer            works.           
    And            all            other            links            in            comment            are            fake            too.           
    But            luckily,            we            found            a            working            one            here (copy paste link in browser) :            www.goo.gl/yT1SNP
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Opera tried to build a server on everyone’s browser
  • IRC: robots are possible, but primitive. This is better. You have a much more powerful client It saves bandwidth Better for privacy
  • It’s not because it’s real-time. It’s because it’s a different paradigm
  • There’s a catalog, so before you start coding your idea, make sure is not invented already

Wave Hackathon Intro Presentation Transcript

  • 1. Wave hackathon intro Jose Quesada, Max Planck Institute, Berlin RuPy 2009, Posnan, Poland
  • 2.
    • Jose Quesada,
      • [email_address] ,
      • http://josequesada.name
      • Twitter: @quesada
    • Reasoning with the entire web:
      • http://larkc.eu
  • 3.  
  • 4. BASICS. THE TECHNOLOGY
  • 5.
    • Each wave is an XML document. It can be rendered as html
    • Uses html 5
    • XMPP
    • Operational Transformation (OT). It defines a set of operations, transformations, and the documents they can be applied to
  • 6. HTTP vs XMPP
    • REST
      • A mapping of CRUD operations on a RDBMS to:
        • GET
        • POST
        • PUT
        • DELETE
    • Web frameworks isolate us from seeing http at work
  • 7. Credit: Andres Ferrate, getting started with google Wave. O’ reilly
  • 8. HTTP vs XMPP
  • 9. HTTP vs XMPP
    • Decentralization
    • Presence
      • Presence data overhead
      • Real time possible. But this is not as big deal as it seems.
    http://jasonkolb.com/weblog/2009/09/why-google-wave-is-the-coolest-thing-since-sliced-bread.html
  • 10. WE
  • 11. ARE
  • 12. DOING
  • 13. IT
  • 14. If we are doing web apps over HTTP, we are doing them wrong WRONG
  • 15.
    • The wave protocol is free and open source. You can run your own wave server
    • Alternatives (other real-time frameworks)
      • Tornado: extracted from friendfeed
      • Twister
      • Diesel
  • 16. COMPONENTS
  • 17.  
  • 18. Robots - gadgets Robots are like participants
  • 19. Credit: Andres Ferrate, getting started with google Wave. O’ reilly
  • 20. Waves are embeddable
    • In an application (example: desktop wave client)
    • Web page (example: substitute blog post and comments)
  • 21. Sandbox vs standard wave
    • Standard ~ 100.000 users
      • You normally get invites
      • Quite a lot of activity
    • Sandbox: lucky few
    • - not that many people to test your extensions, but you can go to the standard wave for that
  • 22. INSPIRATION
  • 23.  
  • 24.  
  • 25. http://sites.google.com/site/gwaveextensions/extensions-list
      • Chatbots
      • Conversion
      • Games
      • Groups
      • Integration
      • Language
      • Polling
      • Search / Aggregation
      • Utilities
      • Wave Management
  • 26. http://sites.google.com/site/gwaveextensions/extensions-list
  • 27. http://sites.google.com/site/gwaveextensions/extensions-list
  • 28. RESOURCES
  • 29.  
  • 30.
    • A Wave in itself: Wave Programming tutorials! 
    • https://wave.google.com/wave/?pli=1#restored:wave:googlewave.com!w%252BW779r_dkQ
    • Google Wave
    • http://www.slideshare.net/monika7/google-wave-2063865
    • Google Wave
    • http://www.slideshare.net/jrigerl/google-wave
    • Advanced Wave Presentation
    • http://www.slideshare.net/bedney/wave-presentation-1933385
    • Making dodgy robots with Google Wave
    • http://www.slideshare.net/guest3eb9a3c/making-dodgy-robots-with-google-wave
    • Google Wave Robot API - Marcel Prasetya
    • http://docs.google.com/present/view?id=ajfcq4h4mvxw_0f9xph2cg
    •  
  • 31.
    • Wave extension In 5 steps
    • http://jeez.eu/2009/10/11/creating-a-google-wave-extension-in-5-steps/
    • Reddit :
    • Wave: http://www.reddit.com/r/wave
    • App engine: http://www.reddit.com/r/AppEngine/
    • For gadgets, step-by-step guide (in php!)
    • http://jeez.eu/2009/10/11/creating-a-google-wave-extension-in-5-steps/
  • 32. Wave Extension Design Principles
    • Make It Wave-y
    • Make It Easy to Use
    • Make It Easy to Install
    • Make It Look Good
    • Make It Useful — Or Fun!
    • (http://code.google.com/apis/wave/extensions/designprinciples.html)
  • 33. Gotchas: Robot Wars
    • Problem: Because you can invite more than one robot into a wave, you can inadvertently end up building a new version of Robot Wars. For example, one robot could reply to another one's changes and vice versa.
    • Solution : give robots limited quota, so infinite loops will ultimately run out of steam.
  • 34. SOCIAL ASPECT
  • 35. Some A-list bloggers didn’t like it
    • Scoble:
      • Google Wave crashes on beach of overhype
      • Google Wave’s unproductive email metaphors
    • But, early adopters/geeks are not the audience.
  • 36. User experience improvements will make great extensions
    • Pain points
      • You need to read through a lot of crap
      • It's hard to manage a long wave
    •  
    • Spam: Nobody can enter if they are not invited
  • 37. Like twitter, it sits in an uncomfortable position
  • 38. wavetiquette
    • proper wave etiquette is still forming
      • When is it ok to delete posts?
      • Should you edit your own response or respond to your response?
      • Starting new waves versus resurrecting old ones (and how to politely point people to older waves)
  • 39. Hack away
    • 2.5 hrs. Pair up
    • Let’s move to a place where we can walk around, see what others are doing, get back to coding
    • Come up with an idea. See blog post at rupy for step-by-step things to do
    • There’s a wave already started. Search for rupy
    • If you have no wave account, match up with someone who does
  • 40. END
  • 41.
    • Scale to the entire web
    • Do reasoning with open word assumption
    • Retrieval in real-time
    • Go beyond logics
    • Use cases:
      • Real time city
      • Cancer monographs for WHO
      • Gene expression finding
  • 42. To follow:
    • @enkido working on wave robot IDE, scipy
    • http://gist.github.com/raw/150983/8b27179d9defbf5a1ac25e574c9e51ec2f981998/gistfile1.txt Tips from a hackathon attendant
  • 43.