jdev - 2020-06-14


  1. Neustradamus has joined

  2. xecks has left

  3. Neustradamus has left

  4. Neustradamus has joined

  5. Neustradamus has left

  6. waqas has left

  7. Neustradamus has joined

  8. sonny has left

  9. sonny has joined

  10. Kev has joined

  11. wurstsalat has left

  12. sonny has left

  13. sonny has joined

  14. sonny has left

  15. sonny has joined

  16. sonny has left

  17. sonny has joined

  18. sonny has left

  19. sonny has joined

  20. lovetox has joined

  21. lovetox has left

  22. lovetox has joined

  23. lovetox has left

  24. Neustradamus has left

  25. Holger has left

  26. Neustradamus has joined

  27. paul has joined

  28. Holger has joined

  29. h has joined

  30. goffi has joined

  31. h has left

  32. rion has left

  33. rion has joined

  34. rion has left

  35. lovetox has joined

  36. adiaholic_ has left

  37. adiaholic_ has joined

  38. asterix has joined

  39. lovetox has left

  40. asterix has left

  41. asterix has joined

  42. lovetox has joined

  43. eta has left

  44. eta has joined

  45. debacle has joined

  46. lovetox has left

  47. sonny has left

  48. sonny has joined

  49. debacle has left

  50. debacle has joined

  51. wurstsalat has joined

  52. rion has joined

  53. rion has left

  54. Ge0rG has joined

  55. xecks has joined

  56. adiaholic_ has left

  57. adiaholic_ has joined

  58. adiaholic_ has left

  59. adiaholic_ has joined

  60. alexis has left

  61. alexis has joined

  62. adiaholic_ has left

  63. adiaholic_ has joined

  64. kikuchiyo has joined

  65. kikuchiyo has left

  66. kikuchiyo has joined

  67. kikuchiyo has left

  68. kikuchiyo has joined

  69. kikuchiyo has left

  70. vaulor has joined

  71. kikuchiyo has joined

  72. kikuchiyo has left

  73. kikuchiyo has joined

  74. kikuchiyo has left

  75. kikuchiyo has joined

  76. kikuchiyo has left

  77. kikuchiyo has joined

  78. kikuchiyo has left

  79. kikuchiyo has joined

  80. kikuchiyo has left

  81. kikuchiyo has joined

  82. kikuchiyo has left

  83. pulkomandy has left

  84. pulkomandy has joined

  85. kikuchiyo has joined

  86. kikuchiyo has left

  87. kikuchiyo has joined

  88. kikuchiyo has left

  89. pulkomandy has left

  90. pulkomandy has joined

  91. kikuchiyo has joined

  92. kikuchiyo has left

  93. kikuchiyo has joined

  94. kikuchiyo has left

  95. kikuchiyo has joined

  96. kikuchiyo has left

  97. kikuchiyo has joined

  98. kikuchiyo has left

  99. kikuchiyo has joined

  100. kikuchiyo has left

  101. kikuchiyo has joined

  102. kikuchiyo has left

  103. kikuchiyo has joined

  104. kikuchiyo has left

  105. kikuchiyo has joined

  106. kikuchiyo has left

  107. kikuchiyo has joined

  108. kikuchiyo has left

  109. kikuchiyo has joined

  110. kikuchiyo has left

  111. kikuchiyo has joined

  112. kikuchiyo has left

  113. kikuchiyo has joined

  114. kikuchiyo has left

  115. kikuchiyo has joined

  116. kikuchiyo has left

  117. kikuchiyo has joined

  118. kikuchiyo has left

  119. kikuchiyo has joined

  120. kikuchiyo has left

  121. kikuchiyo has joined

  122. kikuchiyo has left

  123. kikuchiyo has joined

  124. kikuchiyo has left

  125. kikuchiyo has joined

  126. kikuchiyo has left

  127. kikuchiyo has joined

  128. waqas has joined

  129. debacle has left

  130. kikuchiyo has left

  131. lovetox has joined

  132. kikuchiyo has joined

  133. kikuchiyo has left

  134. kikuchiyo has joined

  135. kikuchiyo has left

  136. Yagizа has joined

  137. asterix has left

  138. asterix has joined

  139. asterix has left

  140. asterix has joined

  141. lovetox has left

  142. asterix has left

  143. asterix has joined

  144. kikuchiyo has joined

  145. rion has joined

  146. asterix has left

  147. asterix has joined

  148. asterix has left

  149. asterix has joined

  150. asterix has left

  151. asterix has joined

  152. lovetox has joined

  153. kikuchiyo has left

  154. asterix has left

  155. asterix has joined

  156. kikuchiyo has joined

  157. kikuchiyo has left

  158. adiaholic_ has left

  159. kikuchiyo has joined

  160. kikuchiyo has left

  161. Neustradamus has left

  162. kikuchiyo has joined

  163. kikuchiyo has left

  164. lovetox has left

  165. Neustradamus has joined

  166. kikuchiyo has joined

  167. kikuchiyo has left

  168. lovetox has joined

  169. adiaholic_ has joined

  170. adiaholic_ has left

  171. adiaholic_ has joined

  172. debacle has joined

  173. debacle has left

  174. debacle has joined

  175. Kev has left

  176. debacle has left

  177. kikuchiyo has joined

  178. kikuchiyo has left

  179. Neustradamus has left

  180. lovetox

    can somebody clear up my confusion with 0260

  181. lovetox

    https://xmpp.org/extensions/xep-0260.html

  182. lovetox

    the dstaddr has to be calculated (sid, initiator, responder)

  183. Neustradamus has joined

  184. lovetox

    ok let me rephrase

  185. lovetox

    in 0260, dstaddr is only mentioned regarding proxys

  186. lovetox

    its clear how dst addr is calculated there

  187. lovetox

    but we have to calc dstaddr also for our direct candidates

  188. lovetox

    is it there always (sid, initiator, responder)

  189. lovetox

    even for my offered candidates if im responder?

  190. kikuchiyo has joined

  191. kikuchiyo has left

  192. lovetox

    rion, ^

  193. rion

    Session initiator and responder. Everything else doesn't matter

  194. kikuchiyo has joined

  195. kikuchiyo has left

  196. rion

    For a proxy rules are different yes. There it matters who offers the proxy

  197. Martin has left

  198. lovetox

    yeah k thanks i thought so, but its weirdly not mentioned explicitly, its implied with XEP-0065 only having this one way to calculate it

  199. Martin has joined

  200. rion

    That was also my concern in some xep comments on wiki iiirc

  201. rion

    I even remember doing some PRs to the xep. But not sure if any related to this topic. In any case none was merged

  202. kikuchiyo has joined

  203. lovetox

    rion, do you support multiple file transfer contents per session?

  204. kikuchiyo has left

  205. lovetox

    and what does psi when a user sends multiple files

  206. lovetox

    do you create one session per file, or one session and multiple contents

  207. kikuchiyo has joined

  208. lovetox

    and can you give me a link to the wiki page

  209. lovetox

    https://wiki.xmpp.org/web/Tech_pages/Jingle

  210. lovetox

    i only found this, and there are no comments

  211. kikuchiyo has left

  212. rion

    > rion, do you support multiple file transfer contents per session? One session for in and out

  213. rion

    Unfortunately I haven't written any docs yet. I remind myself everytime to do this but still can find some spare time for this

  214. kikuchiyo has joined

  215. asterix has left

  216. asterix has joined

  217. Yagizа has left

  218. asterix has left

  219. asterix has joined

  220. kikuchiyo has left

  221. rion

    In short Psi has 1) manager for every application type and every transport type (global instances. e.g. S5Bmanager) 2) specific classes to make instances for every application type and every transport type (e.g. S5BTransport) 3) sessioned managers - a single instances of managers per session. From one side this thing has session and global manager from another side multiple instances of applications of transports. I call these things pads (kind of a place we where application can access global manager. e.g. S5BSessionManagerPad) s5b stuff is not quite standard but I hope it's compatible. It has optimizations wrt trickle candidates. And Psi heavily uses them. Basically it never waits to send session or session answer. If something can be discovered and sent later it will be discovered and sent later. Besides it has priority optimizations. Like if it's possible some higher priority candidate can be discovered later, it will wait before sending candidate-error/use.

  222. rion

    Most clients have simpler implementation. And the XEP doesn't explicitly say what's the preferred way to implement it.

  223. rion

    anyway I look forward to implement webrtc datachannels. I believe it's the future which will eventually deprecate s5b

  224. debacle has joined

  225. debacle has left

  226. debacle has joined

  227. lovetox

    hm how would you trickle candidates? and why? in what circumstance would a higher priority candidate discovered later?

  228. lovetox

    higest priority candidates is your own ip

  229. lovetox

    i guess you always know your own ip way before any jingle session

  230. lovetox

    my opinion about jingle is, its very generic, that does not mean one has to implement every possible option that one could imagine

  231. kikuchiyo has joined

  232. lovetox

    i say almost all circumstances, you give your own ip, and a proxy, if for what ever reason own ip does not work

  233. lovetox

    and thats about it, also 10 years of jingle FT told us there is no probably no client out there who implements more than, send one content with candidates, and thats about it

  234. lovetox

    and really FT should not need more than that

  235. lovetox

    also because probably nobody implements all what the spec could do theoretically, i think there are many wholes in the spec that just resulted from no implementation feedback

  236. lovetox

    probably because jingle allows many theoretically things, where no real use case is there for right now

  237. rion

    > i guess you always know your own ip way before any jingle session Think about upnp. If for some reason it's discovered later.

  238. moparisthebest has left

  239. rion

    > that does not mean one has to implement every possible option That's the real problem. Because everyone has in mind their own way. and it's usually it's incompatible with ways of others

  240. rion

    Just because of this I don't like jingle.

  241. flow has left

  242. rion

    I would better implemented sip

  243. moparisthebest has joined

  244. goffi has left

  245. rion

    I recently implemented new ICE (RFC 8445) and I have to say it's way more clear than for example XEP-0166. Even so XEP-0166 has way more circumstances described. In other words less freedom - simpler/more reliable/more compatible implementation

  246. rion

    I recently implemented new ICE (RFC 8445) and I have to say it's way more clear than for example XEP-0166. Even so RFC 8445 has way more circumstances described. In other words less freedom - simpler/more reliable/more compatible implementation

  247. rion

    waqas: how alive Adium nowadays? I was gooing to remove it from Psi's clients detector.

  248. adiaholic_ has left

  249. adiaholic_ has joined

  250. drops has left

  251. drops has joined

  252. asterix has left

  253. asterix has joined

  254. kikuchiyo has left

  255. lovetox has left

  256. asterix has left

  257. kikuchiyo has joined

  258. waqas

    rion: Not very, AFAIK. There were some commits 7 months ago, but before that was 2017. I haven't found another client I felt like switching to yet.

  259. adiaholic_ has left

  260. waqas has left

  261. rion

    waqas: pidgin?

  262. waqas has joined

  263. wurstsalat has left

  264. wurstsalat has joined

  265. kikuchiyo has left

  266. sonny has left

  267. sonny has joined

  268. debacle has left

  269. vaulor has left