XSF Discussion - 2020-05-19

  1. Alex

    just started Memberbot for our current voting period

  2. Ge0rG

    is it that time of the year again?

  3. Guus

    kindly add 'hell yes!' to the list of accepted answers.

  4. Zash

    s/year/quarter/

  5. pep.

    xmpp:memberbot@xmpp.org?message;body=woo

  6. Guus

    woo?

  7. pep.

    just to initiate the chat :( ✎

  8. pep.

    just to initiate the chat :) ✏

  9. Guus

    ah, I traditionally use o/ for that.

  10. Ge0rG

    does the bot accept "Yes" as a "yes" already?

  11. Guus

    Hell no?

  12. Guus

    unsure, I'm conditioned to use lower case.

  13. Daniel

    No

  14. Ge0rG

    Guus: me too, but my mobile client's keyboard will auto-capitalize

  15. Zash

    Buttons^W Quick Responses ?

  16. Ge0rG

    Alex: two of the applicants have 2019 application links in place. Was that a deliberate move by the applicants or did they actually miss their deadline and didn't do anything?

  17. Alex

    let me check

  18. Alex

    @Ge0rG‎ fixed, thans

  19. Ge0rG

    👍

  20. Syndace

    > Buttons^W Quick Responses ? soon (tm)

  21. Ge0rG

    Why oh why did I parse that as "buttocks"?

  22. Guus

    Freud?

  23. moparisthebest

    apparantly gajim gives you the option to delete your account on the server, anyone know where "delete my account" is defined?

  24. moparisthebest

    I can only find https://xmpp.org/extensions/xep-0133.html#delete-user which seems to be only for administrators

  25. moparisthebest

    and https://xmpp.org/extensions/inbox/account-management.html#deletion which looks like it was never accepted

  26. Ge0rG

    moparisthebest: https://xmpp.org/extensions/xep-0077.html#usecases-cancel

  27. moparisthebest

    thanks Ge0rG ! that explains why my searching for "delete" found nothing...

  28. Ge0rG

    The "remove" is also well-hidden in the XML

  29. moparisthebest

    IBR security concerns could use some work, in practice how many servers actually ask for current password when changing your password and/or deleting your account?

  30. moparisthebest

    it gives a MAY up higher, but that seems like a pretty big security concern: > A given deployment MAY choose to require additional information (such as the old password or previously-gathered personal information) before cancelling the registration. In order to do so, the server or service SHOULD return a Data Form in the error stanza

  31. jonas’

    Alex, memberbot doesn’t send presence to me

  32. jonas’

    (jonas@wielicki.name)

  33. jonas’

    that’s a first

  34. pep.

    > does the bot accept "Yes" as a "yes" already? I fixed it a few months ago? dunno if Alex is using it though

  35. Ge0rG

    Yes, it worked. Thanks very much!

  36. Alex

    @jonas’‎ all looks good on my end. Also have done not modifications with memberbots roster

  37. jonas’

    hm

  38. jonas’

    I re-requested authorization, that hasn’t worked so far

  39. Alex

    @pep. not running the latest versions, I tried, but get exceptions when I ran it ofr testing. Still trying to find out whats going wrong. I think it may be related to chat states. Also, there is still a PR open from you.

  40. Alex

    I cherry pickted the Yes, No changes to the branch I run

  41. jonas’

    May 19 16:07:01 s2sin5578198878d0 debug Received[s2sin]: <presence type='unavailable' from='memberbot@xmpp.org' to='jonas@wielicki.name'>

  42. jonas’

    I’m getting straight type='unavailable' back on subscribe

  43. jonas’

    now it replies to me

  44. jonas’

    but still shows unavailable presence

  45. jonas’

    something is definitely weird

  46. MattJ

    > load_roster: loading for offline user: memberbot@xmpp.org

  47. MattJ

    (Prosody log)

  48. jonas’

    also it stopped replying again

  49. Alex

    @jonas' bot crashed, will be online again soon

  50. jonas’

    thanks

  51. jonas’

    I see memberbot & presence now

  52. Alex

    @pep. this is what I get when I try to start a new coting session with the latest Memberbot code on Github: ``` 2020-05-19 18:55:04,652 DEBUG RECV: <message xml:lang="en" to="memberbot@palaver.im/16903948272308590243398178" from="alex@palaver.im/gajim.ZV7K69RF" type="chat" id="5acded22-1e4a-4e4a-a9b3-d9110d2aca3f"><origin-id xmlns="urn:xmpp:sid:0" id="5acded22-1e4a-4e4a-a9b3-d9110d2aca3f" /><request xmlns="urn:xmpp:receipts" /><body>hi</body></message> 2020-05-19 18:55:04,654 DEBUG Event triggered: message 2020-05-19 18:55:04,655 DEBUG SEND: <message to="alex@palaver.im/gajim.ZV7K69RF" id="f9429227-baf9-4a1a-a03a-fc39894e8ae8-13" xml:lang="en"><composing xmlns="http://jabber.org/protocol/chatstates" /></message> 2020-05-19 18:55:04,657 DEBUG Looking up cached disco#info data for alex@palaver.im/gajim.ZV7K69RF, node . 2020-05-19 18:55:04,658 DEBUG SEND: <r xmlns="urn:xmpp:sm:3" /> 2020-05-19 18:55:04,658 DEBUG SEND: <iq id="f9429227-baf9-4a1a-a03a-fc39894e8ae8-15" to="alex@palaver.im/gajim.ZV7K69RF" type="get"><query xmlns="http://jabber.org/protocol/disco#info" /></iq> 2020-05-19 18:55:04,659 DEBUG SEND: <message xml:lang="en" to="alex@palaver.im/gajim.ZV7K69RF" type="error" id="5acded22-1e4a-4e4a-a9b3-d9110d2aca3f"><error type="cancel"><undefined-condition xmlns="urn:ietf:params:xml:ns:xmpp-stanzas" /><text xmlns="urn:ietf:params:xml:ns:xmpp-stanzas">Slixmpp got into trouble.</text></error></message> 2020-05-19 18:55:04,660 ERROR Error handling {jabber:client}message stanza Traceback (most recent call last): File "/home/alex/.local/lib/python3.6/site-packages/slixmpp/api.py", line 133, in run return handler(jid, node, ifrom, args) File "/home/alex/.local/lib/python3.6/site-packages/slixmpp/plugins/xep_0115/static.py", line 73, in supports info = self.disco._wrap(ifrom, jid, info, True) File "/home/alex/.local/lib/python3.6/site-packages/slixmpp/plugins/xep_0030/disco.py", line 780, in _wrap iq.append(payload) File "/home/alex/.local/lib/python3.6/site-packages/slixmpp/xmlstream/stanzabase.py", line 1170, in append raise TypeError TypeError During handling of the above exception, another exception occurred: ```

  53. pep.

    Alex, maybe move this to slixmpp@muc.poez.io :)

  54. pep.

    Also I don't get notified on "@pep."

  55. Alex

    I use Slack too often ☺️

  56. Zash

    😱️

  57. pep.

    Alex, fwiw, I also can't run memberbot, serialization fails I'm not entirely sure why..

  58. Alex

    okay, good to know that its not related to my python skills only ;-)

  59. pep.

    Except it's not the same error

  60. jonas’

    Daniel, Conversations prefers Opus for audio calls, right?

  61. Daniel

    jonas’: yes

  62. jonas’

    thanks :)

  63. Neustradamus_

    It is possible to update the memberbot logo? Always the old... - https://commons.wikimedia.org/wiki/File:XMPP_logo.svg

  64. Neustradamus_

    About "? (yes / no)" When we click on: - yes, it is showed: yes - no, it is showed: No

  65. pep.

    PR welcome

  66. moparisthebest

    so python memberbot crashes a lot and can't be reliably ran across different machines, anxiously awaiting memberbot-rs pep. :)

  67. pep.

    :-°

  68. pep.

    I'm using it to work on xmpp-rs mostly

  69. eevvoor

    Mentioning best prectices: Beagle IM does not want to use mentioning without @ https://github.com/tigase/beagle-im/issues/14 ✎

  70. eevvoor

    Mentioning best practices: Beagle IM does not want to use mentioning without @ https://github.com/tigase/beagle-im/issues/14 ✏

  71. eevvoor

    > Neustradamus: We type the first letter (or two or more), after tab key, the first username is detected, tab again, the second... > woj-tek: Great that it works in other applications. Though, it's never been specified so that's customary at best. Morover, it can lead to excessive notification when we namedrop someone without intention to rise attention. Is there some standards / XEPs we could come up with?

  72. pep.

    Yeah that was mentioned in jdev yesterday, re mentions

  73. eevvoor

    ah ok

  74. pep.

    the issue here is that choosing a specific character is again mixing input format and wire format

  75. pep.

    There's conversejs using 0372 for this specific use-case. The user types @ and autocompletes a nick, and converse on the wire sends 0372. The receiving client then knows it's been mentioned. It doesn't have to parse "@" in the text, and it can also use another character if it wants (or no character)

  76. eevvoor

    Where is that docunented? What could I cite here in the github issue pep.?

  77. pep.

    I'm replying in the issue

  78. pep.

    And Wojtek knows what I'm talking about I assume

  79. pep.

    "Current situation is is not ideal and it seems that the best way forward would be to implement XEP-0372: References: Mentions and while we consider it there is no ETA."

  80. pep.

    (fwiw I'm not especially advertising for 372, I just care about the distinction between input and wire format :p)