XSF Discussion - 2014-02-11

  1. Maranda has left
  2. stpeter has joined
  3. Lance has left
  4. Zash has left
  5. Maranda has joined
  6. waqas has left
  7. waqas has joined
  8. Lance has joined
  9. Maranda has left
  10. Lance has left
  11. Tobias has left
  12. bear has left
  13. stpeter has left
  14. Kev has left
  15. Kev has joined
  16. waqas has left
  17. emcho has left
  18. Alex has joined
  19. Simon has joined
  20. Simon has left
  21. emcho has joined
  22. emcho has left
  23. jabberjocke has joined
  24. simon has joined
  25. jabberjocke has left
  26. ralphm https://twitter.com/g0rdin/statuses/432999314257084417
  27. SouL has left
  28. ralphm For those with some German skills. For those without, the executive summary is: "Carbons >>> Hangouts, Stream Management is awesome. Yeah. The future. Yeah."
  29. simon he's a happy camper. Now we just need to get some mobile clients sorted.
  30. Lloyd has joined
  31. ralphm I really like watching http://display.ik.nu/xmpp.
  32. Tobias you and your self-signed certs ;)
  33. ralphm :-D
  34. ralphm Better than nothing, I suppose?
  35. Tobias probably
  36. Tobias it says via Twitter, are there other source that go into it?
  37. ralphm Not for this feed, no. But ikDisplay can have multiple different sources. It was originally created as a back channel for the federated semantic-web-like social networking sites I worked on at Mediamatic.
  38. ralphm Including ActivityStreams.
  39. ralphm https://github.com/ralphm/ikdisplay
  40. SouL has joined
  41. ralphm Tobias: do you have any use cases?
  42. Tobias ralphm, just wondered about the sources...but i suppose not many networks have sources for public streams anyway
  43. ralphm Yay silos.
  44. Tobias has left
  45. Zash has joined
  46. emcho has joined
  47. emcho has left
  48. emcho has joined
  49. Ash has joined
  50. Ash has left
  51. ralphm Tobias: That said, it probably should have support for Superfeedr. However, its XMPP PubSub API has some non-standard warts.
  52. Tobias has joined
  53. Ash has left
  54. winfried has joined
  55. jabberjocke has joined
  56. emcho has left
  57. SouL has left
  58. SouL has joined
  59. emcho has joined
  60. Ash has joined
  61. Ash has left
  62. emcho has left
  63. emcho has joined
  64. Ash has joined
  65. emcho has left
  66. emcho has joined
  67. emcho has left
  68. emcho has joined
  69. Alex has left
  70. emcho has left
  71. emcho has joined
  72. SouL has left
  73. xnyhps has left
  74. xnyhps has left
  75. xnyhps has joined
  76. Ash has left
  77. Ash has joined
  78. Ash has left
  79. Ash has joined
  80. Ash has left
  81. waqas has joined
  82. emcho has left
  83. emcho has joined
  84. Zash has left
  85. waqas has left
  86. winfried has left
  87. Zash has joined
  88. winfried has joined
  89. waqas has joined
  90. SouL has joined
  91. Zash has left
  92. stpeter has joined
  93. Ash has joined
  94. Ash has left
  95. Ash has joined
  96. dwd xnyhps, To be fair, if you send more than 2^96 stanzas, you've a better than even chance of hitting a collision.
  97. winfried has left
  98. xnyhps You want to send the entire internet how many times? ;)
  99. dwd xnyhps, Although I imagine we could mitigate that by recommending people restart their XMLStream at least once before the heat death of the universe.
  100. Lloyd :)
  101. jabberjocke anybody have a good federated xmpp domain for groupies to the philips hue bands we are startig around the world
  102. jabberjocke the anni-frid@jabber.se <mailto:anni-frid@jabber.se>,bjorn@jabber.se <mailto:bjorn@jabber.se>, benny@jabber.se <mailto:benny@jabber.se> agneta@jabber.se <mailto:agneta@jabber.se> from abba@jabber.se <mailto:abba@jabber.se> is soon online
  103. Tobias disco will get a completely new meaning in the XMPP world (:
  104. jabberjocke YEEES :)
  105. ralphm jabberjocke: looking awesome #hue
  106. Ash has joined
  107. Ash has left
  108. dwd xnyhps, Oh, he's right.
  109. dwd xnyhps, I think you hit parity on the probability of hitting a 10 hex-char (ie, 48-bit) hash fragment after only 4.5 million years on a stanza per second.
  110. xnyhps I meant outputting the first 10 bytes of the hash, not the first 10 bytes of the hex representation of the hash, so 80 bit.
  111. Lloyd has left
  112. xnyhps (Also, 10 hex-char is 40 bit, isn't it?)
  113. dwd Ah, yes.
  114. Kev It is worth noting, potentially, that while they're a generally bad idea, 0-based integer counters do have bandwidth going for them :)
  115. Tobias yeah...think of all the savings....when outputting tons of bloated XML
  116. Tobias ^^
  117. dwd Oh, don't start.
  118. Tobias ;)
  119. xnyhps Use compression, and pick random parts from the stream so far to use as ids.
  120. dwd That actually works.
  121. Kev Absolutely.
  122. Kev Use an RNG to select bits of a stream to avoid needing to use an RNG.
  123. dwd Kev, No, this is for saving bandwidth.
  124. xnyhps Just hope you don't actually pick the content of a message. :P
  125. Kev dwd: It can't possibly save bandwidth.
  126. Kev However many bytes of entropy you want to have are going to take that many bytes to transmit.
  127. Kev (At least that many bytes to transmit, you could transmit lots with little entropy, I realise)
  128. dwd Kev, No, not at all. If you select carefully, you can generate random identifiers that are always encoded by zlib as a reference, hence three octets or so.
  129. Kev And by doing so, you're reducing the entropy.
  130. Kev You're talking about selecting your randomness very carefully so that it's not too random :)
  131. dwd Smallish number of bits.
  132. Zash has joined
  133. dwd But it's OK, because you could send the *real* random data earlier in the stream to refer back to.
  134. Kev This is close enough to the edge of my knowledge that I accept I could be wrong in this. But this sounds like Not A Good Idea.
  135. xnyhps I was entirely not serious.
  136. dwd xnyhps, Nor me. But I'm wondering how far I can string Kev along. :-)
  137. Kev xnyhps: You, I believe. Dave I have less faith in...
  138. dwd Kev, You didn't like the suggestion that you'd put arbitrary random data in the stream, then refer back to it, so you get both the compression *and* the randomness?
  139. dwd I was proud of that one.
  140. Kev That bit I assumed was a joke. The rest I was less convinced about.
  141. fsteinel has joined
  142. Maranda has joined
  143. stpeter thinks of the acronym DFTT
  144. xnyhps Sorry Peter.
  145. SouL has left
  146. SouL has joined
  147. Ash has joined
  148. stpeter xnyhps: I haven't seen anything useful from this person, but I admit that I have started to tune him out (not quite killfile, but close)
  149. xnyhps Me neither
  150. Kev You're talking about me, right? :p
  151. stpeter ;-)
  152. Zash Who are you?
  153. ralphm has left
  154. ralphm has left
  155. ralphm has left
  156. ralphm has left
  157. Maranda has left
  158. ralphm has left
  159. Maranda has joined
  160. jabberjocke has left
  161. bear has joined
  162. Tobias has joined
  163. Zash has joined
  164. emcho has left
  165. emcho has joined
  166. emcho has left
  167. fsteinel has left
  168. emcho has joined
  169. emcho has left
  170. Tobias has left
  171. Tobias has joined
  172. SouL has left
  173. bear has left
  174. Kev has left
  175. Kev has joined
  176. emcho has joined
  177. emcho has left
  178. emcho has joined
  179. Simon has joined
  180. jabberjocke created a fosdem post draft at xmpp.org <http://xmpp.org> please review and add a good foto
  181. Kev Right, I think that's comments for the people who asked for them on GSoC ideas given.
  182. intosi has left
  183. intosi has joined
  184. ralphm has left
  185. stpeter has left
  186. Simon has left
  187. Zash has joined
  188. ralphm has left
  189. Simon has joined
  190. Simon has left
  191. Maranda has left
  192. winfried has joined
  193. emcho has left
  194. emcho has joined
  195. Tobias has left
  196. Tobias has joined
  197. Zash has left
  198. winfried has left