XSF Discussion - 2017-11-02


  1. jonasw

    moparisthebest, huh

  2. jonasw

    thanks for the hint

  3. jonasw

    moparisthebest, I always only saw DKIM_INVALID but I assumed that’s the mailing lists fault

  4. jonasw

    moparisthebest, even though, I can find the key in the DNS without issues?

  5. dwd

    jonasw, DKIM doesn't really work with mailing lists. It only works if all you do is 1:1 mail.

  6. jonasw

    dwd, I am aware of that.

  7. jonasw

    it’s not that I *want* to do DKIM.

  8. Ge0rG

    Only three days remaining for Council and Board candidates. Wow.

  9. jonasw

    I might roll back DKIM. It doesn’t seem to have helped with delivery to google or anyone anyways.

  10. jonasw

    and it only casues damage

  11. goffi

    I'm wondering about the MAM last call, do we have implementations of MAM for Pubsub? At least one we made for SàT Pubsub, but any other one?

  12. dwd

    goffi, Not that I know of. And our on MIX is out of date, since it needs the pointless id added.

  13. goffi

    is not needed to have 2 implementations to do a last call on MAM then?

  14. goffi

    actually the one on SàT Pubsub may be outdated to.

  15. dwd

    goffi, That's Final, not Draft, isn't it?

  16. goffi

    ah maybe

  17. jonasw

    in retrospect, DKIM-Spam-Issues probably also explain some of the XHTML-IM discussion :/

  18. jonasw

    iteam, can we configure the ML so that it mangles DKIM-signed messages in a way which avoids incorrect signatures?

  19. jonasw

    some people don’t have a choice on whether they send DKIM signatures

  20. moparisthebest

    jonasw, if you want to review component/protocol etc it's to a working state, pre-compiled .apk here or compile it yourself: https://github.com/moparisthebest/Conversations/releases

  21. jonasw

    a compiled build is not really useful to review something, is it?

  22. jonasw

    I can’t into mobile development, at all

  23. moparisthebest

    it links to both the mobile code and the component

  24. moparisthebest

    I think additionally the component needs to advertise in disco that it's an 'echo component' and that should be good enough

  25. Zash

    Which kind of review?

  26. Zash

    And of what?

  27. moparisthebest

    any kind and of any of it :)

  28. jonasw

    moparisthebest, frankly, I’d prefer a written specfiication over having to read java code.

  29. jonasw

    but I’m at work anyways

  30. moparisthebest

    the specification is there too in the readme, such as it is https://github.com/moparisthebest/xmpp-echo-self

  31. jonasw

    ok, might take a look this evening

  32. moparisthebest

    also the entire component is 130 lines of java code including comments

  33. moparisthebest

    I wasted about 4 hours trying to get sleekxmpp or slixmpp to work for this and failed...

  34. moparisthebest

    anyway being able to seamlessly SMS through my phone from gajim is sweet, or any other xmpp client supporting carbons

  35. jonasw

    I still find your (ab-)use of carbons... non-satisfactory

  36. jonasw

    this is a hack for something which deserves a proper solution.

  37. Zash

    Does this even make sense?

  38. moparisthebest

    I wouldn't call it a hack, multi-client is useless without carbons anyway, not sure why the component should be made complicated and require registration just to support use without carbons...

  39. jonasw

    it is a hack.

  40. Zash

    Transports being attached to the server is one of the very earliest design decisions in Jabber, so doing this in a non-awkward fashion will be Hard.

  41. moparisthebest

    this is one of the problems with some XMPP specs, instead of solving the simple problem simply, they attempt to solve complicated problems no one actually has yet but might have in the future in a more complicated way

  42. jonasw

    I think it makes sense to have per-user transports if the transport is linked to a hardware token owned by the user (e.g. SMS)

  43. Zash

    moparisthebest: IM is not a simple problem

  44. Zash

    It may look simple, but it's not.

  45. moparisthebest

    this solves the problem of a client-side sms transport and works perfectly so it seems rather simple and it works

  46. moparisthebest

    and requires no changes to other clients or servers, most importantly

  47. Zash

    "Works" and "Hack" are not mutually exclusive.

  48. Zash

    Hacks usually work.

  49. moparisthebest

    why is relying on other already defined XEPs a hack?

  50. jonasw

    moparisthebest, but doesn’t it strain the server by intentionally sending messages to non-existant domains?

  51. Zash

    Making something hacky that works is a good first step, as it helps understand the problem.

  52. moparisthebest

    nothing stops anyone from making a new XEP that does complicated state management and registration to avoid carbons, it's just useless

  53. moparisthebest

    jonasw, the domain exists

  54. jonasw

    ah, the domain of the "echo" component?

  55. moparisthebest

    it's a standard xmpp domain/component

  56. moparisthebest

    yep

  57. moparisthebest

    in fact my pre-compiled apk is pointed to my component running at echo.burtrum.org and works for anyone that can federate to that

  58. moparisthebest

    this should be replaced by discovery and fallback to a hard-coded component, eventually

  59. Zash

    Eh, is it wise to publish a thing that would leak all your SMSes to you?

  60. moparisthebest

    as a super alpha with a warning about it? sure

  61. jonasw

    Zash, is it wise to install a random apk from a random persons github page? ;-)

  62. moparisthebest

    I wouldn't, I'd compile it myself pointed to my own echo server instance :)

  63. moparisthebest

    I also just found out about this today: https://github.com/SilenceIM/Silence/pull/390 the SMS app is planning on adding a transport-over-xmpp option hehe

  64. Zash

    yetanothermessengerapp

  65. Link Mauve

    moparisthebest, what kind of issue did you have with slixmpp?

  66. Link Mauve

    Did you start from the echo_component example?

  67. moparisthebest

    yes Link Mauve it alternatively would return strings or parsed element structures but I could never get them back into a Message that I could .send etc, my 3 failed attempts are here: https://github.com/moparisthebest/xmpp-echo-self/tree/master/failed_python_attempts

  68. Link Mauve

    Strings or parsed element structures?

  69. moparisthebest

    so depending what I tried the <message> in the <forwarded> block would either be an Element or just a string

  70. Link Mauve

    Some of your code reads like it should work.

  71. Link Mauve

    moparisthebest, you need to load the xep_0297 plugin in order to get a Message, probably.

  72. moparisthebest

    Link Mauve, yea I did that too check xmpp-echo-self.forward.py

  73. moparisthebest

    xmpp-echo-self.py doesn't use forward and works with sleekxmpp but not slixmpp, but then I decided to go with forwards anyhow

  74. Link Mauve

    moparisthebest, the usual way is:

  75. Link Mauve

    forwarded_message = msg['forwarded']['stanza'] forwarded_message['to'] = your_user forwarded_message.send()

  76. Link Mauve

    From what I understand you want to do.

  77. moparisthebest

    Link Mauve, yea so sometimes I'd get an error on forwarded_message['to'] = your_user like 'str does not support .attr()' and sometimes I'd get an error on forwarded_message.send() like 'Element does not have .send() method'

  78. Link Mauve

    moparisthebest, that’s if you don’t have the plugin loaded.

  79. Link Mauve

    (Yes, slixmpp defaults to '' for unknown attributes…)

  80. Link Mauve

    (Yes, I hate it.)

  81. Link Mauve

    (And my branch changing that broke a ton of code in poezio alone, so I didn’t try to go forward.)

  82. Link Mauve

    (I want to test aioxmpp, if it managed to be less non-typed than slixmpp.)

  83. Link Mauve

    (But what I want the most, is a proper Rust library.)

  84. Link Mauve

    (xmpp-parsers is based on the opposite idea from slixmpp’s, types are good and you should use them, always.)

  85. Link Mauve

    (But it only parses and serialises stanzas and payloads, it isn’t an XMPP library per se.)

  86. jonasw

    Link Mauve, aioxmpp is rather strongly typed

  87. jonasw

    :-)

  88. Link Mauve

    I should try to move poezio to it, someday.

  89. jonasw

    sounds like a plan ;-)

  90. moparisthebest

    yes Link Mauve completely agree I wanted to do it in rust but not quite there yet :)

  91. moparisthebest

    anyway I spent a solid 4 hours trying different things with sleek and then slix then gave up so meh...

  92. moparisthebest

    would have tried aioxmpp but jonasw said no component support yet

  93. jonasw

    I didn’t say "yet" ;-)

  94. moparisthebest

    sorry sorry :P

  95. Link Mauve

    moparisthebest, both xmpp and tokio-xmpp support components, fyi.

  96. moparisthebest

    anyway Guus whack is nice and simple, typed but also super easy to just grab / manipulate XML directly, I like it :)

  97. Link Mauve

    I personally added that. :)

  98. Link Mauve

    The only constraint is that you can’t use both a client and a component when you import them in your project, it’s a feature which toggles the component or client thing.

  99. moparisthebest

    still need a new version of xmpp released though, current doesn't compile with stable rust, had to use git for my client thing

  100. Guus

    Wait what?

  101. Guus

    Someone mentioned me?

  102. moparisthebest

    yep, whack compliment

  103. Guus

    Yey!

  104. Guus

    Didn't work on that for ages though 😀

  105. Guus

    Also mostly code from Jive

  106. moparisthebest

    everything doesn't need to be developed for latest node.js in the last week to be good :)

  107. Guus

    Happy to hear it's helpful for you.

  108. dwd

    moparisthebest, You're still developing on last week's node.js? Luddite.

  109. Ge0rG

    My node.js is from last month!

  110. Ge0rG

    Okay, that was a lie. My node.js is 4.4.7 LTS, which is from mid-2016.

  111. moparisthebest

    wow that's like 6 versions behind

  112. moparisthebest

    8 is LTS now

  113. Link Mauve

    I had an update to 9.0 like yesterday, you’re all so out of date…

  114. moparisthebest

    node has to be the only software where LTS means like "ok I guess we'll support this version for 3 months"

  115. Zash

    lolwut

  116. tux

    Sounds like node.js is the software pendant to memory manufacturers. 🙃

  117. Zash

    What should happen if you send <presence type="error"/> (with nothing else)?

  118. zinid

    should be dropped by the server?

  119. dwd

    Zash, A little window should pop up telling you you have too much time on your hands.

  120. Zash

    > Discarding unhandled error presence (<nil>, unknown condition) from c2s: <presence type='error'>

  121. dwd

    Zash, I preferred my error message.

  122. Ge0rG

    The words "time" and "hands" should be replaced by the respective Emoji..

  123. Zash

    :time::hands:

  124. dwd

    I just tried it with Openfire. A world of nothing happened.

  125. zinid

    same for ejabberd :)

  126. moparisthebest

    https://github.com/openspace42/aenigma "aenigma provisions a fully functional and secure out of the box XMPP server you can get running today."

  127. moparisthebest

    never heard of that before, looks like bash script to set up ejabberd? odd

  128. zinid

    there are also nginx and sslh in the bundle ;)

  129. moparisthebest

    I only saw it because dev emailed a question to the sslh mailing list :)

  130. Flow

    which clients do support "xmpp over ssh"? Or do you need an ssh-client setting up a tunnel?

  131. Flow

    ahh s/ssh/ssl/

  132. moparisthebest

    xep-368 style? conversations does

  133. moparisthebest

    I had a list of implementations in the email hang on...

  134. dwd

    moparisthebest, He didn't mean that.

  135. moparisthebest

    oh got it

  136. Alex

    we need more board & council candidates here ;-) https://wiki.xmpp.org/web/Board_and_Council_Elections_2017#

  137. Ge0rG

    I might volunteer

  138. Alex

    Ge0rG: go, go , go

  139. moparisthebest

    what happens if there aren't enough candidates actually

  140. Ge0rG

    I've already started my election page, but had to leave home.

  141. jonasw

    I was kind of hoping that we’d have more candidates than seats so that the election actually gets interesting :/

  142. Alex

    moparisthebest: :-S we did not have such a case in the entire career of the XSF yet. Would have to lookup the bylaws then or apply myself ;-)

  143. Alex

    in the last years applications for board and council always came in close to the deadline

  144. Ge0rG

    Didn't we have situations in the past where the number of candidates matched the seats, making the election rather pointless?

  145. Kev

    It's not entirely pointless.

  146. Kev

    You don't get elected automatically you, still need to get elected.

  147. Ge0rG

    Not entirely, no

  148. Ge0rG

    I imagine that my council application will be rather controversial

  149. jonasw

    that’s a good thing, right?

  150. moparisthebest

    not that Ge0rG guy...

  151. moparisthebest

    haha <3

  152. Zash

    Make XMPP Great Again!

  153. moparisthebest

    I'd buy that hat

  154. Zash

    Tell the SCAM team

  155. jonasw

    well played

  156. Ge0rG

    That motto is kind of burned. Besides, it should be "Make Jabber Great Again"...

  157. Zash

    Ha

  158. Ge0rG

    I realized my error some time ago, but then Drumpf was elected already, doing bad things, so...

  159. moparisthebest

    oh right, no I'd vote against you if you ran on a slogan with Jabber in it

  160. Zash

    "Make Jabber Ours Again"

  161. Ge0rG

    moparisthebest: why so?

  162. Zash

    Ge0rG: For your own protection (against trademark infrigement)(?)

  163. moparisthebest

    yep!

  164. Ge0rG

    I know my trademarks

  165. moparisthebest

    zinid, so the sslh question guy is saying ejabberd will support '368 next version, in what way(s) ?

  166. zinid

    moparisthebest: what is 368

  167. zinid

    I don't remember all those stupid xep numbers

  168. Zash

    -xep 368

  169. Bunneh

    Zash: XEP-0368: SRV records for XMPP over TLS (Standards Track, Draft, 2017-03-09) See: https://xmpp.org/extensions/xep-0368.html

  170. zinid

    it supports it already for outgoing server connections

  171. Zash

    "Legacy SSL on port 5223 but with SRV records"

  172. moparisthebest

    presumably it already supported legacy ssl on port 5223 for c2s

  173. moparisthebest

    but what else?

  174. zinid

    in theory it should support sni, but it doesn't

  175. zinid

    sni for incoming connections