XSF logo jdev - 2020-01-22


  1. larma has left
  2. larma has joined
  3. larma has left
  4. larma has joined
  5. larma has left
  6. larma has joined
  7. aj has left
  8. rion has left
  9. rion has joined
  10. larma has left
  11. larma has joined
  12. aj has joined
  13. aj has left
  14. actupper has left
  15. actupper has joined
  16. actupper has left
  17. actupper has joined
  18. actupper has left
  19. sonny has joined
  20. debacle has left
  21. actupper has joined
  22. actupper has left
  23. actupper has joined
  24. sonny has left
  25. sonny has joined
  26. tsk has left
  27. tsk has joined
  28. sonny has left
  29. sonny has joined
  30. paul has joined
  31. wurstsalat has joined
  32. sonny has left
  33. sonny has joined
  34. sonny has left
  35. sonny has joined
  36. sonny has left
  37. lovetox has joined
  38. goffi has joined
  39. sonny has joined
  40. asterix has joined
  41. asterix has left
  42. pulkomandy has left
  43. asterix has joined
  44. pulkomandy has joined
  45. sonny has left
  46. sonny has joined
  47. paul has left
  48. pulkomandy has left
  49. asterix has left
  50. asterix has joined
  51. pulkomandy has joined
  52. lovetox has left
  53. lovetox has joined
  54. sonny has left
  55. sonny has joined
  56. paul has joined
  57. wurstsalat has left
  58. wurstsalat has joined
  59. goffi has left
  60. goffi has joined
  61. debacle has joined
  62. debacle has left
  63. debacle has joined
  64. Wojtek has joined
  65. sonny has left
  66. lovetox has left
  67. pulkomandy has left
  68. pulkomandy has joined
  69. sonny has joined
  70. lovetox has joined
  71. asterix has left
  72. asterix has joined
  73. sonny has left
  74. kikuchiyo has left
  75. sonny has joined
  76. asterix has left
  77. asterix has joined
  78. asterix has left
  79. asterix has joined
  80. sonny has left
  81. sonny has joined
  82. asterix has left
  83. asterix has joined
  84. kikuchiyo has joined
  85. kikuchiyo has left
  86. rion has left
  87. rion has joined
  88. kikuchiyo has joined
  89. pulkomandy has left
  90. pulkomandy has joined
  91. sonny has left
  92. sonny has joined
  93. asterix has left
  94. asterix has joined
  95. pulkomandy has left
  96. pulkomandy has joined
  97. asterix has left
  98. asterix has joined
  99. leosbrf has joined
  100. leosbrf flow , can you provide the link for the official ejabberd muc?
  101. flow leosbrf, it's well hidden at the end of https://docs.ejabberd.im/get-started/
  102. Link Mauve leosbrf, you can look it up yourself, like any other MUC, at https://search.jabber.network/
  103. flow > lovetox> em, disco info comes to mind? I usually view disco#info results as "this server supports this" and not as "you are allowed to use this feature"
  104. kikuchiyo has left
  105. flow how you discover that you are allowed or not allowed to use a feature is a good question. Typically you should get an error IQ back as response to an attempt to use a feature that, while being supported by the server, is not allowed for your account. Of course that error IQ should include a reasonable condition and a helpful text explaining that you are not allowed to do this because $reason
  106. Guus Zash / MattJ I've been asked to add a feature like Prosody's HTML log viewer to Openfire. Any obvious things I should take into consideration?
  107. Guus things you learned the hard way, when you implemented it?
  108. lovetox flow i think you misunderstood the requirement
  109. lovetox > senders should be aware of the recipient will not be able to answer because of that policy.
  110. lovetox so not the account itself does need that info
  111. lovetox other partys need the capabilities of the other client
  112. lovetox which is exactly what disco info is for
  113. lovetox and for your own capabilities you just disco info your own bare account jid
  114. lovetox which is done all the time, to see if MAM can be used and which version
  115. lovetox or httpupload, or whatever
  116. flow lovetox, right I misunderstood. However, I don't think that this makes my statement wrong.
  117. kikuchiyo has joined
  118. pulkomandy has left
  119. asterix has left
  120. pulkomandy has joined
  121. kikuchiyo has left
  122. asterix has joined
  123. kikuchiyo has joined
  124. lovetox but you are wrong, disco info to your bare jid does not in any way suggest what a server supports or not
  125. lovetox it tells you exactly what your account is able to use or not
  126. Zash Guus: Calendars are complicated. The current one is roughly a MAM query filtered through a template language. I'm kinda happy with that.
  127. lovetox if you want to know what a server supports, you have to disco info the service or host
  128. lovetox domain.org, or conference.domain.org
  129. lovetox or disco items to domain.org
  130. lovetox thats how you find out what a server supports
  131. pulkomandy has left
  132. pulkomandy has joined
  133. flow lovetox, that is potentially true, I believe that capabilities are often more fine-grained than the features returned by disco#info, so I am not sure if this is the right mechanism for that. I could be wrong though
  134. asterix has left
  135. asterix has joined
  136. asterix has left
  137. asterix has joined
  138. lovetox you can add as much fine grained caps as you want see, disco info from upload.domain.org, httpupload service
  139. lovetox has a whole dataform with fine grained settings
  140. lovetox like max-file-size
  141. pulkomandy has left
  142. pulkomandy has joined
  143. asterix has left
  144. asterix has joined
  145. asterix has left
  146. asterix has joined
  147. asterix has left
  148. asterix has joined
  149. asterix has left
  150. asterix has joined
  151. kikuchiyo has left
  152. leosbrf .
  153. leosbrf Hi guys, I'm creating a MUC client and I'm trying to use XEP-0424: Message Retraction, but it is not working. Could anyone help with that? I posted the details on stackoverflow: https://stackoverflow.com/questions/59859845/how-to-retract-a-message-in-ejabberd I also posted it on the ejabberd official muc, but still did not get an answer. Thanks.
  154. larma leosbrf, have you read the big red warning at the beginning of https://xmpp.org/extensions/xep-0424.html
  155. sonny has left
  156. pulkomandy has left
  157. larma I doubt any server supports 0424 tombstones. They are also not strictly required because the receiving client should receive both, the message and the retraction message
  158. sonny has joined
  159. larma If you want to ensure the retraction message appears in MAM, you probably need add a store hint when sending it (`<store xmlns="urn:xmpp:hints"/>`)
  160. asterix has left
  161. asterix has joined
  162. allie has left
  163. allie has joined
  164. pulkomandy has joined
  165. kikuchiyo has joined
  166. asterix has left
  167. asterix has joined
  168. asterix has left
  169. asterix has joined
  170. pulkomandy has left
  171. pulkomandy has joined
  172. asterix has left
  173. asterix has joined
  174. sonny has left
  175. sonny has joined
  176. sonny has left
  177. sonny has joined
  178. pulkomandy has left
  179. pulkomandy has joined
  180. sonny has left
  181. pulkomandy has left
  182. pulkomandy has joined
  183. bhaveshsgupta has joined
  184. lovetox has left
  185. kikuchiyo has left
  186. lovetox has joined
  187. lovetox has left
  188. lovetox has joined
  189. sonny has joined
  190. kikuchiyo has joined
  191. bhaveshsgupta has left
  192. kikuchiyo has left
  193. pulkomandy has left
  194. kikuchiyo has joined
  195. pulkomandy has joined
  196. sonny has left
  197. sonny has joined
  198. sonny has left
  199. sonny has joined
  200. sonny has left
  201. pulkomandy has left
  202. kikuchiyo has left
  203. sonny has joined
  204. kikuchiyo has joined
  205. sonny has left
  206. leosbrf thanks larma
  207. leosbrf has left
  208. bhaveshsgupta has joined
  209. Wojtek has left
  210. bhaveshsgupta has left
  211. bhaveshsgupta has joined
  212. bhaveshsgupta has left
  213. bhaveshsgupta has joined
  214. sonny has joined
  215. bhaveshsgupta has left
  216. bhaveshsgupta has joined
  217. debacle has left
  218. bhaveshsgupta has left
  219. kikuchiyo has left
  220. kikuchiyo has joined
  221. bhaveshsgupta has joined
  222. sonny has left
  223. bhaveshsgupta has left
  224. bhaveshsgupta has joined
  225. bhaveshsgupta has left
  226. bhaveshsgupta has joined
  227. bhaveshsgupta has left
  228. bhaveshsgupta has joined
  229. wurstsalat has left
  230. asterix has left
  231. asterix has joined
  232. bhaveshsgupta has left
  233. Syndace has left
  234. Syndace has joined
  235. goffi has left
  236. asterix has left
  237. pulkomandy has joined
  238. bhaveshsgupta has joined
  239. sonny has joined
  240. pulkomandy has left
  241. pulkomandy has joined
  242. pulkomandy has left
  243. pulkomandy has joined
  244. gav has left
  245. bhaveshsgupta has left
  246. gav has joined
  247. bhaveshsgupta has joined
  248. sonny has left
  249. debacle has joined
  250. bhaveshsgupta has left
  251. kikuchiyo has left
  252. kikuchiyo has joined
  253. bhaveshsgupta has joined
  254. bhaveshsgupta has left
  255. bhaveshsgupta has joined
  256. lovetox has left
  257. paul has left
  258. kikuchiyo has left