XMPP Council - 2010-09-20

  1. stpeter


  2. Kev


  3. stpeter

    how goes it?

  4. Kev

    43minutes by my watch :)

  5. stpeter

    time check verified, sir!

  6. Kev

    I've actually read the protoXEPs in advance, it must be a Monday :)

  7. Fritzy


  8. Kev

    stpeter: I gave waqas r/o access to the repo, btw, when he asked earlier. Said he didn't need r/w yet.

  9. stpeter


  10. stpeter


  11. Tobias

    what's r/o?

  12. Kev


  13. Tobias

    ahh :)

  14. MattJ

    Doesn't everyone have read access?

  15. Kev

    Not through ssh.

  16. Kev

    And we've not set up a public mirror yet afaik.

  17. Tobias

    Kev: gitosis only manages access to the repo, right?

  18. Kev


  19. Kev

    Why or what were you wondering about?

  20. Tobias

    since we seem to have no git savvy email post commit hook notification expert around i'm making myself one :)

  21. Kev

    Does such a thing not exist already?

  22. Tobias

    it does

  23. Tobias

    it just needs to be activated by someone :)

  24. Tobias

    k..i wonder if that work

  25. Tobias


  26. stpeter

    of the Council members, I see Ralph and Remko online, with Matthew being awat

  27. stpeter

    away even

  28. Fritzy

    I'm here too

  29. Kev

    Yep, got 15mins though.

  30. stpeter

    just noting :)

  31. stpeter wanders off for tea

  32. ralphm slowly gets back into action after a well-deserved-but-way-too-short holiday

  33. Kev

    Mine was a week.

  34. Kev

    Well, 4 days away.

  35. ralphm

    yeah, mine was 7 workingdays

  36. ralphm

    including today

  37. ralphm

    but we had a colo outage over the weekend

  38. ralphm


  39. MattJ is back

  40. MattJ

    Timed dinner just right :)

  41. stpeter


  42. Kev

    Just enough time for me to brb before 7.

  43. Kev

    And we're on.

  44. MattJ

    Has anyone poked Remko?

  45. Kev

    I've reminded him at 14 minutes and 0 minutes.

  46. MattJ

    Fair enough

  47. Kev

    I expect he'll be along, he acked the 14minute reminder.

  48. remko


  49. Kev


  50. MattJ

    Yay :)

  51. Kev

    1) Roll call.

  52. Kev

    Sausage bap.

  53. Fritzy


  54. Kev

    Also: all here.

  55. Fritzy

    <presence />

  56. Kev

    2) Agenda bashing.

  57. ralphm


  58. stpeter wanders back in

  59. MattJ


  60. Fritzy

    current agenda is ok

  61. remko


  62. Kev

    3) ProtoXEP - Spim Markers and Reports: http://xmpp.org/extensions/inbox/spim.html

  63. Kev

    Accept as a XEP?

  64. Kev

    I had various comments to make about this, but nothing to stop us throwing it up as Experimental.

  65. Fritzy

    I have a lot of problems with it

  66. ralphm

    oh, the evil bit

  67. MattJ waits to hear Fritzy's problems

  68. ralphm

    I thought we already had a spec for that

  69. Kev

    ralphm: Yes.

  70. Fritzy

    I'm going to vote -1 and email to the list my comments

  71. Kev

    Ok - this is substantial stuff that can't be sorted out while it's on the vine, then?

  72. Fritzy

    Well, sure -- let me go stream of thought

  73. ralphm


  74. stpeter


  75. Kev

    I'd rather we had something we could put in the minutes as a reason for rejecting it :)

  76. ralphm

    I see many things wrong with this spec even at a glance

  77. Fritzy

    I don't like the filters extending the presence stanza

  78. ralphm

    like abusing presence for pubsub

  79. MattJ

    ralphm, eh?

  80. ralphm

    Fritzy: fools seldom differ

  81. Fritzy


  82. ralphm

    MattJ: like example 3

  83. ralphm

    this is clearly a horrible way to do things

  84. MattJ

    ralphm, I don't see why... it's not abusing presence for pubsub

  85. MattJ

    Those tags could be on a message stanza too

  86. Fritzy

    Also, I don't see how a complaint actually associates itself with what it is complaining about -- maybe I'm missing something here?

  87. ralphm

    it is, it is soliciting a subscription for stuff through presence

  88. MattJ

    Fritzy, the "key" attribute

  89. stpeter

    OT hmph, did we not add this meeting to the calendar?

  90. MattJ

    stpeter, if you didn't and I didn't then I guess not

  91. stpeter


  92. Fritzy

    MattJ: the key is associated with the subscription to the filter -- not the stanza it is complaining about

  93. Fritzy

    MattJ: or am I really missing something big here?

  94. MattJ

    ralphm, no, you're missing it...

  95. MattJ

    ralphm, that's a normal subscription request from one user to another user

  96. MattJ

    The <report> elements are to tell the recipient where to report spim to

  97. waqas

    stpeter: I'd also request notifications posted on identi.ca for council meetings. I always miss the meetings.

  98. MattJ

    They are inserted by the filters as the stanza passes through

  99. ralphm

    MattJ: I understand that

  100. Kev

    waqas: I'm not opposed to that. Although I'd rather I didn't have to remember it.

  101. MattJ

    Fritzy, subscription to the filter?

  102. Kev

    Something for AOB.

  103. ralphm


  104. Fritzy

    I don't see what the complaint is for since it only contains to the key to the filter subscription.

  105. MattJ

    What filter subscription?

  106. Fritzy

    example 3

  107. dwd

    [log URI?]

  108. MattJ

    Fritzy, Read what I said to ralphm above

  109. MattJ

    You and he need to read the XEP again I suspect :)

  110. ralphm

    I believe we once figured out a way to discover special addresses at servers

  111. ralphm

    e.g. for reaching admins and what not

  112. Fritzy


  113. Fritzy


  114. Fritzy

    I get that now

  115. ralphm

    I think that should cover it

  116. MattJ

    Fritzy, to be clear that stanza is just an example, it could also be a <message>

  117. Fritzy

    so you're complaining about a specific jid

  118. MattJ

    Obviously if 2 *council members* don't understand this then the XEP needs clarifying :)

  119. Kev

    For what it's worth, I didn't think this was anything like as bad as you two do.

  120. Tobias

    MattJ: or the xep needs to wait for a new council ;)

  121. MattJ

    No, I like it... it's simple, and fits well with the other XEPs we have

  122. Fritzy

    MattJ: or wait, you're complaining about the stanza that is marked with a key.

  123. MattJ

    Fritzy, yes, now you're getting it :)

  124. ralphm

    MattJ: maybe you are right. I am still unsure about the usefulness.

  125. Fritzy

    sounds useful to me... if a bit noisy

  126. MattJ

    For example, reports could lower entity reputation, they could automatically add to block lists, etc.

  127. Kev

    I'll agree with it being noisy, but I think you need that if you want this level of control.

  128. MattJ

    Fritzy, if you read further it says to only include these tags in certain stanzas

  129. Fritzy

    right, I see that.

  130. MattJ

    Like initial subscription requests, or messages from people not in your roster

  131. MattJ

    So yes, it's "noisy", but only where it has to be

  132. Fritzy

    There might also be a need to optionally have a form for complaints from specific filters to make it more useful.

  133. MattJ

    The alternative would be to drop per-stanza reporting, but that has issues

  134. Fritzy

    so you could explain what you're complaining about

  135. Fritzy

    or suggest an action

  136. ralphm

    I think the marking bit is ok, but I'm not very sure about soliciting reports on individual stanzas

  137. MattJ

    Yes, I think Dave may have suggested something like that on the list

  138. Kev

    Ok, so, cutting this short.

  139. Kev

    Are Fritzy and/or Ralph still -1?

  140. stpeter

    using <presence type='subscribe'/> seems odd for this purpose...

  141. MattJ

    stpeter, not you too... :)

  142. Kev

    I picked a good day to take time out to read the proposals at length, I think :)

  143. MattJ

    stpeter, that is a normal subscription request from one user to another user

  144. MattJ

    Kev, likewise :)

  145. stpeter

    anyway I can post to the list about it

  146. Kev

    So, the proposal clearly needs clarification.

  147. ralphm

    MattJ: the problem is not in the fact that it is presence, it is the fact that every stanza is littered with lists of filters that you could report a stanza to as 'spim'.

  148. MattJ

    stpeter, the "filters" inject these tags so that the recipient can know where to report the stanza to

  149. Fritzy

    stpeter: it isn't using -- it's just marking that to show how to complain about

  150. dwd

    FWIW, my general thought was that it's an interesting start, we need something like this, and this is a solidly documented proposal.

  151. Kev

    The question is if Fritzy and Ralph are still vetoing it.

  152. MattJ

    dwd, I agree

  153. Kev

    There are much less well-written protoXEPs.

  154. MattJ is +1

  155. ralphm

    dwd: true

  156. Kev

    Several are sitting in my outbox.

  157. dwd

    The details could be a lot better, but it's a step in the right direction and a solid base.

  158. ralphm

    dwd: would you implement something like this?

  159. stpeter

    however, I am almost always in favor of publication to get discussion going, put the spec into source control, etc.

  160. ralphm

    MattJ: ?

  161. Kev

    ralphm: I'd strongly consider it (client)

  162. MattJ

    ralphm, yes?

  163. stpeter

    not that I have vote at the moment :)

  164. Kev

    Ok, this item is going on much too long.

  165. ralphm

    I am trying to get a feel of the demand for something like this

  166. Kev

    Fritzy: Are you still -1?

  167. Kev

    ralphm: Are you still -1?

  168. MattJ

    ralphm, I'd implement it

  169. MattJ

    For sure

  170. Fritzy

    I'm no longer vetoing it for experimental, but I think it warrants some cleanup and discussion.

  171. dwd

    I suspect some of our partners may be interested. I suspect we might be too. With some evolution, obviously.

  172. Kev

    Spam filtering is something that would really interest me to implement server-side.

  173. ralphm

    I'm 0

  174. dwd

    Fritzy, Oh, for sure.

  175. MattJ

    We've accepted far worse protoXEPs... :)

  176. Kev

    Appeals to my past life as a labrat.

  177. Kev

    Ok, excellent.

  178. MattJ


  179. dwd

    Kev, Just *don't* mention it to David...

  180. Kev

    The XEP Editor can publish, and we'll free-for-all on the standards list.

  181. Fritzy

    yeah, so when will this be in M-link?

  182. Fritzy


  183. Kev

    dwd: Could get interesting.

  184. Kev

    4) ProtoXEP - Bidirectional Server-to-Server Connections. http://xmpp.org/extensions/inbox/bidi.html

  185. Kev


  186. MattJ


  187. ralphm


  188. Kev

    I object to the formatting of example 3 breaking the XML highlighter, but am in favour.

  189. MattJ

    Only time has stopped me implementing this

  190. Kev

    I've already complained to one of the authors about that :)

  191. ralphm

    dwd: I'm curious about idleness and disconnects

  192. dwd

    This is Fippo's write-up of my suggestion of resolving Justin's issue as raised in 2003 or something.

  193. Fritzy

    Definitely +1

  194. Fritzy

    we need to get somethign out there that solves this.

  195. Kev


  196. remko


  197. ralphm

    dwd: did you think about that yet?

  198. dwd

    ralphm, I believe that's unaffected. Indeed, I think it's much easier to manage idleness and 198 and things with bidi.

  199. Kev

    5) New term applications reminder.

  200. dwd

    ralphm, For a start, doing ping-checks across S2S is a PITA.

  201. MattJ

    Reminded, thanks :)

  202. dwd

    ralphm, (without bidi)

  203. stpeter notices that Kev is in 30-minute-meeting mode

  204. Kev

    Just a reminder to anyone thinking of reapplying or applying that the application period will close in a touch over a week.

  205. remko


  206. Kev

    stpeter: Kev is *always* in 30min meeting mode.

  207. Kev

    Or ideall 20.

  208. MattJ

    dwd, it's not when you have send_iq() :)

  209. Kev

    6) Date of next meeting.

  210. Kev

    Fritzy: Mondays are difficult for you - when is less difficult?

  211. dwd

    MattJ, No, because the response still comes back over a different socket.

  212. MattJ

    dwd, doesn't matter... it means the one you sent on is fine

  213. Fritzy

    Tues-Fri any other time is less difficult

  214. Kev

    Fritzy: Any *other* time?

  215. Kev

    Implying this time is bad any day?

  216. dwd

    MattJ, Track that over a cluster...

  217. MattJ

    dwd, I shall do some day :)

  218. Fritzy

    Monday afternoon or Tues-Fri any time.

  219. ralphm

    Fritzy: UTC times, please

  220. Kev

    Later than this is a nuisance for me, and I suspect other .eu people, although I could manage an hour later ok I think.

  221. Fritzy

    +2 hrs than this or Tues-Fri

  222. Fritzy

    I'm fine with next Monday same time though

  223. Fritzy

    just as a tendency

  224. ralphm


  225. Fritzy

    I often have meetings on Monday morning

  226. Kev


  227. Fritzy

    and other catch-up

  228. stpeter

    is it worth working this out before the new Council is elected?

  229. Kev

    Well, does anyone have difficulty with Tuesday, at the same time?

  230. ralphm

    stpeter: my thought

  231. Fritzy

    stpeter: yeah, I'm fine with working this out in the next council if I'm still on

  232. ralphm

    lets just finish the term with this slot

  233. Kev

    stpeter: There are enough weeks left that if 20% of Council can't make the meetings, it's probably worth sorting IMO.

  234. stpeter

    (if there is a new Council considering that http://wiki.xmpp.org/web/Board_and_Council_Elections_2010 is empty!)

  235. ralphm


  236. MattJ


  237. ralphm copy/pastes

  238. Fritzy


  239. Kev

    stpeter: My app's written, but not linked.

  240. stpeter

    darn, I was hoping to be elected the Council-of-One :)

  241. Fritzy

    let's just do Monday next week for now

  242. Fritzy

    same time same bat-channel

  243. Kev


  244. remko


  245. Kev

    Any other business?

  246. ralphm

    stpeter: you're running?

  247. Kev

    Calendaring and microblogs from waqas.

  248. Fritzy


  249. ralphm


  250. ralphm

    application for fosdem

  251. Kev


  252. Kev

    So, Matt - are you still (generally) doing the calendar entries?

  253. ralphm

    we want the full shebang again?

  254. stpeter

    ralphm: I was going to if no one else did, that way I could dispense with all this democratic-process nonsense :)

  255. Kev

    ralphm: Let's do the other first.

  256. ralphm

    Kev: ok

  257. MattJ

    Kev, I was, then stpeter was... that got me out of the habit :)

  258. MattJ

    I can start reminding myself again

  259. Kev


  260. Kev

    Who wants to announce on identi.ca?

  261. ralphm

    wait what?

  262. Kev

    Is there an XSF account?

  263. MattJ

    stpeter is busy enough that we should ban him from trivial things like editing calendars

  264. Kev

    Do we want to do this?

  265. stpeter

    if it's in the calendar, people will tend to remember it

  266. MattJ

    There is an XSF account

  267. stpeter

    Kev: there is

  268. Fritzy

    I believe there is an XSF account on identi.ca

  269. ralphm

    do what?

  270. Kev

    Announce meetings on identi.ca - it was waqas's suggestion earlier.

  271. ralphm


  272. ralphm


  273. ralphm


  274. Kev

    I'm happy to delay such changes to process until the new Council take over.

  275. stpeter

    attendance goes up if we announce it 15 minutes before the meeting

  276. Fritzy

    xmpp uris!

  277. ralphm

    Kev: nah

  278. Kev

    But we can start doing it now

  279. Kev

    who wants to do it?

  280. ralphm

    Kev: you!

  281. stpeter

    I find myself not paying attention to identi.ca anymore :(

  282. Kev

    I guess the Chair can do it, but he's likely to forget.

  283. MattJ

    How about... I take it on, but I'll write a bot

  284. Kev

    stpeter: I've disabled the XMPP bot now, too distracting.

  285. ralphm

    MattJ: haha

  286. stpeter

    +1 to bot

  287. Kev

    MattJ: perfect, ta.

  288. Kev


  289. Kev


  290. Kev

    Ralph :)

  291. ralphm


  292. Kev

    Your 2 minutes start now.

  293. stpeter

    MattJ: poke me if you need the password for the XSF account

  294. ralphm

    it's that time of year again to apply for a devroom and a booth

  295. MattJ

    stpeter, I think I know it, thanks

  296. ralphm

    at FOSDEM

  297. stpeter


  298. ralphm

    5/6 feb 2011

  299. Kev

    ralphm: I'm inclined to say we want the status quo.

  300. ralphm


  301. Kev

    devroom was overflowing last year.

  302. stpeter

    yeah that was fun

  303. ralphm

    Did I do the application this year?

  304. MattJ


  305. ralphm

    I forgot

  306. ralphm

    I can do it this time, again

  307. stpeter

    yes you did

  308. stpeter

    at least, I didn't :)

  309. ralphm


  310. Kev

    I think this is probably Board, rather than Council, mind.

  311. MattJ

    ralphm, you could always ask the assistance of the communications team if you need it :)

  312. stpeter

    Board meeting on Tuesday of this week

  313. stpeter

    we could discuss there

  314. Tobias

    dwd: a little late, just had to add an A record, but here are the logs :P http://logs.xmpp.org/muc_log/muc.xmpp.org/council/100920/

  315. ralphm

    Kev: nah, it has always been done by me, basically

  316. stpeter


  317. stpeter

    it's in the calendar, too

  318. ralphm

    with no particular strong binding to the xsf

  319. Fritzy

    Can bidi be extended to include dwd's multi-domain per s2s connection with signatures?

  320. Tobias set the topic to

    XMPP Council Room | http://wiki.xmpp.org/web/Radar | http://logs.xmpp.org/muc_log/muc.xmpp.org/council/

  321. stpeter

    ralphm: right

  322. ralphm

    although we always went as such

  323. stpeter

    ralphm: and I'm fine with that!

  324. Tobias set the topic to

    XMPP Council Room | http://wiki.xmpp.org/web/Radaras

  325. MattJ

    Tobias, sensible URLs for the logs? You deserve a bonus :)

  326. MattJ

    Tobias, I couldn't get that working

  327. Tobias

    MattJ: i didn't do nothing :)

  328. Tobias

    just had the record added :D

  329. ralphm

    just more of a reminder, and I'm wondering if we plan to do a summit again

  330. Kev

    ralphm: Well, if we get a room, I'm happy.

  331. Tobias

    MattJ: config and all was already there

  332. MattJ

    We're doing a summit if we can get somewhere with windows, I think

  333. Kev

    I'd hope we'd do a summit again, although that needs (probably Board) volunteers to arrange.

  334. ralphm

    MattJ: +1

  335. Kev

    Right, windows would be nice. Internets even nicer.

  336. MattJ

    We've been underground far too long :)

  337. stpeter

    I've heard that I can get a free meeting room at a Cisco location near the airport (not in the center)

  338. Kev

    stpeter: I think that's worth strongly considering.

  339. stpeter

    but I need to ask and get that organized

  340. stpeter

    to see if it's doable

  341. Kev

    Could someone ask Board to discuss this tomorrow, please?

  342. stpeter


  343. Tobias

    MattJ: but i guess it would be nice to eliminate the the mud_log/muc.xmpp.org parts..it blows the whole thing up and there aren't any other muc components running

  344. Kev


  345. MattJ

    Tobias, +1

  346. stpeter

    Board meetings are open, BTW

  347. Kev

    I think we're out of agenda items then, unless there's AOAOB.

  348. MattJ

    I'm done

  349. Kev

    stpeter: I'll be trying to remember to attend.

  350. Kev

    I'll knock out the minutes tomorrow morning, probably.

  351. ralphm hands the gavel

  352. Kev

    Ok, we're done then

  353. Kev bangs the gavel.

  354. Kev

    Thanks all.

  355. MattJ


  356. ralphm


  357. Fritzy

    Kev/stpeter: has there been any progress made on multi-domain and single cert + signatures per s2s connection?

  358. remko


  359. stpeter

    Kev: added to http://typewith.me/EyJg4G3XSr

  360. ralphm

    oh, fosdem also requests ideas for main track speakers

  361. Kev

    stpeter: ta.

  362. Fritzy

    aka: the gtalk problem

  363. ralphm

    not something I've done, but if anyone wants to speak...

  364. stpeter

    Fritzy: see http://tools.ietf.org/html/draft-barnes-xmpp-dna-00

  365. Fritzy

    stpeter: thanks

  366. stpeter

    Fritzy: there is also http://tools.ietf.org/html/draft-ietf-xmpp-dna-00 (expired), but the doc from Richard Barnes incorporates discussion at the meeting in Maastricht in late July

  367. Fritzy


  368. MattJ

    ralphm, I'd likely forget to take my coat off ;)

  369. stpeter

    Kev: will you have time to write up minutes for this meeting? any other volunteers?

  370. Kev

    Isode are fairly kind people, I'll do it tomorrow morning.

  371. Kev

    Unless someone else has a burning desire to get involved!

  372. stpeter


  373. stpeter

    I might find time to do it this evening (Mountain Time)

  374. stpeter

    but not before then

  375. stpeter


  376. Fritzy

    stpeter: thanks!

  377. Kev

    stpeter: If you want to beat me to it, feel free.

  378. Tobias

    k..would be handy if one of those *admin folk* would add this to the topic line: http://logs.xmpp.org/council

  379. MattJ set the topic to

    XMPP Council Room | http://wiki.xmpp.org/web/Radar | Room logs: http://logs.xmpp.org/council

  380. MattJ

    It's not happy with that... the URLs it directs to are wrong

  381. Tobias

    works for me

  382. Kev

    Not for me.

  383. Tobias

    http://logs.xmpp.org/100714/ <-- this is wrong indeed :)

  384. Kev

    You end up trying http://logs.xmpp.org/100920/council/council/council/council/council/council/

  385. Kev

    Before deciding that no matter how many times you press it, it won't work.

  386. stpeter


  387. Tobias

    Kev: what did you do to get that?

  388. MattJ

    I'll probably look at that, the person who wrote the code originally has gone AWOL :)

  389. Kev

    Clicked today's tade, then clicked council

  390. Kev

    then clicked council

  391. Kev

    then clicked council

  392. Kev


  393. ralphm

    FOSDEM this year marks a preference for 'encompassing topics'

  394. ralphm

    shall I suggest related, open protocols as a possible grander theme?

  395. Kev

    Isn't that always our grander theme?

  396. Tobias

    Kev: the link seems to have to have a / at the end

  397. Tobias

    mind changing that in the topic?

  398. ralphm

    Kev: sure, but we've always 'marketed' the room as xmpp specific

  399. Kev

    Ah, I see.

  400. ralphm

    even though our community is clearly broader in interest

  401. Kev

    Well, we could do extensible social stuff.

  402. Tobias set the topic to

    XMPP Council Room | http://wiki.xmpp.org/web/Radar | Room logs: http://logs.xmpp.org/council/

  403. ralphm

    they might then opt to have a bigger room and hook us up with other open protocols people

  404. ralphm

    which I think is nice

  405. ralphm

    (and we do the summit, too)

  406. Kev

    I think our tie to open social stuff is more useful than our tie to generic open protocols.

  407. Kev

    open social protocols works.

  408. ralphm


  409. ralphm

    that'd be the thing

  410. ralphm

    most of the talk on open protocols revolves around this topic anyway

  411. Kev

    Well, they should all be using XMPP, so sure :D

  412. ralphm

    oauth, openid, discovery thingies, etc.

  413. ralphm


  414. Tobias

    Kev: mind adding a / to the log url at top?

  415. ralphm

    application done

  416. MattJ set the topic to

    XMPP Council Room | http://wiki.xmpp.org/web/Radar | Room logs: http://logs.xmpp.org/council/

  417. Tobias

    thanks kev

  418. MattJ


  419. stpeter wanders off to run an errand...

  420. MattJ

    Tobias, without '/' should probably redirect

  421. MattJ

    I'll add that to the tracker

  422. MattJ

    (prosody-modules tracker, that is)

  423. Tobias

    ok :)

  424. Tobias

    since i tried that and failed pretty fast and though i should give up pretty fast too

  425. Tobias


  426. MattJ


  427. Tobias

    MattJ: do you have admin access to the MLs?

  428. Kev

    I do.

  429. MattJ

    No, thankfully

  430. Tobias

    Kev: could you tell me if there's something in xmpp-commit moderation queue?

  431. Kev

    Peter normally manages them, mind.

  432. Tobias

    since i pushed something to the repo and it was supposed to send a mail to there

  433. Kev

    what's the mailing list address?

  434. Kev


  435. Kev

    Gottit, nevermind.

  436. Tobias


  437. Kev

    Now, let's work out what the password is.

  438. Kev

    I don't see any pending mails.

  439. Tobias


  440. Tobias

    i've added the mailinglist = foo stuff to the hook section of the repo config

  441. Tobias

    and enabled the post-receive hook

  442. mlundblad

    was there a council meeting tonight?

  443. remko


  444. Tobias

    remko: btw: did you get your prosody issues sorted out?

  445. remko

    mattj is on it, as always

  446. remko

    it's related to xep-198

  447. Tobias


  448. MattJ

    remko, btw... I found no broken hashes in my contact list

  449. MattJ

    Well, actually I found 2... let me send that email, I'm getting like waqas :)

  450. remko

    you found no broken hashes, but actually 2?

  451. remko

    that doesn't sound like 'no' to me :)

  452. Tobias

    more noish :)

  453. remko

    yes, my contact list is also clean, but the latest adium beta has a bug

  454. remko

    and i suspect jabbim and jabber2jabber as well

  455. Tobias

    latest? the one released yesterday?

  456. remko

    oh darn, was there a release yesterday?

  457. Tobias


  458. Tobias


  459. remko

    ah yes, it was a beta

  460. remko

    actually, i even tried the nightly, same problem

  461. Tobias


  462. remko

    and jabber2jabber uses gloox i'm told

  463. remko

    so that seems to be aligned with mattj's mail

  464. MattJ

    Yes... Spectrum also uses gloox, and it's likely the same issue

  465. MattJ

    since someone found that Spectrum contacts report as invalid also

  466. MattJ

    It generates a correct hash, but doesn't add any features to the disco results when a node is included

  467. remko

    jabber2jabber uses spectrum

  468. remko

    right, adium has a similar problem

  469. remko

    it hashes correctly, but doesn't update the hash if you add some features

  470. MattJ


  471. remko

    that's the price you pay for caching ;-)

  472. remko


  473. remko


  474. remko

    anyway, i'm off, ttyl

  475. MattJ

    Prosody caches it too, but it regenerates for every new feature added/removed :)

  476. MattJ