XSF Discussion - 2013-12-17


  1. bear just registered xmmp.org and pointed it's A record to xmpp.org

  2. waqas

    Thanks bear!

  3. bear

    not sure how to get hover to do the dns for web forwards, gladly will point it to our nameserver if that is easier

  4. ralphm

    emcho: did you get a stand, too?

  5. intosi

    bear: I think we can work out the details for DNS. iteam is glad to support it.

  6. bear

    intosi - cool - just let me know what to put as nameservers then

  7. bear

    oh - probably same as xmpptest.com

  8. bear

    i'll change it to ns1.jabber.org now

  9. bear

    ok, I made xmmp.org have the same nameserves as xmpptest.com

  10. intosi

    I'll set something up for it.

  11. intosi

    bear: DNS is set up.

  12. intosi

    -- Checking SOA records of slaves ... xmmp.org: OK

  13. intosi

    Hmm, except that ns3 isn't syncing. I'll chat with Florian to fix that.

  14. bear

    cool

  15. intosi

    We had the same issue with xmpptest.com.

  16. bear

    cool - now xmmp.org should point to xmpp.org

  17. intosi

    It works for me.

  18. intosi

    Best thing: didn't even have to change the nginx config to make it happen.

  19. bear

    yea, gotta love a good nginx config

  20. bear

    good in this case being simple

  21. dwd

    So, lots of good news yesterday, then.

  22. dwd

    Oh, hadn't noticed the xmmp.

  23. bear

    yea, set that up and then read the news from ralph and saw that the forwarded email has XMMP in it :)

  24. dwd

    bear, If you're up, want to Bloggerize the stand?

  25. bear

    sure

  26. bear

    shall i also mention jingle ?

  27. ralphm

    Yeah, I shall have a word with Wynke on that :-D

  28. dwd

    bear, In what sense?

  29. ralphm

    I'd like to know if Jitsi got a stand too

  30. ralphm

    but emcho isn't responding

  31. dwd

    emcho, ICMP_ECHO_REQUEST

  32. bear

    oh, yea misread that - i'll do ours now and another later

  33. dwd

    Two posts is better than one.

  34. ralphm summons emcho

  35. intosi

    raise Emcho()

  36. bear

    something along the lines of: The XSF is happy to annouce we will again be present at FOSDEM with the Realtime Lounge and a stand" ?

  37. ralphm

    'and a stand'?

  38. bear

    yea, i ran out of words :/

  39. ralphm

    bear: some words: epic, must-see, awesome

  40. intosi

    Interactive, responsive design, standards-compliant?

  41. ralphm

    bear: unique, Jingle, IoT, demos

  42. bear

    http://www.piratepad.ca/p/VCq8kVvwUa

  43. ralphm

    bear: hah, no

  44. bear

    no?

  45. ralphm

    bear: you are drafting, we are giving you words you ran out of. Seems like a great deal.

  46. bear

    ah

  47. bear

    one sec

  48. Kev

    Scalable. Secure. World-class. Cutting-Edge. Value-add. Blue-sky.

  49. Kev

    Am I doing this right?

  50. ralphm

    oh, oh, I know: synergy, solutions

  51. ralphm

    and WebRTC of course

  52. intosi

    Kev, ralphm: spot on!

  53. dwd

    If you're struggling, might I suggest we nudge Laura?

  54. intosi

    Toss in high grade encryption, too. It appears to be a popular topic.

  55. ralphm

    dwd: that's a great point

  56. Kev

    Anonymous. Strong identity. Strong authentication. Dialback.

  57. Kev

    bear: Your challenge, should you choose to accept it, is to get all of these in :p

  58. bear

    oh, man - the voice of reason from dave

  59. bear

    hell no, i'm punting as we have a real wordsmith now ;)

  60. ralphm

    bear: but yeah, drop the 'stand' part

  61. ralphm

    the lounge is the thing

  62. bear writes a members announcement

  63. bear

    err thingy

  64. bear

    yea, that

  65. ralphm

    we do have tables, of course

  66. ralphm

    but stands are what the other guys do. We're way past that :_D

  67. bear

    :)

  68. intosi

    We did stands 10 years ago, we moved on.

  69. dwd

    Stands are so three years ago.

  70. bear

    ok, request for help sent

  71. intosi

    Still miss our flag. Waves fist at unnamed German guy who kept it.

  72. dwd

    Flag?

  73. fippo

    intosi: ulrich?

  74. intosi

    The table cloth we used

  75. intosi

    fippo: yeah, him :)

  76. intosi

    http://photo.ik.nu/v/fosdem/fosdem_2004/jabber3.jpg.html

  77. ralphm

    I can always order a flag, but as I remember, the space we will be in, is not very helpful in hanging things on walls. But I suppose a table cloth could be done, still.

  78. fippo

    ah, i remember making plan for stealing that flag :-)

  79. dwd

    How about this for the basis of a second t-shirt: http://www.google.co.uk/imgres?client=ubuntu-browser&biw=1200&bih=1509&tbm=isch&tbnid=QO6_PBV7zTImmM:&imgrefurl=http://fortmissoulamuseum.org/WWII/detail.php%3Fid%3D449&docid=IX1zJvAWtJMX3M&imgurl=http://www.fortmissoulamuseum.org/WWII/images/posters/1986.004.439.jpg&w=800&h=1120&ei=lBawUuXyGsOThQeWwYDABg&zoom=1&ved=1t:3588,r:63,s:0,i:278&iact=rc&page=2&tbnh=192&tbnw=137&start=49&ndsp=58&tx=67&ty=81

  80. intosi

    http://photo.ik.nu/v/fosdem/fosdem_2004/jabber1.jpg.html

  81. intosi

    Look at the size of that monitor...

  82. bear

    I have one of those in the basement

  83. bear

    ugh, I really should send it to a recycle center

  84. ralphm

    I am looking at the site I ordered the flag from last time.

  85. intosi

    This one was mine, I gave it away together with the SGI that used to be attached to it.

  86. ralphm

    They also do custom fatboys

  87. Zash

    That sounds like the bomb

  88. intosi

    That's very loungy.

  89. bear

    that sounds like a great sponsor thingy

  90. bear should really go to bed now

  91. bear

    my word selection is regressing

  92. ralphm

    How many colors?

  93. dwd

    Depends what's on it. What's the cost?

  94. ralphm

    (the Jabber logo has 2, the XMPP logo has 5 (+ shades), Real Time logo has 2. Add 1 for text)

  95. ralphm

    dwd: I don't know, that's why I need to know the number of colors. They don't list prices on the site)

  96. Kev

    I think we should probably just give up on 'Jabber' at this point :/

  97. ralphm

    Kev: it shows you were not present at the summit

  98. Kev

    You think being at the summit would persuade me that we shouldn't?

  99. ralphm

    Well, at the very least there was no consensus against reusing Jabber

  100. Kev

    The trademark's now owned by a company using it to refer to a competing system. I don't see how it's good to keep using it.

  101. ralphm

    I don't see how that matters in practice.

  102. Kev

    "Buyer" confusion.

  103. ralphm

    The Jabber name is still widely regarded to refer to what we do, and they only ones that are going to be confused are the Cisco Marketing people

  104. Kev

    I don't think that's true.

  105. dwd

    Actually the buyer confusion is very much on our side. End users particularly are still very much using the Jabber term for XMPP based IM solutions.

  106. ralphm

    who will ask legal and then find out that we can do what we want with the trademark

  107. Kev

    XMPP (the protocol, not the name) actually has a reasonable amount of penetration, and if we say "You should call it Jabber", the people who want it say "Buy us a Jabber system please", and the purchasers then buy "Cisco Jabber", this is not a good thing for us.

  108. Kev

    ralphm: It's not a question of being able to do what we want with it, it's whether using it is helpful.

  109. dwd

    Kev, XMPP has penetration in terms of technologists and developers.

  110. Kev

    dwd: Yes. So the end users say "Get us a Jabber system", and procurement buy a Cisco Jabber system.

  111. dwd

    Kev, Jabber has penetration as a consumer-grade network.

  112. fippo

    and jabber has penetration in terms of CIOs

  113. fippo

    bear: I think it would help to mention IOT in the announcement as well

  114. bear

    fippo - post that as a reply so i remember - i'm going to go find my bed and crawl into it

  115. bear waves

  116. Kev

    bear: GN.

  117. intosi

    nn

  118. emcho

    heya

  119. ralphm

    emcho: hey

  120. ralphm

    emcho: did you guys get a stand at FOSDEM as well?

  121. emcho

    yes got it

  122. emcho

    and a lightning talk as well

  123. ralphm

    awesome

  124. emcho

    two tables

  125. intosi

    emcho: good news!

  126. emcho

    right!

  127. emcho

    seems like we'll be able to rebuild last year's RTL

  128. intosi

    If we include the right bytes, it will be LTR

  129. emcho

    or change it of course

  130. emcho

    maybe this year we could do it a bit differently actually

  131. emcho

    last year the loungy area was kind of barred by the tables

  132. emcho

    so it wasn't evident that it was free access

  133. emcho

    (or maybe that was the intention?)

  134. emcho

    so maybe this year we could have the tables at one side and the loungy area at the other

  135. ralphm

    emcho: well, one of the problems is that the area is also a passthrough for people that need to use the elevator

  136. ralphm

    (like weelchairs)

  137. ralphm

    wheel

  138. emcho

    yeah sure, but we wouldn't block it. laste year had this: [wall][--emptyspace--][tables][lounge] what we could try is this: [wall][tables][--emptyspace--][lounge]

  139. intosi

    There's not a lot of wall usable for that. There's the exit of the lecture hall as well.

  140. emcho

    well we could experiment. we are certainly OK with last year's arrangement

  141. emcho

    we could also reverse the tables so that the XSF is seen before jitsi this time

  142. fippo

    we can also stream the xsf table to the jitsi table ,-)

  143. dwd

    Don't cross the streams.

  144. dwd

    Or was that something else?

  145. intosi

    dwd: no, that's for this.

  146. ralphm

    intosi: as far as I remember, that exit should not be used during FOSDEM and we might put a sign to that effect on the inside

  147. dwd

    Rough design of my "Enemy Listening" concept to the list.

  148. dwd

    Nobody has any comments on t-shirt designs? That's got to be a first.

  149. Zash

    Lunch coma

  150. dwd

    The one I'm parodying is here: http://www.fortmissoulamuseum.org/WWII/images/posters/1986.004.439.jpg

  151. dwd

    Ooooh. That thumbnails with Gajim and the right plugins. Purr-tee!

  152. Zash

    http://pics.zash.se/531867ea.jpeg

  153. Zash

    Nice, IP address leakage

  154. Zash

    Mr Dave Cridland

  155. dwd

    Well, yes.

  156. dwd

    So, can't decide between "Encrypt you talk" and "Encrypt your speech". Maybe even "Encrypt for Freedom". Also, I don't like "Don't use silos", I think it's dull.

  157. dwd

    "Secure your server", maybe?

  158. intosi

    Secure your server would be better.

  159. intosi

    Or Encrypt your s2s

  160. intosi

    or comms instead of s2s

  161. Zash

    Secure Your Server sounds pretty good

  162. dwd

    How about that, then?

  163. MattJ

    "I have seen the enemy, and he is us. Secure your server!"

  164. emcho

    "Winter is coming!"

  165. ralphm

    "Encrypt your jabber" would bring out the original meaning of the word :-D

  166. dwd

    Usually, any t-shirt discussions spawn an endless and depressing bikeshed discussion. This year, everyone seems scarily quiet.

  167. Zash

    The calm before the storm?

  168. ralphm

    I blame it on the US being asleep still

  169. dwd

    Ah, they may all be in the STOX interim, I suppose.

  170. dwd

    I want a better word than "encrypt". I'm tempted to use "Encipher", just for the period.

  171. dwd

    What about "Keep that Jabber secret"?

  172. stpeter is indeed in the STOX interim conference call

  173. fippo

    stpeter: you're in a loop ;-)

  174. dwd

    What sort of numbers of t-shirts do we want this year, BTW?

  175. Zash

    Integer numbers.

  176. dwd

    Sounds rational.

  177. Zash

    Naturally

  178. ralphm

    Get real!

  179. MattJ

    Considering we don't have any actual number to discuss yet, doesn't that make it imaginary?

  180. dwd

    I can't remember how many we got last time I rodered them, which doesn't help.

  181. MattJ

    This is the most productive room I'm in

  182. ralphm

    dwd: that's making things complex

  183. fippo

    stpeter: foundation bug is already noted in http://wiki.xmpp.org/web/User:Fippo#XEP_0176

  184. ralphm

    dwd: what about "Jabber in code"?

  185. fippo

    quick poll: you're allowed to send an <iq/> to a bare jid (even a jingle session-initiate), right?

  186. ralphm

    yes

  187. MattJ

    Sure

  188. ralphm

    but a server must reply on the account's behalf

  189. MattJ

    Right

  190. Lance

    it probably won't do what you want, but you can

  191. fippo

    right. or a stox pstn gateway

  192. Kev

    But if you want servers to handle jingle for you, it's fine.

  193. fippo

    ah, we'll have to discuss that on the stox list

  194. stpeter

    fippo: thanks -- it would indeed be good to fix the bugs in those specs

  195. fippo

    stpeter: yeah... if I only had more time :-/

  196. stpeter

    fippo: yeah, I hear you!

  197. Kev

    Agendawriting time for Council - fippo, are your updated specs ready to go in the inbox?

  198. stpeter

    Kev: I received your email, will reply shortly

  199. Kev

    stpeter: No rush.

  200. fippo

    kev: yeah, i think it's just the html in the inbox that needs to be updated

  201. fippo

    stpeter: heh, I managed to do a thourough review of stox-media in the last 90 minutes at least :-)

  202. stpeter

    :P

  203. stpeter

    brb

  204. Kev

    fippo: Do you have home-rendered versions anywhere?

  205. Kev

    If it's already checked into Git. Saves Peter publishing again.

  206. fippo

    kev: inbox doesn't seem to contain any .html -- https://github.com/fippo/customxeps/tree/gh-pages/extensions has html, too

  207. Kev

    https://github.com/fippo/customxeps/blob/gh-pages/extensions/jingle-sources.html and https://github.com/fippo/customxeps/blob/gh-pages/extensions/jingle-grouping.html ?

  208. fippo

    yes

  209. Kev

    Urgh.

  210. Lance

    http://fippo.github.io/customxeps/extensions/jingle-sources.html

  211. Kev

    https://raw.github.com/fippo/customxeps/gh-pages/extensions/jingle-sources.html doesn't work :(

  212. Lance

    http://fippo.github.io/customxeps/extensions/jingle-grouping.html

  213. Kev

    Ah, ta.

  214. Kev

    Lance: Nothing to do with peptzo, right?

  215. Lance

    No, I haven't had time to write a XEP-80 update proposal

  216. Lance

    still not sure which approach is better

  217. Zash

    Lance: Update with what?

  218. Lance

    Adding current time zone offset

  219. Zash

    Ah

  220. Lance

    I had a proposal to just add that in PEP, but there were comments that it would fit better in GeoLoc

  221. dwd

    I think it does fit there, but logistically it might be easier to split it off.

  222. fippo

    bear: can you bring the sign from http://www.flickr.com/photos/andyet-photos/10370068076/ along, too? :-)

  223. fippo

    http://www.ucstrategies.com/unified-communications-expert-views/business-to-business-uc-collaboration.aspx -- *sigh*

  224. fippo

    "For example, company A, which requires XMPP over TLS connection, can still connect to company B which uses XMPP over TCP with dial-back."

  225. fippo

    that annoys me enough to register even

  226. bear

    do we have numbers and cost info from the last tshirt purchase? I'm asking if &yet can help with some of this and they will need a ballpark figure

  227. stpeter

    bear: I have that information, but it's at the Cisco office and I'm working at home today

  228. bear

    no worries - i'm just gathering data

  229. stpeter

    hmm

  230. stpeter

    reading http://xmpp.org/about-xmpp/xsf/xsf-bylaws/ Section 8.3 (on "Work Teams"), I conclude that we need to actually establish the UPnP Forum liaison team, with a charter and all, so we might be putting the cart before the horse to ask for volunteers at this time

  231. stpeter

    I'll post to the members@ list about it

  232. fippo

    stpeter: did we do that for the jingle work team?

  233. fippo

    (even though that ended up in a different way :-)

  234. stpeter

    not really, so that team is null and void! ;-)

  235. fippo

    poor dwd

  236. stpeter

    message sent to the list

  237. fippo

    the upnp guys are in portland?

  238. fippo

    (well, depending on the definition of "guys" obviously)

  239. MattJ

    Was UPnP invented in the 90s by any chance?

  240. Zash

    The one that's based on SOAP over HTTP over UDP?

  241. MattJ

    Yes

  242. stpeter

    well, they are all over the world -- I don't think they are "in" any specific place

  243. ralphm

    not just the world, universal!

  244. stpeter

    heehee

  245. ralphm

    but yeah, a consortium

  246. ralphm

    I know people from Philips working on it, while I was there in 2003

  247. stpeter

    maybe the XSF could be located at the geographic center of all its members -- probably somewhere over the Atlantic Ocean :-)

  248. MattJ

    :)

  249. Zash

    Or under

  250. stpeter

    some would say we're all wet, so sure

  251. ralphm

    good old, design by committee, everyone getting their exceptions and/or IP in

  252. stpeter

    yep, most SDOs are like that, it seems

  253. stpeter

    yay, got down below 9000 messages in my inbox ;-)

  254. stpeter

    something to do over the holidays...

  255. waqas

    stpeter: Weren't you at inbox zero at some point?

  256. stpeter

    at some point

  257. stpeter

    it happens once in a while

  258. stpeter

    and then it explodes

  259. ralphm

    do mailinglist posts count?

  260. stpeter

    ralphm: I don't differentiate

  261. ralphm

    stpeter: oh

  262. waqas

    Mailing list posts are auto-labelled and don't go in my inbox. I have most emails auto-labelled.

  263. stpeter

    BTW it seems that Joe Hildebrand might be at FOSDEM for sure, so we could still hold meetings at the Cisco offices even if I'm not able to travel

  264. ralphm

    woot

  265. ralphm

    go hildjj

  266. Zash

    aha

  267. stpeter

    should know soon if that will pan out

  268. Zash

    "might .. for sure" :D

  269. stpeter

    he said so yesterday, but I want to verify

  270. Zash

    "60% of the time, it works every time"

  271. stpeter

    but yes, a poorly constructed sentence, that was

  272. ralphm

    I have 971 unread messages on standards@

  273. ralphm

    maybe I should give up on those

  274. ralphm

    some go back to 2010 :-D

  275. stpeter

    :/

  276. Zash

    "Mark as read" is your friend

  277. bear

    getting info on fosdem is great news - i've been trying to keep the two events raised at work so they know what is coming

  278. ralphm

    I'd love to see a bunch of &yetis

  279. bear

    with two events it would be tough to have a large showing, but each event has it's own sales/tech reasons - i'm gathering data for both to make the pitch

  280. stpeter nods

  281. stpeter

    thanks, bear!

  282. stpeter

    bbiaw