XSF logo jdev - 2020-01-17


  1. bhaveshsgupta has left
  2. bhaveshsgupta has joined
  3. bhaveshsgupta has left
  4. bhaveshsgupta has joined
  5. bhaveshsgupta has left
  6. bhaveshsgupta has joined
  7. debacle has left
  8. bhaveshsgupta has left
  9. bhaveshsgupta has joined
  10. bhaveshsgupta has left
  11. bhaveshsgupta has joined
  12. sonny has left
  13. bhaveshsgupta has left
  14. bhaveshsgupta has joined
  15. serge90 has left
  16. serge90 has joined
  17. paul has left
  18. sonny has joined
  19. bhaveshsgupta has left
  20. bhaveshsgupta has joined
  21. bhaveshsgupta has left
  22. bhaveshsgupta has joined
  23. bhaveshsgupta has left
  24. bhaveshsgupta has joined
  25. bhaveshsgupta has left
  26. bhaveshsgupta has joined
  27. bhaveshsgupta has left
  28. bhaveshsgupta has joined
  29. sonny has left
  30. bhaveshsgupta has left
  31. bhaveshsgupta has joined
  32. sonny has joined
  33. bhaveshsgupta has left
  34. bhaveshsgupta has joined
  35. arashi has left
  36. asterix has joined
  37. asterix has left
  38. asterix has joined
  39. sonny has left
  40. asterix has left
  41. asterix has joined
  42. asterix has left
  43. asterix has joined
  44. moparisthebest has left
  45. moparisthebest has joined
  46. wurstsalat has joined
  47. asterix has left
  48. asterix has joined
  49. lovetox has joined
  50. bhaveshsgupta has left
  51. bhaveshsgupta has joined
  52. bhaveshsgupta has left
  53. paul has joined
  54. bhaveshsgupta has joined
  55. pulkomandy has left
  56. pulkomandy has joined
  57. bhaveshsgupta has left
  58. larma has left
  59. bhaveshsgupta has joined
  60. larma has joined
  61. bhaveshsgupta has left
  62. bhaveshsgupta has joined
  63. moparisthebest has left
  64. moparisthebest has joined
  65. strar has left
  66. strar has joined
  67. goffi has joined
  68. pulkomandy has left
  69. pulkomandy has joined
  70. bhaveshsgupta has left
  71. bhaveshsgupta has joined
  72. sonny has joined
  73. bhaveshsgupta has left
  74. bhaveshsgupta has joined
  75. bhaveshsgupta has left
  76. bhaveshsgupta has joined
  77. sonny has left
  78. sonny has joined
  79. bhaveshsgupta has left
  80. bhaveshsgupta has joined
  81. arashi has joined
  82. bhaveshsgupta has left
  83. bhaveshsgupta has joined
  84. bhaveshsgupta has left
  85. bhaveshsgupta has joined
  86. bhaveshsgupta has left
  87. pulkomandy has left
  88. pulkomandy has joined
  89. sonny has left
  90. bhaveshsgupta has joined
  91. Syndace has left
  92. Syndace has joined
  93. bhaveshsgupta has left
  94. bhaveshsgupta has joined
  95. pulkomandy has left
  96. pulkomandy has joined
  97. larma has left
  98. larma has joined
  99. bhaveshsgupta has left
  100. bhaveshsgupta has joined
  101. debacle has joined
  102. pulkomandy has left
  103. pulkomandy has joined
  104. kikuchiyo has left
  105. kikuchiyo has joined
  106. pulkomandy has left
  107. kikuchiyo has left
  108. Wojtek has joined
  109. kikuchiyo has joined
  110. pulkomandy has joined
  111. bhaveshsgupta has left
  112. bhaveshsgupta has joined
  113. debacle Can someone enlighten me in respect to disco, please? I hacked together a component. My client, Gajim, does not perform a disco "get" to that component, when connected. It does so, however, with other components, such as Biboumi or Cheogram. I assume, I'm missing something in the protocol, so that my component is considered worthwhile by Gajim to perform a "get". But what would that be?
  114. jonas’ debacle, how does gajim learn about your component?
  115. debacle jonas’ I added it to the roster with JID = mycomponent.myserver.com.
  116. jonas’ fun
  117. jonas’ no idea then
  118. debacle In Gajim it appears under "Transports" then, which seems to be correct.
  119. Kev Gajim is almost certainly doing what most clients do, and starting with a disco#items on your server's JID, and then walking those.
  120. bhaveshsgupta has left
  121. Kev I don't know, but that's the usual thing to do.
  122. Kev So if your component isn't listed in your server's disco#items, that might be an explanation.
  123. debacle Kev, I am not on that server, though.
  124. debacle Gajim asks my own server, but not that remote component.
  125. debacle To make things more fun: remote server name == remote component name.
  126. debacle But that is the same with Cheogram, which is also on a remote server and (if I'm not mistaken) has server name == component name.
  127. Kev I guess things to look for then are subscription state, and whether either of the other transports is using caps.
  128. bhaveshsgupta has joined
  129. bhaveshsgupta has left
  130. flow I always wondered about the mechanism which makes (external) components appear in the disco#items response. Is that documented/specified somewhere?
  131. bhaveshsgupta has joined
  132. jonas’ flow, in your server’s docs
  133. flow I'd expect there to be a generic implementation-independent mechanism
  134. Kev It's entirely down to your server. I keep getting tempted for M-Link to make it able to list arbitrary entries in its disco#items (so if there are common remote MUC services, it could list those for discoverability, for example).
  135. flow which is maybe coupled to the external components protocol
  136. jonas’ flow, there isn’t
  137. jonas’ Kev, prosody has that, fwiw
  138. jonas’ it’s useful because my HTTP upload service lives on a different domain which would typically not be associated with the user domains
  139. flow is there none because we do not need one, or nobody bothered to write something down?
  140. jonas’ we don’t need one
  141. jonas’ (IMO)
  142. jonas’ server config is fine
  143. flow I think debacle just demonstrated that one mechanism would be nice to have
  144. flow users/admin expect that their extenral component appears in clients once they configured it, not that an additional configuration step being required to do so
  145. jonas’ flow, I don’t think he did
  146. jonas’ flow, there would still be configuration required in any but the most trivial cases
  147. flow well, he wrote a component, was obviously be able to connect it with his server, but wondered why gajim did not discover it. AFAIKT the answer gajim did not discover it, is because it is not in the disco#items response
  148. jonas’ flow, you’d have to tell the component or the server for which domains to allow/attempt additions to disco#items
  149. flow jonas’, I don't think so
  150. jonas’ how’s biboumi knowing which domains to add itself to disco#items wise?
  151. flow I do not know biboumi, but the trival case is that component.example.org is added as item
  152. jonas’ to which domains?
  153. jonas’ my prosody has about five
  154. jonas’ plus about seven more component domains
  155. flow well, per default probably to all vhosts of the server
  156. jonas’ is that a server-side default or a component-side default?
  157. flow I don't argue that there are cases where manual configuration may be needed, but there could be sensible defaults
  158. flow probably server-side default
  159. jonas’ prosody already adds components which share the same domain suffix to a vhost
  160. Kev I think that if Flow is proposing a line in XEP-0114 that says "You probably want to add this to your disco#items too" (if there isn't one - I've not looked), then it seems sensible enough to me.
  161. jonas’ Kev, indeed
  162. jonas’ but it seemed more like a protocol suggestion to me
  163. bhaveshsgupta has left
  164. Kev It wasn't clear to me, I'm skimming in and out. But I think that line would be sensible (if not present already), whether it was Flow's suggestion or not :)
  165. flow Kev, I am actually also propose a standardized protocol allowing components to add themselves to the disco#items of the server
  166. jonas’ agreed, though I’d probably suggest to limit it to vhosts which are a suffix of the components domain name
  167. jonas’ you wouldn’t want your various domain-specific MUC services to appear on all domains for example
  168. flow but that is outside of the scope of xep114 obviously
  169. flow and a hint about a typical action you want to perform when using a xep sure is sensible
  170. flow however that action has to be performed (manual changes to the server configuration, automatically via stanardized protocol)
  171. Kev Would it be "allowing components to add " in that case, or "allowing authorised entities to add "?
  172. MattJ e.g. the admin, by editing a config file
  173. flow Kev, good question, probably "allowing authorised entities"
  174. bhaveshsgupta has joined
  175. Kev I suspect this is one of those nice things whose value isn't great enough to be worth the effort, but I might just be being unimaginative.
  176. Kev (We seem to have lasted this long with the current behaviour, although making that behaviour documented if it's not seems sensible to me)
  177. flow > jonas’> agreed, though I’d probably suggest to limit it to vhosts which are a suffix of the components domain name how about "add only under the one vhosts if the suffix matches, otherwise add to all vhosts"? :)
  178. asterix has left
  179. asterix has joined
  180. bhaveshsgupta has left
  181. Zash Admin ad-hoc command for adding disco items?
  182. kikuchiyo has left
  183. bhaveshsgupta has joined
  184. kikuchiyo has joined
  185. bhaveshsgupta has left
  186. bhaveshsgupta has joined
  187. debacle Kev, caps is a difference, indeed. Gajim sends disco get to the components with caps in the presence (or whatever it was), my component does not.
  188. bhaveshsgupta has left
  189. bhaveshsgupta has joined
  190. flow debacle, I am curious: why did you subscribe to your components presence in the first place?
  191. bhaveshsgupta has left
  192. bhaveshsgupta has joined
  193. debacle flow I'm not sure why I did :-) I wanted to see the component, because it is not only a transport, but also offers an adhoc command.
  194. debacle I believe, that the component also appears in Gajim under Transport, if I do not subsribe, but send/receive something over that transport.
  195. debacle I believe, that the component also appears in Gajim under Transports, if I do not subsribe, but send/receive something over that transport.
  196. sonny has joined
  197. bhaveshsgupta has left
  198. bhaveshsgupta has joined
  199. Zash has left
  200. Zash has joined
  201. kikuchiyo has left
  202. kikuchiyo has joined
  203. pulkomandy has left
  204. pulkomandy has joined
  205. kikuchiyo has left
  206. bhaveshsgupta has left
  207. bhaveshsgupta has joined
  208. bhaveshsgupta has left
  209. bhaveshsgupta has joined
  210. larma has left
  211. larma has joined
  212. bhaveshsgupta has left
  213. bhaveshsgupta has joined
  214. bhaveshsgupta has left
  215. bhaveshsgupta has joined
  216. pulkomandy has left
  217. pulkomandy has joined
  218. kikuchiyo has joined
  219. pulkomandy has left
  220. pulkomandy has joined
  221. Syndace has left
  222. Syndace has joined
  223. bhaveshsgupta has left
  224. bhaveshsgupta has joined
  225. pulkomandy has left
  226. pulkomandy has joined
  227. lovetox has left
  228. bhaveshsgupta has left
  229. bhaveshsgupta has joined
  230. lovetox has joined
  231. kikuchiyo has left
  232. pulkomandy has left
  233. bhaveshsgupta has left
  234. bhaveshsgupta has joined
  235. lovetox has left
  236. lovetox has joined
  237. pulkomandy has joined
  238. sonny has left
  239. sonny has joined
  240. kikuchiyo has joined
  241. bhaveshsgupta has left
  242. bhaveshsgupta has joined
  243. kikuchiyo has left
  244. bhaveshsgupta has left
  245. bhaveshsgupta has joined
  246. lovetox has left
  247. sonny has left
  248. pulkomandy has left
  249. lovetox has joined
  250. serge90 has left
  251. serge90 has joined
  252. pulkomandy has joined
  253. kikuchiyo has joined
  254. aj has joined
  255. asterix has left
  256. asterix has joined
  257. lovetox has left
  258. lovetox has joined
  259. bhaveshsgupta has left
  260. bhaveshsgupta has joined
  261. aj has left
  262. rion has left
  263. rion has joined
  264. kikuchiyo has left
  265. lovetox has left
  266. debacle has left
  267. kikuchiyo has joined
  268. bhaveshsgupta has left
  269. kikuchiyo has left
  270. bhaveshsgupta has joined
  271. bhaveshsgupta has left
  272. bhaveshsgupta has joined
  273. debacle has joined
  274. kikuchiyo has joined
  275. Wojtek has left
  276. bhaveshsgupta has left
  277. bhaveshsgupta has joined
  278. pulkomandy has left
  279. kikuchiyo has left
  280. pulkomandy has joined
  281. bhaveshsgupta has left
  282. bhaveshsgupta has joined
  283. asterix has left
  284. asterix has joined
  285. asus has joined
  286. asus has left
  287. kikuchiyo has joined
  288. pulkomandy has left
  289. bhaveshsgupta has left
  290. bhaveshsgupta has joined
  291. kikuchiyo has left
  292. kikuchiyo has joined
  293. lovetox has joined
  294. kikuchiyo has left
  295. pulkomandy has joined
  296. kikuchiyo has joined
  297. lovetox has left
  298. bhaveshsgupta has left
  299. lovetox has joined
  300. bhaveshsgupta has joined
  301. asterix has left
  302. asterix has joined
  303. bhaveshsgupta has left
  304. bhaveshsgupta has joined
  305. asterix has left
  306. asterix has joined
  307. bhaveshsgupta has left
  308. bhaveshsgupta has joined
  309. lovetox has left
  310. bhaveshsgupta has left
  311. lovetox has joined
  312. bhaveshsgupta has joined
  313. Alex has left
  314. Alex has joined
  315. larma has left
  316. larma has joined
  317. bhaveshsgupta has left
  318. bhaveshsgupta has joined
  319. lovetox has left
  320. lovetox has joined
  321. lovetox has left
  322. bhaveshsgupta has left
  323. bhaveshsgupta has joined
  324. asterix has left
  325. bhaveshsgupta has left
  326. bhaveshsgupta has joined
  327. lovetox has joined
  328. lovetox has left
  329. asterix has joined
  330. pulkomandy has left
  331. pulkomandy has joined
  332. pulkomandy has left
  333. pulkomandy has joined
  334. pulkomandy has left
  335. pulkomandy has joined
  336. bhaveshsgupta has left
  337. asterix has left
  338. pulkomandy has left
  339. pulkomandy has joined
  340. paul has left
  341. strar has left
  342. strar has joined
  343. debacle has left
  344. goffi has left