XSF Discussion - 2014-02-10


  1. Kev

    Hey folks. Pubsubbish question.

  2. Kev

    Would people think it unexpected if they did a disco#items on pubsub.server.tld, and got back results for something1@pubsub.server.tld, something2@pubsub.server.tld, something3@pubsub.server.tld... each with a single node per JID?

  3. Kev

    (Note use of 'unexpected' rather than 'illegal')

  4. ralphm

    Kev: I think so, yet.

  5. ralphm

    yes

  6. ralphm

    It doesn't seem illegal, though.

  7. ralphm

    Reading the prose in XEP-0030, it does seem to favor addressable entities (i.e. things with a JID) over using nodes.

  8. ralphm

    Having an empty node identifier is ill-defined in XEP-0060. Of course there's a reference to a section on collections, but that section has moved to it's own XEP.

  9. ralphm

    (and I am still of the opinion that collections are not a thing to want, even though it might appear that way at first)

  10. dwd

    ralphm, I like collections.

  11. ralphm

    dwd: no you don't, trust me.

  12. dwd

    Kev, Unexpected, yes.

  13. dwd

    ralphm, I implemented "full" collections. I really quite like the notion.

  14. ralphm

    I haven't found any compelling use case where you want to deal with DAGs and all the explicitness of setting them up. I did think I wanted to use them on multiple occasions, and then always did a second implementation with implicit nodes as an interface to an existing (or new even) backend's business logic.

  15. ralphm

    Some of those nodes would kinda feel like collections, but without all the hassle and fixed semantics.

  16. dwd

    Yes, I think if you're implementing a customer pubsub layer over existing logic, you don't need them. But I'd prefer a way to avoid that being the only way to deploy pubsub.

  17. ralphm

    dwd: I'm sympathetic to that idea, but it always seems to result in distributed knowledge about 'resources', with all the synchronisation issues that come with that.

  18. ralphm

    I'd like to compare this with the way the web currently works, especially after CGI was 'invented'. Most of the time, you don't explicitly create resources there, either.

  19. dwd

    Don't *say* that. The REST people will crawl out of the woodwork.

  20. dwd

    Once they start, they never shut up.

  21. ralphm

    Fortunately, I'm room admin.

  22. ralphm

    And I'm also ok with creating leaf nodes explicitly. But collections are arguably designed to mimick some existing backend topology, and I think it's better to do that by making the pubsub protocol part of that backend, instead of treating it as an external, second-class thing.

  23. ralphm

    Taking that to its conclusion, you generally don't need all the explicitness of collection node configuration.

  24. ralphm

    And probably also not exposing the internal structure of where an event came from.

  25. Kev

    ralphm / dwd: Thanks.

  26. ralphm

    Kev: I'd love to hear more about the actual use case.

  27. Kev

    I think it's just a wart of someone not knowing what the usual way of doing things was.

  28. Kev

    I saw this happening, there's no reason for it to need to be this way. I just wanted to check I wasn't just being Wrong before I suggested it was unusual for them to do this.

  29. dwd

    As I recall, at one point, that was considered the right way.

  30. ralphm

    dwd: wait what?

  31. dwd

    ralphm, Pubsub nodes having a local-part to their jid.

  32. Kev

    I don't remember this.

  33. ralphm

    dwd: I think you are confused with http://xmpp.org/extensions/xep-0024.html

  34. dwd

    Oh, no, I'm muddled. It was resource-parts that were added.

  35. dwd

    '60§4.6.1 I'm thinking of.

  36. dwd

    The Node identifier MUST NOT be specified by the node identifier, in fact.

  37. dwd

    Yay for overloaded terms!

  38. Kev

    Ambiguity is underrated.

  39. Kev

    And, to be clear, when I say 'ambiguity', I'm using it in the sense of 'being clear'.

  40. ralphm

    Kev: if you want to argue against 'wrong', have a look here: http://howtosdeit.blogspot.nl/2014/02/comunicate-rabbitmq-with-publish.html?spref=tw

  41. Kev

    Ta.

  42. Kev

    As an aside, I've decided not to put up Swift ideas for GSoC this year. I don't think I've got time to mentor properly.

  43. ralphm

    Kev: rather that then finding out while students are at it.

  44. ralphm

    Kev: good call

  45. Kev

    It's a shame. I like GSoC, but work has become...busy.

  46. Simon

    This whole day-job thing really cramps one's style.

  47. ralphm

    :-)

  48. Kev

    Wouldn't swap it.

  49. ralphm

    "They say Google is dropping #XMPP on May 15th. So it seems we are dropping Hangouts in the day of our first anniversary. F*ck them!" — LoquiIM (https://twitter.com/LoquiIM/statuses/432867870016434176)

  50. Tobias

    they?

  51. Tobias

    are they referring to some magic 8-ball?

  52. ralphm

    Don't know. But if that turns out to be true, I can see how they will support unauthenticated encryption on all s2s traffic by May 19.

  53. Kev

    Heh.

  54. Simon

    Anyone know any of the Loqui guys?

  55. ralphm

    I don't think I do.

  56. Simon

    I've asked Sonny Piers since he works in Spain and in XMPP and I don't think there are many XMPP startups in Spain.

  57. ralphm

    As a counter argument, I know virtually no XMPP developers in The Netherlands, where I'm sure there are some.

  58. dwd

    {citation-needed}

  59. dwd

    I mean for the May 15th thing.

  60. dwd

    Ah, Google Voice is dropping XMPP support on May 15th.

  61. Zash

    Google Voice has XMPP support?

  62. dwd

    http://www.androidpolice.com/2013/11/04/merging-of-google-voice-and-hangouts-will-result-shutting-down-all-3rd-party-voice-apps-in-may-2014/ and so on. Announced on 2013/11/01 I think.

  63. Tobias

    Zash, come on, admit it, you'll gonna miss it

  64. Zash

    Yes, me, of all people, is gonig to miss it.

  65. ralphm

    dwd: yeah, that's the only stuff I could find, too. I'd be very amazed if all XMPP support, i.e. the old Google Talk network, would be shutdown at that date. Of course I've been surprised before.

  66. Neustradamus

    and: http://blog.obihai.com/2013/10/important-message-about-google-voice.html

  67. Neustradamus

    https://productforums.google.com/forum/?_escaped_fragment_=topic/voice/CdojHZ5_WBU#!topic/voice/CdojHZ5_WBU

  68. dwd

    Chatting to Richard Barnes, "our" RAI AD - he's offering to help push for MozSpace as needed from the Mozilla side.

  69. Zash

    MozSpace?

  70. bear

    zash - where can I find luasec?

  71. bear

    I have added prosody.im's apt repo but apt is not finding it

  72. Zash

    Which distro/version?

  73. bear

    nv

  74. bear

    it's liblua5.1-sec1 - like I had any chance of guessing that package name

  75. Zash

    Ah, heh

  76. Tobias

    sec1 is better than sec0

  77. bear

    ah crap - where is util.sql found?

  78. Zash

    In trunk

  79. bear

    what file - it's obvious my current server has it, but i'm setting up yet another test server

  80. bear

    and running into that error

  81. Zash

    util/sql.lua

  82. Zash

    It's not included in 0.9

  83. bear nods

  84. Tobias

    it's part of Prosody Business Edition

  85. bear

    I am missing it from my install notes

  86. bear

    hmm, it says module DBI isn't found - which file is that?

  87. Zash

    Separate package

  88. Zash

    LuaDBI

  89. Zash

    https://prosody.im/doc/depends#luadbi

  90. bear

    ah - lua-dbi-mysql

  91. bear

    wow - my notes from before really sucked

  92. bear

    why am I asking prosody questions in here

  93. bear sighs