Discussing how to enable an application to participate in a federated social web

1. OStatus-enabling your Application

2. What is OStatus?

3. Modeling distributed social networks

4. Broadcaster-receiver

5. Aggregation

7. Especially good when not explicitly “social”

8. Wikis

9. Blogs

10. CMS

11. Bug tracking

12. Photo-sharing

14. Response handler

15. Receiver

16. I. Make good feeds.

17. ActivityStreams

18. http://activitystrea.ms/

20. Atom feeds

21. Single feed per person

22. Author element at the feed level

26. object

28. Important elements include <preferredUsername>, <displayName>, <note>, and <urls>.

29. II. PuSH-enable your feeds

31. http://code.google.com/p/pubsubhubbub/

32. Add a 'hub' link

33. Send new-content update

34. Congratulations!

37. Tumblr

38. WordPress.com

39. Gowalla

40. III. WebFinger identities

41. http://code.google.com/p/webfinger/

42. [email_address]

43. Update schema

44. Congratulations!

46. IV. Model remote users

48. “favorites”

49. Social graph

51. Subclasses User and RemoteAuthor

53. Numerical ID may be locally but not globally unique

55. Very weak user role

56. absolute minimum permissions

57. No login, if possible!

58. V. Accept Salmon for replies

59. http://www.salmon-protocol.org/

61. Replies

62. Plain Atom entries

64. notify the user

67. Different languages

68. Different libraries

69. VI. Accept Salmon for social activities

70. Atom + ActivityStreams

72. Unfollow

74. Share

77. have a two-way conversation

78. VII. Allow subscriptions to remote users

79. PuSH subscriber role

81. By profile URL

82. By WebFinger ID and “updates-from”

83. By Atom/RSS feed URL

85. Redirect to own server

86. VIII. Send Salmon slaps

88. Provide an RSA key in WebFinger

89. Sign the slap!

90. IX. Send Salmon slaps for social activities

92. Fave/Like

93. Share

94. Profile update

95. What next?

97. Activity Streams JSON encoding

98. Better on-site UI

99. Conversation tracking

101. http://federatedsocialweb.net/

102. [email_address]