1 / 12

Aperator : Making Tweets Enable Actionable Commands on Third Party Web Applications

Aperator : Making Tweets Enable Actionable Commands on Third Party Web Applications. Peter Zakin , Soumya Sen , Mung Chiang Princeton University WEBAPPS 2012. Social Network Saturation. Small and Large Communities.

cais
Télécharger la présentation

Aperator : Making Tweets Enable Actionable Commands on Third Party Web Applications

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Aperator: Making Tweets Enable Actionable Commands on Third Party Web Applications Peter Zakin, SoumyaSen, Mung Chiang Princeton University WEBAPPS 2012

  2. Social Network Saturation

  3. Small and Large Communities • Most of our time is spent on Facebook and Twitter—not on the smaller networks • Hard to be a good citizen of many different web applications • How can we make it easier to belong to many different networks? • How can we support content-growth on smaller networks? • Flow of information: from small networks to large networks

  4. What is Aperator? • Send actionable commands from Twitter to other web applications. • Currently, aperator supports commands for Delicious, Facebook, Foursquare and Read it Later.

  5. Aperator Syntax • @aperator delicious www.example.com • @aperatorrilwww.example.com • @aperatorfb I’m here at WEBAPPS • @aperator 4sq Fenway Park

  6. Demo!

  7. Architecture

  8. Limitations • Speed • Private accounts are not supported. • Issue could be resolved through REST API • Foursquare and ‘geo’ attribute

  9. Similar Work • Twitter, #fb and #in • ifttt

  10. Takeaway: Aperator Open Lexicon • Aperator could support a developer platform. • Developers reserve syntactical keywords • Delicious, Read it Later etc…. • Purely back-end applications • SMS (Twilio Integration)

  11. Takeaway: Twitter as Social OS • Aperatorpromotes inter-API synergy • Universal interface • Moving beyond #fb and #in with structured commands • Package Installer/Aperator Connect? (probably a TOS violation) • Web Shell?

  12. Final Thoughts

More Related