We need to talk about Twitter presentation from Social Developers London

1. Angus Fox
Social Developers London
@nuxnix
This talk draws on information
from dev.twitter.com but is in
no way endorsed byTwitter
Corporation  #justsaying

2. The first place to start is at dev.twitter.com
SSL
Streaming
Certs
API 1.0 retired
Embedded
Tweet
Permalinks
>32bit user
ID’s

3.  November 4, 2013
 SSL certificates - root certificate will change to
VerisignG3
▪ userstream.twitter.com
▪ stream.twitter.com
 The stream.twitter.com certificate is already
signed against theVerisign G3 root, so clients
currently connecting to this domain already
have the appropriate root certificates installed
 More Info
 https://dev.twitter.com/docs/security/using-ssl

4.  Use two test accounts with large Ids:
 @64Flavors (ID: 4503597479886593) and
 @Overflow64 (ID: 4503599627370241).
 They’ve been set up toTweet every 10 minutes,
generating experimental data for both the REST
and Streaming APIs

5. Headlines tell the
story behind theTweet
New feature for publishers
using EmbeddedTweets that
connects articles about the
Tweet with theTweet itself.
Related Headlines 

6.  If you still have not updated your app and you
want people to be able to continue using it,
it’s not too late!
 https://dev.twitter.com/docs/api/1.1/overview

7. IPO announcement repercussions
Continuing
‘wider’ issues
IPO confirms
Twitters
intent
Narrow use
cases
Potential
issues for
developers
Old school
and new
school
Alternatives App.net Diaspora*

8.  Privacy
 users can broadcast sensitive personal information to anyone who
views their public feed.
 privacy options can sometimes compromise personal information.
 On centralized services, where all of the information flows through
one point user information has sometimes been exposed to
governments and courts without the prior consent of the user
 usually through subpoenas or court orders.
▪ http://en.wikipedia.org/wiki/Wikileaks_related_Twitter_subpoenas
 Security
 there is potential for sensitive information to be publicized
 includes information which may be subject to a superinjunction
 Integration
 Corporate and government culture needs to change to recognise the
change already in place in interpersonal culture

10.  Consumption of
information about
people or brands
which post updates
onTwitter
 Interacting with
brands as a kind of
support network
 A brand and celebrity
ghetto
 The odd spark of live
events

12.  No open development partner program
 No Transparency on the monetization strategy for twitter
 Twitter cannot be assumed to be benevolent, has adopted an
embrace, extend and extinguish strategy towards third parties
 Expect charges and fees
 Expect less user data privacy
 No Service Level Agreement for uptime, feeds
 No community code of conduct
 No community governance process to twitter API
 No community process to innovations in twitter
technogies
 No Independent adjudication for twitter id disputes

13. OLD SCHOOL
 Instant messaging
 IRC
 Email?
 Text messages? / iMessage
/ BBM
 Google
 Facebook
 Linked-In
NEW SCHOOL
 APP.NET
 Diaspora
 Status.net
 Tent.io
 Enterprise social software
 Connections
 Jive
 SharePoint

14. Your Passport to Great Applications

16.  App.net makes building social apps easier
 Out of the box social platform and API
 A framework of built-in functionality
▪ user profiles
▪ following/follower
▪ public and private messaging
▪ content streams
▪ sharing for video, audio, and images
▪ Geolocation
 App Directory
 One App.net ID, sustainable platform without
advertising

17. Decentralisation, Freedom, Privacy

19.  Use diaspora* as your home base to post to
your profiles on other major social services.
This way your friends will still be able to keep
in touch with what you’re up to, even if
they’re not yet on diaspora*. diaspora*
currently supports cross-posting to your
Facebook,Twitter, andTumblr accounts, with
more to come.

21.  Activity stream
 (Brand/Fan) Pages
 Like button
 Hashtag
 Groups
 Reblogging
 Polling
 Internet petitions

22.  Before the sponsored updates.
 Before the terms of service changed.
 Before data stopped being private.
 Before we sold our memories.
 Before we forgot our rights.
 Before everything that made media
 Less social and more cynical,
 There was one simple idea:
 Our lives are our own.
 What we share and who we share it with,
 Our memories, our secrets,
 Our lives are our own.
 That idea is important
 So we’re going back to before.
 And in going back to before,
 We’re going forward.
 Tent.Going back to forward.

23.  Tent is a protocol that puts users back in control.
 Users should control the data they create, choose who can access
it, and change service providers without losing their social graph.
 Tent is a protocol, not a platform. Like email, anyone can build
Tent apps or hostTent servers, allTent servers can talk to each
other, and there is no central authority to restrict users or
developers.
 Tent helps you keep all your data in one place that you control.You
can choose a hosting provider or run your own server. If you want
to move hosts later your data and relationships come with you.
 WithTent you can put data back in the hands of your users, leaving
you to focus on what you're best at: designing and building
applications.There is no central authority to cut off API access.You
deal only with your users, directly.

24. Users Type Lifecycle Opinion
Twitter 200,000,000
(Feb 13)
Apache License,
Version 2.0
Pre IPO Brand and
Celebrity
Ghetto
App.net 100,000 (March
13)
Private Service Stable Developer
ghetto
Diaspora* 405,000 (Sept 13) AGPLv3, MIT Stable Unknown
GNU Social
(status.net)
Unknown GNU Affero Stable In decline
Tent.io Unknown BSD Preview New
Adjusted in part from :
http://en.wikipedia.org/wiki/Comparison_of_software_and_protocols_for_distribute
d_social_networking

25. Presentations are available from Slideshare
Slides
http://www.slideshare.net/nuxnix