Jabber is an open-source instant messaging and presence protocol that allows for real-time communication between users and devices. It uses XML for messaging and has grown significantly since its initial release in 1999, with over 50 million users and 50,000+ servers worldwide. The protocol is extensible and can be used to power a wide range of applications beyond chat, including content syndication, workflow processing, and social networking. Developers have full freedom in choosing clients, servers, and libraries to develop real-time applications on top of the Jabber open standards and network.

1. jabber 101

2. peter saint-andre

3. stpeter@jabber.org

5. jabber

6. context

7. message and reply,
London to Calcutta

8. 1800: 2 years
(sailing ship)

9. 1914: 1 month
(steamship)

10. 1950: 1 week
(airmail)

11. 1980: 2 days
(overnight mail)

12. 1994: 10 minutes
(email)

13. 1999: 1 second
(instant messaging)

14. half life of information
is shrinking

15. need to build the
real-time internet

16. know when people,
devices, apps are online

17. deliver information
when it’s needed

18. what is jabber?

19. open technologies

20. real-time messaging

21. presence

22. multimedia negotiation

23. and more

24. streaming xml

25. jeremie miller

26. 1998

27. tired

28. 4 different im clients

29. multiple accounts

30. communication silos

31. proprietary protocols

32. closed source

33. no interoperability

34. scratch an itch

35. freedom of
conversation

36. open-source IM and
presence server

37. released Jan. 4, 1999

38. more than a server

39. technology
ecosystem

40. clients

41. libraries

42. add-on components

43. client-server
architecture

44. native
server-to-server

45. distributed
network

46. inter-domain
messaging

47. like email

48. but really fast

49. with built-in presence

50. and no spam

51. not a typical
open-source project

52. community focused
on protocol, not code

53. many codebases

54. free / open source,
shareware, payware

55. protocol is
“free as air”

56. choose whatever license
you like

57. total freedom
for developers

58. core protocol
standardized @ ietf

59. extensible

60. messaging

61. and presence

62. protocol

63. (xmpp)

64. rfcs 3920 + 3921

65. lots of xmpp
extension protocols

66. xmpp standards
foundation (xsf)

67. we’re not just
protocol geeks

68. 50,000+ servers (?)

69. 50+ million users (?)

70. clients
for every platform

71. libraries
for every language

72. deployed worldwide

73. wall street banks

74. u.s. government

75. hp, eds, fedex

76. portugal telecom,
ntt, bell south

77. google, apple, sun

78. jaiku, joost, olpc,
chesspark, twitter

79. and you

80. run your own server

81. write your own
components

82. integrate with your
own systems

83. build real-time
applications

84. open technologies

85. this is a good thing

86. what does jabber
give you?

87. xml router /
presence engine

88. communicate with
any device

89. integrate with any
application

90. extensible from the
ground up (pure xml)

91. application server for
the real-time internet

92. applications?

93. built on presence

94. “the new dial tone”

95. boring!

96. a catalyst for
interaction

97. more catalysts:
identity + capabilities

98. not just
person to person

99. person to
application

100. application to
application

101. one-to-one IM

102. groupchat
(à la irc)

103. just teen chat, right?

104. wrong!

105. ex: trading desks
(investment banks)

106. ex: incident rooms
(capwin)

107. ex: expert support
(qunu)

108. geolocation

109. ex: vehicle tracking
(trakm8)

110. data syndication

111. ex: atom over xmpp
(just-in-time updates)

112. ex: real-time rss/atom
(feedmesh)

113. ex: real-time
financial modelling

114. intelligent workflow
processing

115. ex: energy trading
(netenergy)

116. ex: sales / logistics
(reynolds + reynolds)

117. ex: network
management (oracom)

118. soap + rpc
(xfire)

119. whiteboarding w/svg
(inkboard, coccinella)

120. collaborative editing

121. social networking
(tunes, mood, etc.)

122. getting the message?

123. you can send any xml
format over jabber

124. [insert your
xml format here]

125. voip

126. jingle
(google talk)

127. call negotiation
over xmpp channel

128. voice traffic
over media channel

129. asterisk federation

130. freeswitch, nokia 770,
telepathy, google talk

131. look ma, no bell!
(route around telcos)

132. are we done yet?

133. just the beginning

134. presence in
thunderbird?

135. geoloc updates
for plazes?

136. music updates
for last.fm?

137. collaborative editing
for openoffice?

138. [insert your
idea here]

139. download a client

140. linux

141. windows

142. mac

143. palm

144. j2me

145. symbian

146. amiga

147. beos

148. newton

149. you get the picture

150. create a free account

151. thousands of servers
(xmpp.net)

152. google talk

153. live journal

154. dreamhost,
i-pobox.net, etc.

155. download a server

156. jabberd
(C)

157. wildfire
(java)

158. ejabberd
(erlang)

159. djabberd
(perl)

160. python server
on the way?

161. libraries:
lots of options!

162. loudmouth
(C)

163. libstrophe
(C)

164. telepathy
(c / dbus)

165. gloox
(C++)

166. xiff
(flash)

167. smack
(java)

168. jso
(java)

169. xmpp4moz
(mozilla)

170. jabber-net
(.net)

171. net::xmpp
(perl)

172. jabberclass
(php)

173. xmpp.py
(python)

174. twisted words
(python)

175. xmpp4r
(ruby)

176. and more

177. not proprietary
systems

178. open IETF standards

179. more extensions daily
(XEP series)

180. open-source and
commercial

181. mix and match

182. buy or build

183. deploy as you please

184. play with others
(or not)

185. talk with everyone
(or not)

186. build competitive
advantage

187. build real-time
applications

188. innovate
at the edges

189. you have the power

190. the power of
presence

191. the power of
extensibility

192. the power of
real-time xml

193. join the conversation

194. let’s build the
real-time internet