WebRTC-enabled Twitter                  Aswath Rao     http://www.enthinnai.com
SummaryProposal to add RTC feature to TwitterDetailed description of featuresDemands minimal infrastructure resourcesB...
Real Time Communication within TwitterOther social networks have added RTC capabilities  Facebook Messenger  Google Cha...
Individual Users Main use case   RTC Escalation from DM Permission-based like DM   If User A can DM User B, then A mus...
Business UsersMain use case  Customer Service Interaction with RTCMore flexible permission rulesThey may allow  Follo...
Presence InformationBrowser clients report keyboard status as Presence informationPresence information is displayed upon...
Session initiationProfile summary will display  The user’s status (assuming permitted)  A link to initiate a WebRTC ses...
Impact on Infrastructure Additional infrastructure resources are kept to  a minimum Redefined presence information handl...
Upcoming SlideShare
Loading in …5
×

WebRTC-enabled Twitter

694 views
627 views

Published on

0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
694
On SlideShare
0
From Embeds
0
Number of Embeds
109
Actions
Shares
0
Downloads
8
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

WebRTC-enabled Twitter

  1. 1. WebRTC-enabled Twitter Aswath Rao http://www.enthinnai.com
  2. 2. SummaryProposal to add RTC feature to TwitterDetailed description of featuresDemands minimal infrastructure resourcesBased on the design ideas used in EnThinnai
  3. 3. Real Time Communication within TwitterOther social networks have added RTC capabilities Facebook Messenger Google Chat/Talk/Hangout Has become a “table stake”Individuals would prefer to upgrade DMBusinesses would like to upgrade customer service interactionWebRTC facilitates introduction of RTC
  4. 4. Individual Users Main use case RTC Escalation from DM Permission-based like DM If User A can DM User B, then A must be able to initiate an RTC session User B will be able to accept different modalities Text chat alone Text and voice chat Text and video chat Permission settings and modalities will be determined by time and context
  5. 5. Business UsersMain use case Customer Service Interaction with RTCMore flexible permission rulesThey may allow Followers Followers and Following Any Twitter user Any
  6. 6. Presence InformationBrowser clients report keyboard status as Presence informationPresence information is displayed upon explicit request Eliminates the complexity in distributing Presence information to thousands of following (by individual users) and millions of followers (for business users)
  7. 7. Session initiationProfile summary will display The user’s status (assuming permitted) A link to initiate a WebRTC session (assuming permitted and online)A new request for session initiation will be notified in the same manner new tweet notification is delivered today
  8. 8. Impact on Infrastructure Additional infrastructure resources are kept to a minimum Redefined presence information handling does not introduce any load User’s reporting change in the status Presence is notified only on request Session management signaling is Only during a session Uses already designed link – New tweet notification link

×