XSF Discussion - 2019-09-07


  1. Daniel

    If references are going to use fasten and Sims uses references am I going to fasten within the message itself?

  2. Ge0rG

    Daniel: references will only use fasten if they are added by another entity after the original message

  3. Ge0rG

    So if you put a SIMS into the original message, you don't fasten it.

  4. Ge0rG

    If you add a SIMS later, it needs to be fastened to the original, and might also contain a reference of the specific text fragment

  5. messi

    my file is already been encrypted in the file format of xmpp.jp so how to resolve it

  6. messi

    we have send u an mail on the given by you but ur mail id is not correct so kindly send us ur proper mailid

  7. ralphm

    Daniel: I will include a SIMS example

  8. flow

    why do we need the raplace attribute in <apply-to> (from the fasten protoxep)?

  9. ralphm

    To explicitly override a previous fastened thing, as opposed to having another one.

  10. flow

    I mean I think I understand it, but it should probably be spelled out what happend if it is not there

  11. flow

    or set to false (which I assume is the default)

  12. ralphm

    Kev just wanted to get the thing in the inbox to make sure we can start discussing it. I think everyone agrees that it needs work, and this is one of those things.

  13. ralphm

    Another is actually retracting fastened things, as well as retracting the original message completely.

  14. flow

    Sure, some figures/graphs would also be great

  15. Ge0rG

    I've heard there is a blog post in the making...

  16. ralphm

    Yes, I'm working on it right now :-D

  17. Ge0rG

    Guus: your anonymous s2s filter has failed indeed, I have a subscription request from one random account. I was just looking in the logs on the wrong machine. Will grep when I'm back at a real computer

  18. Guus

    Ge0rG: eek!

  19. Guus

    I'm interested in the details

  20. Ge0rG

    Guus: looks like the subscription request just went out unfiltered. I sent XML logs to you privately

  21. Guus

    Ge0rG: Thanks. This is puzzling. Messages did get blocked?

  22. Ge0rG

    Guus: yes

  23. Guus

    Puzzling. I'm unaware of another flow that leads to S2S session establishment, but there obviously is one

  24. Guus

    I'll look into this

  25. Zash

    Already establised sessions?

  26. Ge0rG

    Guus: you also have real accounts on that domain, and those are allowed to do s2s

  27. Guus

    I worded that wrong

  28. Guus

    it's the router (which conditionally causes s2s sessions to be established, but that's besides the point)

  29. Ge0rG

    Anon sessions shouldn't even be able to trigger the router

  30. Ge0rG

    Guus: if the s2s session already exists, will an anon user be able to send messages thorough it?

  31. Guus

    Ge0rG obviously anon sessions hit the router. If not, we me might as well drop support for anonymous.

  32. Guus

    s2s session existence shouldn't be a factor, but obviously, I'm missing something.

  33. Ge0rG

    Guus: I don't think there was a session to my private server before I sent the subscription

  34. Guus

    shouldn't matter, but could rule something out

  35. Guus

    I'm debugging now

  36. flow

    Ge0rG, what was/is the latest on you approaching the german government regarding open-standards communication?

  37. Ge0rG

    flow: no useful news yet

  38. Ge0rG

    flow: the last status was probably logged in a Board meeting a month ago

  39. Guus

    Once more, Ge0rG improves the quality of Openfire.

  40. Guus

    I know that some of you don't think that that's difficult, but I don't see many of you do what Ge0rG does 😛

  41. Ge0rG

    Guus: maybe it's a sign that everyone is lacking resources?

  42. Ge0rG

    While I'm a professional pen tester, this engagement didn't require any of my special skills.. 😉

  43. Guus

    Be like Ge0rG .

  44. Ge0rG

    Ironically, people tell me to be less like Ge0rG. Don't be like grumpy Ge0rG.

  45. Guus

    Don't be like people that are telling Ge0rG to be less like Ge0rG. Be like Ge0rG.

  46. Ge0rG

    Guus: may I quote you on my next Council election rally?

  47. Guus

    Yes please. I want a kickback on the profit of t-shirts with this on it though

  48. Zash

    Guus, ok, I'll try to be grumpier.

  49. Guus

    THAT'S THE SPIRIT

  50. pep.

    The tagline on my website is already "grumpy pep". Should I try harder?

  51. Zash

    The Grumpy XMPP Gang

  52. Ge0rG

    pep.: you are not nearly grumpy enough

  53. pep.

    gotcha

  54. pep.

    I think you've missed my many attempts on Debian and dynamic typing though

  55. Ge0rG

    pep.: maybe. Did you write them in the off topic muc?

  56. Ge0rG

    http://exple.tive.org/blarg/2019/09/06/forward-motion/

  57. Ge0rG

    Our candidates are: Mattermost, Matrix/Riot.IM, Rocket.Chat, and Slack

  58. Ge0rG

    This is frigging sad

  59. mathieui

    wow that’s awful

  60. pep.

    When do we convert Mattermost or Rocket.Chat to XMPP?

  61. pep.

    (or Riot?)

  62. pep.

    XMPP isn't even mentioned in the "solutions we didn't pick and why"

  63. pep.

    ..

  64. pep.

    XMPP implementations, that is.

  65. pep.

    Though Zulip was XMPP, no?

  66. mathieui

    I don’t think so

  67. Zash

    HipChat was

  68. Zash

    Don't think anything else in that space is

  69. ralphm

    Yup HipChat was XMPP, written in Twisted/Python. Had some issues and then Atlassian made a deal with Slack.

  70. Ge0rG

    Everybody makes a deal with slack. Except Microsoft, they just sneakily force-install Teams on all windows computers.

  71. pep.

    Just like Android has non-removable Google stuff? It's pretty much the default nowadays :)

  72. pep.

    Gotta take advantage of providing a platform

  73. Guus

    Zulip isnt XMPP

  74. pep.

    k

  75. edhelas

    https://twitter.com/edhelas/status/1170465450079207430

  76. pep.

    Indeed.

  77. pep.

    I wasn't that direct, https://post.lurk.org/@pep/102753556039334817 :-°

  78. edhelas

    but actually, what removed XMPP from the choice was the lack of a proper "Slack like" client

  79. edhelas

    Movim is approaching a bit the design but doesn't have this UX/UI that is shared among alllll those projects

  80. pep.

    Sure, what I said above. Ah wait no that was in the other room. "pep.> Our lack of bundled solution (server+web client) is probably the culprit"

  81. edhelas

    possible

  82. linkmauve

    pep., do we really have none of that? I’m pretty sure I saw some such (commercial) offerings.

  83. pep.

    Do we?

  84. pep.

    I'd like to hear about them

  85. mathieui

    (I’m pretty sure they got their suggestions off their discourse forum, whose users probably have not heard of such solutions)

  86. edhelas

    > all i am going to say about that: we are looking at products that make our community more productive and resolves issues we have around communication, we are not looking at protocols. if there is an overlap, cool. if not, cool.

  87. edhelas

    from a friend that is working at Mozilla

  88. pep.

    So the manifesto is just for lolz? As usual?

  89. edhelas

    ¯\_(ツ)_/¯

  90. mathieui

    edhelas, it says so there: http://exple.tive.org/blarg/2019/04/26/synchronous-text/

  91. pep.

    > We aren’t picking an outlier; whatever stack we choose needs to be a modern, proven service that seems to have a solid provenance and a good life ahead of it. We’re not moving from one idiosyncratic outlier stack to another idiosyncratic outlier stack. Does that include XMPP?

  92. Zash

    Does that include IRC?

  93. pep.

    Apparently it does

  94. Zash

    Also "service"

  95. Zash

    XMPP is not a service.

  96. Zash

    Or a product.

  97. edhelas

    > mattermost inc. is very happy to provide support and long-term gurantees for their product when asked. and given by the range and amount of customers they already support, I have no reason to doubt that

  98. edhelas

    I think that it's pretty clear what we're missing there

  99. pep.

    I'm not convinced "one more solution" is the solution though :(

  100. Zash

    1. Start Jabber Inc. 2.0! 2. ??? 3. Profit!

  101. Zash

    History ain't gonna repeat itself! (or wait)

  102. edhelas

    it's not about Jabber or stuff like that

  103. Zash

    > Inc. -orporated

  104. edhelas

    but proposing a client + server package with a "modern" (basically Slack like) client and full support behind it