jdev - 2019-09-21

  1. lksjdflksjdf has left
  2. ralphm has left
  3. ralphm has joined
  4. Daniel has left
  5. sonny has left
  6. Daniel has joined
  7. Daniel has left
  8. sonny has joined
  9. wurstsalat has left
  10. Daniel has joined
  11. wurstsalat has joined
  12. larma has left
  13. Daniel has left
  14. Daniel has joined
  15. larma has joined
  16. Daniel has left
  17. Daniel has joined
  18. Daniel has left
  19. Daniel has joined
  20. Daniel has left
  21. Daniel has joined
  22. Daniel has left
  23. Daniel has joined
  24. Daniel has left
  25. Daniel has joined
  26. Daniel has left
  27. Daniel has joined
  28. Daniel has left
  29. Daniel has joined
  30. Daniel has left
  31. Daniel has joined
  32. Daniel has left
  33. Daniel has joined
  34. sonny has left
  35. sonny has joined
  36. lksjdflksjdf has joined
  37. sonny Hey, so xmpp.js supports "dynamic" dns/http lookups. However a user is asking to add multiple endpoints support *client side* in configuration. Is that a common requirement?
  38. sonny https://github.com/xmppjs/xmpp.js/issues/568
  39. sonny or common use case*
  40. pep. I'm curious what their use-case is, fallback endpoints? Maybe they can solve that at the DNS level rather?
  41. sonny "I'm a user that doesn't have admin capabilities to update DNS on our XMPP servers, and admins who do are reluctant to do so because of pre-existing network dependencies"
  42. pep. I see. Then I guess it depends if you want to support this use-case? I can't help much I'm not sure how common that is
  43. sonny ok - thanks
  44. pep. sonny, maybe ask conversejs? or jsxc
  45. pep. JC is not on this channel, maybe you can join discuss@conference.conversejs.org
  46. sonny why? I don't think it is web specific
  47. pep. Ah when that user says endpoint, what kind of endpoint is that
  48. pep. rereads the issue
  49. sonny yep it's unclear
  50. pep. What does "enpoint" in the doc means? In the documentation bits they quoted
  51. sonny hostname and port
  52. vanitasvitae has left
  53. sonny tcp/direct tls/websocket
  54. pep. interesting
  55. sonny here you get an idea https://github.com/xmppjs/xmpp.js/tree/master/packages/resolve#usage
  56. vanitasvitae has joined
  57. sonny so if you pass a domain to the client library it uses `resolve` to fetch endpoints, sort them, and fallbacks https://github.com/xmppjs/xmpp.js/tree/master/packages/client#client-1
  58. sonny yeah doc is really lacking I think it's defeating its purpose by confusing users
  59. pep. What project doesn't have lacking documentation..
  60. sonny prosody? 😀
  61. pep. I'm not convinced. (Not saying it's particularly bad either)
  62. Alex has left
  63. Alex has joined
  64. rion has left
  65. rion has joined
  66. Kev has joined
  67. Kev has left
  68. Kev has joined
  69. Kev has left
  70. Kev has joined
  71. Kev has left
  72. lovetox hm can i send a direct invite as pm to a muc participant?
  73. Zash I don't see why not
  74. lovetox hm yes
  75. Zash Unless it's tied too hard to invites being in type=normal messages?
  76. lovetox yeah i just looked that up
  77. lovetox but nothing says that a direct invite must be type=normal
  78. lovetox where you are getting this from?
  79. lovetox also private message can be type=chat
  80. lovetox or type=normal
  81. lovetox it just is not allowed for it to be type=groupchat
  82. Zash Mostly just based on examples in https://xmpp.org/extensions/xep-0249.html having no type attribute
  83. Zash It /would/ be kinda cool to send invites to entire rooms
  84. lovetox yeah but that just doesnt mean a thing does it
  85. lovetox all examples are minimal examples
  86. lovetox and only contain stuff which is absolutley necessary
  87. Kev has joined
  88. Kev has left
  89. lovetox has left