XSF Discussion - 2019-10-24


  1. pep.

    ralphm, https://github.com/xsf/xeps/pull/846 can this be added to the agenda. It should only be editor land it's a change in the schema but editors prefer to be on the safe side

  2. pep.

    (I couldn't add stuff on the trello board)

  3. ralphm

    Yeah, I don't think this requires a board vote. Please make it so.

  4. MattJ

    ralphm, I probably won't make the meeting later as I'll be travelling, but if I do it'll be mobile-only

  5. Seve

    ralphm, MattJ, I'm unfortunately in the same situation today :(

  6. ralphm

    Me too

  7. Guus

    Nyco and me will hold the fortress!

  8. Daniel

    Can Board follow up on the financial report? Apparently this was discussed at the end of last month (no minutes from that meeting and I was driving at the time) but never acted upon?

  9. Guus

    Daniel yes. It's still on our agenda.

  10. Guus

    from what I recall, we ended up debating if we'd like Peter to provide data from past years.

  11. Guus

    chat log here: https://logs.xmpp.org/xsf/2019-09-26?p=h#2019-09-26-ae8c71a4f222d202

  12. Daniel

    From the looks of it there hasn't been a real conclusion and to my knowledge it hasn't been brought up again at other meetings. (despite 'still being on the agenda') - can I ask for it to be put on the real agenda?

  13. Daniel

    If Board wants my input publishing current data (2018) is fine for now. And if it looks fishy people can ask for more?

  14. Guus

    It did not ever leave the agenda - it has been on my mind every meeting, but we simply didn't get around to doing it. One thing that I noted in the last meeting was that I think it'd be good to find a way to be more efficient in those meetings.

  15. Daniel

    If he really has that stuff on paper publishing all of it seems a bit much. If it were just upload uploading some spreadsheet I'd be with you in asking for all of it

  16. Guus

    Daniel I'm curious why you bring this up. I have no problem with us releasing this information, but I personally have little interest in it (other than that I'd want to prevent us from being regarded as secretive / non-open). What's your motivation?

  17. Daniel

    I brought it up *now* because today is board meeting and I had a minute of spare time to ask for it. It has been on my mind for a bit longer. I (as a scam member) would start to spend some money and I would like to see how much money we have, how much new money is coming in and what things we spend money on in the past. Just to get a grasp on what kind of money I'd be OK asking for

  18. Daniel

    I've also heard rumors that we are not very good at actually collecting money from our sponsors

  19. Daniel

    (sending invoices)

  20. Daniel

    *would like to start spending

  21. Guus

    Daniel for SCAM, there's a yearly budget of 1000 USD that we can spend.

  22. Daniel

    Right. I have however no grasp if this is a fair amount

  23. Daniel

    Like what part of the annual budget is that

  24. Guus

    and yes, we've dropped the ball on doing invoicing / contacting sponsors in the past. That has even been discussed in this room, nothing about that is 'rumor' as far as I know. πŸ™‚

  25. Guus

    Fair questions.

  26. Guus

    Like I said, the financial reporting never was on a backburner, even if we didn't get around to handle it in the last few meetings.

  27. Guus

    as for SCAM's budget - I'm not sure if we can, or should, qualify 'fair'. I'd have to check, but I think we've not spent any of that budget this year

  28. Guus

    (maybe some around the summit/fosdem, but that might also have come from last years budget)

  29. Guus

    so maybe it's more a question of: what do you want to do with the budget?

  30. Guus

    (And if we want to spend more than the budget, we can take that to board)

  31. pep.

    Guus, Daniel and I didn't know about it until not so long ago :p

  32. Guus

    "it" ?

  33. pep.

    The budget

  34. pep.

    SCAM's

  35. Guus

    Ok. Well, there is. πŸ™‚

  36. Guus

    I've mentioned it just now in the SCAM MUC

  37. Daniel

    (discussing this here so other non scam people can see this as well)

  38. Daniel

    Yeah I've known about the scam budget for a couple of months /weeks now. That's fine

  39. Daniel

    I could imagine myself asking scam to pay for sprint venues. We don't always have hacker spaces or something in the cities we want to do sprints in. And/or hackerspaces are not always ideal locations for reasons. Now if I were to ask for rent that can very quickly exceed the budget of 1k. However before I do I just want to know how much money for example 1k rent for 3 days is to the xsf

  40. Daniel

    And then decide if I can justify asking for that

  41. Guus

    fwiw, the SCAM budget was requested as a means to not have to go to board for every expense, which (as you've found) can take a long time. It was not intended as any kind of hard limit that SCAM could spend.

  42. Daniel

    Yeah I see the scam budget paying for day to day items such as merch and drinks at sprints

  43. Guus

    us wanting to spend numbers like that does warrant board involvement, I think.

  44. Daniel

    But not for the entire sprint

  45. Guus

    right

  46. Daniel

    That's fine asking board

  47. Daniel

    I just don't know if it is a reasonable ask

  48. Guus

    but I understand your motivation to see the board financials.

  49. Daniel

    And also even if Board decides people need to be able to understand the decision making

  50. Kev

    I'd think of it in terms of the Summit, which is the most important XSF-arranged event of the year, which we usually try to get sponsorship for all of and the budget comes in at less than that much usually (I think).

  51. Kev

    So I'd have thought there'd need to be a strong argument for why it was valuable to the XSF for spending that sort of amount.

  52. Guus

    It'd be nice to decouple budget from one important event - as such coupling makes it harder for other important events to be developed.

  53. Kev

    My point is that if we try to avoid spending much on the most important event we arrange, spending more on other events would need some significant justification. In my view.

  54. Guus

    Kev, there's an argument to be made that the sprints serve a good purpose - but I agree that for much money to be spend, we need to discuss that further.

  55. pep.

    Also, we can do many more events :)

  56. pep.

    We just don't have any idea if financials would even allow for this

  57. Kev

    They wouldn't, I think. We don't bring in that much from sponsorship, unless things have changed since I last remember.

  58. pep.

    I agree about all what Daniel said above fwiw

  59. pep.

    Kev: the issue is not that you think it would or not

  60. Guus

    I understand that people want to have the numbers to form their own opinion.

  61. Guus

    also, that might be a motivation to more actively attract funds.

  62. pep.

    Yes

  63. pep.

    To both

  64. Guus

    Kev also, I'm not sure if we are trying to 'avoid spending' money on the Summit, other than that we're careful to not overspend / overindulge, as we recognize that we depend greatly on donations of others?

  65. Seve

    To let money out, you want to make sure money will be comming in.

  66. Kev

    We seem to put a lot of emphasis on needing people to sponsor the room, the lunch, the dinner each year.

  67. Kev

    I think it might be hard to justify asking for all that sponsorship for the Summit, if the XSF is giving out significant amounts to run other, less well attended and core, events.

  68. Guus

    Kev I'm seeing that as us resorting to measures as we're doing a poor job of getting 'regular' / year round sponsors.

  69. Kev

    Yes, I agree with that.

  70. Guus

    Kev right, now I see your point

  71. Guus

    and I agree.

  72. Kev

    If we had buckets of cash, arranging more 'minor' events would seem like a good use of it. We just don't.

  73. Guus

    Opening the financials might allow others to come to the same conclusion.

  74. Guus

    (I almost typed 'collusion' there, I'm following the US news to closely)

  75. pep.

    Kev: even if that might be true, that's not an argument against revealing financials

  76. Kev

    No, which is why I didn't understand why Board were putting roadblocks in the way of doing so.

  77. Guus

    I don't think he ever made the argument to not reveal financials Pep?

  78. Guus

    I don't think board is putting in roadblocks, other than that they're slow to come to a conclusion

  79. pep.

    Guus: ah ok that's how I understood it

  80. Kev

    I thought "Oh, we can't just release them from now on, we have to keep them hidden until we can release a full history" was where it was.

  81. Kev

    Which I think is pointless.

  82. Guus

    we're basically debating: "should we release financials for the current year only, or also venture further down in the financial history?"

  83. Guus

    None in board argued to keep things hidden

  84. pep.

    I'd like to have the full history in the long run, but I'm happy with the current year as a start, better than nothing and that can already help

  85. Guus

    board being ineffective to come to a decision on wether to release current year only, or more history might have perceived as such. But, to be fair to board, I think they only discussed it once, in a meeting that was already running over time.

  86. Daniel

    we seem to have at least 3 platinum sponsors? (given they have 'a page on the xsf') site. that's 30k

  87. Daniel

    that doesn’t seem like we are super tight on cash

  88. Daniel

    unless i don’t understand how expensive the summit is

  89. Daniel

    which is why i would like to the the numbers at least for one year

  90. Guus

    more reasons to disclose those financials.

  91. Daniel

    i don’t distrust people or anything. that's why for me 2018 would be fine

  92. Daniel

    because i reckon all years will be similar

  93. Guus

    I'll try to push board to address this in todays meeting, but as you might have read, at least three members are, at best, attending from mobile devices.

  94. Daniel

    also we have another 2-4k coming in from gsco?

  95. Guus

    Unsure - I don't wnat to speculate.

  96. Guus

    instead, I'll try to facilitate board coming to a conclusion on the publication of financials.

  97. Daniel

    > Unsure - I don't wnat to speculate. Of course. Me neither. But that's what people will do if they can do quick math on one hand with the sponsors that are visible on the page and on the other hand have Kev saying that we don't even have enough money to pay for summit. But yes thank you Guus for following up with board on that

  98. Guus

    I think I have not disagreed with anyone here, other than that i don't believe that board is putting up hurdles for making financials public, other than that they're slow to come to a conclusion on this.

  99. Guus

    (Disclaimer for the log files: I currently serve on the Board)

  100. Kev

    Ok, I'm sorry if I was being unfair with the barriers comment.

  101. Kev

    It seemed to me there was a trivial decision to make (release for now on) that could be +1d in seconds, and then a more complicated second question that didn't need to block the first of asking Peter to reconstruct past records.

  102. Guus

    Kev, I think board didn't do an efficient job in discussing the topic, which bogged down everything. We should simply kick it in gear again, and finish the one discussion that we had, be done with it.

  103. Guus

    And I can understand how inactivity is easily misjudged as 'putting up hurdles'

  104. edhelas

    https://www.indeed.com/viewjob?jk=113dde3cc7ce7284&tk=1dnufmkih40kn801&from=serp&vjs=3

  105. edhelas

    Facebook Portal is built using XMPP ?!

  106. edhelas

    ah no it's in the prefered qualifications

  107. pep.

    Maybe we could ask them officially to disclaim and, oh and also drop a few dollars :-Β°

  108. Guus

    pep. go for it

  109. pep.

    I mean "The XSF"

  110. Guus

    The XSF isn't a magical entity that out of itself produces questions πŸ˜ƒ

  111. pep.

    too bad

  112. Guus

    do you want to draft something, maybe find a lead that we can contact?

  113. pep.

    I have unfortunately very little writing/communications skills (if it wasn't obvious enough will all I write here) :x

  114. pep.

    Unless you're happy with my sentence above

  115. Guus

    Very happy.

  116. pep.

    "Hey facebook. Give us monies"

  117. Guus

    Excellent. Now please find the right person at Facebook to send this to.

  118. pep.

    support@

  119. Guus

    We then have a concrete proposal, that the XSF can debate/improve upon.

  120. pep.

    postmaster@

  121. pep.

    looking for something, but I doubt this kind of information is publicly displayed anyway.

  122. pep.

    Having connections would certainly help a bit here

  123. Guus

    My first feedback would be: "it's my estimation that this proposal has little chance of success. Please improve it before sending it" πŸ˜‰

  124. pep.

    That I could have guessed myself :)

  125. pep.

    Can we not get somebody to do that? As in, we have money, can we not spend money to get more money? That's usually how it works right.

  126. pep.

    We still need to find a point of contact. How many members do we have, they can be useful sometimes, maybe somebody knows something or someone that knows someone else

  127. Guus

    https://xmpp.org/about/xsf/members.html

  128. pep.

    That was rhetorical

  129. lskdjf

    > we've dropped the ball on doing invoicing / contacting sponsors in the past. Guus, I'd be interested in the extend to which this happened. Also, are there plans to still invoice the amount or has that already been done? To my (little) understanding of contracts, those companies would still legally be required to pay and the XSF already did their part (displaying the companies as sponsors)

  130. Guus

    I don't know exactly. Also, I don't think we should pressurize companies in paying things after we slipped up. That's likely to ensure no future sponsorships will happen.

  131. larma

    Guus, if they are not paying, what are the sponsors good for?

  132. Guus

    from what I understand, it's us not invoicing some of them, not them not paying invoices

  133. Guus

    Also, this was quite a while ago, and was addressed.

  134. larma

    So those that were not invoiced in the past are invoiced now? Didn't they ask why there were not invoiced before? Was that an actual board decision to not invoice them delayed or just continued laziness?

  135. Guus

    From what I recall, this involved sponsors where it was ambiguous if they'd silently extended their sponsorship with another year. Since this became known, we've purged the list of sponsors. Those that are still a sponsor, are invoiced. To my knowledge, there's no issue with payment.

  136. Guus

    (I've not actually checked the latter, but I have no indications that something is amiss in that respect)

  137. larma

    So the actual problem wasn't sponsors not being invoiced but sponsors not being removed from the sponsor list after they were no longer a sponsor?

  138. Guus

    a bit of both, probably.

  139. Guus

    If we'd engaged them, they might have remained a sponsor for a few more years. SOme of the sponsors that we removed ceased to exist, so there's no point in following up with them.

  140. Guus

    (as in, company out of business)

  141. larma

    makes sense πŸ™‚

  142. larma

    Guus, looking through archives: ProcessOne is a sponsor since 2015 (excluding May-July 2019), Tigase since end of 2016. Both of them seemingly expressed they want to be a sponsor in 2019. Was any of the two not invoiced for their sponsorship since they began being a sponsor (2015 or 2016 respectively)?

  143. Guus

    I don't know the details, not can I immediately find out.

  144. Seve

    πŸ˜ƒ

  145. Guus

    hello!

  146. nyco

    Board?

  147. Guus

    Board meeting time

  148. Guus

    I'm seeing three

  149. Seve

    πŸ‘†βœŒ

  150. Guus

    this morning, several people warned that they'd be on mobile, at best.

  151. MattJ

    o/

  152. nyco

    I'm on a customer meeting, I'll follow with difficulties

  153. Guus bangs gavel

  154. Guus

    Welcome at this edition of the XSF Board weekly meeting.

  155. Guus

    as usual, the agenda is driven by what's on our Trello board: https://trello.com/b/Dn6IQOu0/board-meetings

  156. nyco

    Previoulsy on "Board Meetings"... :)

  157. Guus

    1. Role call

  158. Seve

    :D

  159. Seve

    Greetings 🎩

  160. Guus

    I've seen everyone but ralphm (who this morning warned that he might not be available)

  161. Guus

    mentioning him in the hope he'll pop in...

  162. Guus

    While we wait: does anyone want to add something to the agenda?

  163. Seve

    Not me, thank you

  164. MattJ

    Nor me

  165. Guus

    This morning, I've emailed about one of the items (financials) - I'd suggest we discuss that first.

  166. nyco

    I couldn't find time to read the thread, sorry

  167. Guus

    2. Minute taker

  168. Guus

    Would someone from the floor be so kind as to compose minutes?

  169. Guus

    ah, i forgot: last time, we discussed doing this live-ish, right?

  170. Guus

    as most of us are either on mobile, or busy, I"m thinking that's not feasible today?

  171. nyco

    right, I will propose a process, plus the tools for this

  172. Guus

    so for today, we could really use a minute taker, to not have to depend on chat logs

  173. nyco

    agree, mostly desktop solution

  174. Guus eyes the room

  175. Seve

    Today is not a good day for that due to mobiles :) but we can draft something out together after, checking the logs

  176. Guus

    sadly, no volunteers. If someone would like to do this retroactively, please.

  177. Guus

    In the interest of time, I'm continuing.

  178. Guus

    3. Publicize XSF Financials.

  179. MattJ

    +1 ;)

  180. Guus

    Does someone want to comment on my earlier email?

  181. Seve

    > +1 ;) Nice

  182. nyco

    I'll read the thread before voting

  183. MattJ

    As you and Seve already observed, we were all already in agreement about publication

  184. nyco

    off meeting

  185. MattJ

    There was just the matter of whether we would ask Peter to go through his paper archives for historical stuff

  186. Guus

    Ok, I motion that we ask our Treasurer to make prepare for publication of a summary of XSF financials, to be published on the XMPP.org website, for the current fiscal year, as well as future years.

  187. MattJ

    +1

  188. Seve

    +1

  189. Guus

    +1

  190. stpeter

    Yep, I can do that.

  191. Guus

    I will - right, stpeter has been informed πŸ™‚

  192. MattJ

    :)

  193. stpeter

    It will take me a few weeks, though.

  194. Guus

    while we have you - there was a debate last time, that revolved around us asking you to do this for past years

  195. Guus

    I don't think anyone expects this overnight, I'm fine with a few weeks (for the most recent data only)

  196. stpeter

    The past years can be done, too. We once had this information on the website (several websites ago!), so the wayback machine could perhaps help us. But in any case I have all the information, I just need to compile it again.

  197. Guus

    There was an argument where people felt it unfair/unneeded to do this for past years, while others (well, me), suggested that it'd be helpful to have, and well, since you offered...

  198. Guus

    Is the amount of work involved significantly more, after you did the first year?

  199. Guus

    alternatively, we could circle back to this after you did the the most recent stuff only

  200. Daniel

    If you decide to publish all can we prioritize 2018+current over 20 years of history

  201. Guus

    I've seen history on the website before, so I'm assuming that a large part of it is simply scraping old data?

  202. Guus

    (others, like myself, can help with that)

  203. Guus

    stpeter ?

  204. Guus

    We might have lost him. I think we can agree to have at least the most recent data. Let's circle back to having historical data too in a future meeting.

  205. stpeter

    I'm not sure where on the site we used to have this information. It's possible I have it all on my computer, but I don't have time to look right now because I need to take my wife to the airport soon.

  206. stpeter

    (By "all" I mean the earlier years - there will be a gap in the middle there somewhere.)

  207. stpeter

    But prioritizing recent years makes sense.

  208. Guus

    understood. If we can at least a commitment that somewhere in the next few weeks we'll publish the most recent data, that'd be good.

  209. stpeter

    Sure thing!

  210. Guus

    I'll take anything else as a bonus. I'd be happy to help you scrape stuff

  211. Guus

    Safe travels to your wife.

  212. stpeter

    I'll visit the wayback machine over the weekend.

  213. Guus

    thanks!

  214. Guus

    4. Commitment for weeks ahead: Review of Roadmap page

  215. Guus

    Ralphs icon is with that, on Trello

  216. Guus

    We discussed this earlier, but I'm unsure what the current state or action is

  217. Guus

    crickets.

  218. stpeter

    (We might also have the relevant files on an XSF machine, will check there too.)

  219. Guus

    let's park this for when Ralph is back

  220. Seve

    Ralph mentioned he would work on a list of possible topics for the Roadmap

  221. Guus

    5. Call for action: find candidates for the upcoming elections

  222. Guus

    Did we send out stuff through our comm channels?

  223. Guus

    I've not seen anything, but I've been away for a few days too.

  224. Seve

    I'm not aware, apart from the emails sent out by Alex

  225. Guus

    nyco do you happen to know?

  226. Guus

    Alas, we lost him to that meeting he warned us about

  227. Guus

    Does anyone have concrete plans to address this?

  228. Guus

    Have people in mind?

  229. Guus

    The current list of candidates is short: https://wiki.xmpp.org/web/Board_and_Council_Elections_2019

  230. Guus

    Especially for board

  231. Guus

    err, council, sorry.

  232. Seve

    I don't know of any person that could fit or be interested

  233. Seve

    We can tweet about it

  234. Guus

    Shall we draft an open invitation to be posted on our blog, and/or twitter?

  235. MattJ

    sgtm

  236. MattJ

    It would also make it easier for those of us in the community to link potential candidates to

  237. MattJ

    (which implies it would be good for such a post to have an overview of responsibilities)

  238. Guus

    Yeah. We could take Alex's default text as a template - I'd love to expand on it a little though

  239. Guus

    Yeah, that sounds good MattJ

  240. Guus

    Does anyone have a concrete text in mind, or shall I draft a suggestion?

  241. MattJ

    I don't, but happy to review a draft

  242. Guus

    ok

  243. Guus

    As it's time

  244. Guus

    6 AOB

  245. Guus

    Anyone?

  246. Seve

    None

  247. MattJ

    None

  248. Guus

    If I'm not mistaking, DST switchover is upon us, this weekend. Board members are all in the same switchover region, but others might be affected

  249. Guus

    (just in case you're in the US and REALLY want to be here for the next meeting?)

  250. Guus

    7. Date/Time of next

  251. Guus

    +1w

  252. Seve

    All good!

  253. Guus

    <the end>

  254. Guus bangs gavel

  255. Guus

    Thanks

  256. MattJ

    Thanks Guus

  257. Seve

    Thank you Guus

  258. Guus

    MattJ draft sent by mail

  259. Guus

    MattJ _rough_ draft sent by mail

  260. pep.

    > Guus> This morning, I've emailed about one of the items (financials) - I'd suggest we discuss that first. on board@ that's not public?

  261. MattJ

    Correct

  262. MattJ

    I don't believe it contained anything that wasn't discussed in the room today or in previous meetings

  263. larma

    financial summary 2001-mid 2008: https://web.archive.org/web/20150315021548/http://xmpp.org/about-xmpp/xsf/xsf-financial-summary/

  264. Guus

    Thanks larma / ping stpeter

  265. stpeter

    larma: thanks for that!

  266. pep.

    stpeter, "(By "all" I mean the earlier years - there will be a gap in the middle there somewhere.)"

  267. pep.

    What did this mean

  268. pep.

    (I'm compiling minutes)

  269. Guus

    Thanks pep.

  270. Guus

    I read that as that he might have all data that he compiled earlier still on his computer somehwere, but that he didn't compile data from all available rough data

  271. stpeter

    We have records for the early years. I will create financial summaries for the recent years, starting from 2019, but I will need to fill in 2008-2018 because https://web.archive.org/web/20150315021548/http://xmpp.org/about-xmpp/xsf/xsf-financial-summary/ indicates that I last did this in 2008.

  272. stpeter

    (Well, we have *records* for all the years, but they're in a fireproof safe at my house.)

  273. pep.

    stpeter, I see

  274. pep.

    So it'll just take time but data is present

  275. pep.

    somewhere

  276. stpeter

    Yes, the data just needs to be compiled - i.e., I need to look at all the expense reports and add things up. Not that hard.

  277. pep.

    k

  278. stpeter

    OK, now I actually need to go, I will check in later.

  279. pep.

    Minutes sent.

  280. Guus

    https://github.com/xsf/xmpp.org/pull/626

  281. pep.

    "only a few hours a week" hmm maybe this should be removed

  282. Guus

    I'm out for the day

  283. Guus

    Or at least a couple of hours

  284. Guus

    Please leave comments in the PR

  285. pep.

    k

  286. MattJ

    What types of invites do clients currently use with MUC? Do any clients do direct invitations?

  287. flow

    larma, FYI, we already depend on the unicode standard for our wire format, see also the most recent discussion at the IETF's XMPP WG mailing list

  288. flow

    also, I think that if you go for bytes or codepoints than sender (and ideally also recipient) should normalize the unicode string frist

  289. lovetox

    yes gajim in some circumstances

  290. Zash

    MattJ: I found a handful of mediated invites in my archive, no direct.

  291. lovetox

    about the sticker discussion

  292. lovetox

    byte seems very weird, i have to decode the stanza from the wire

  293. lovetox

    then get the body data

  294. lovetox

    then reencode it? split it up into parts

  295. Zash

    I (posted to the list that I) would go for codepoints.

  296. lovetox

    decode the single parts again

  297. Zash

    Everything except JavaScript should be able to deal with that.

  298. Zash

    Wait, what

  299. Zash

    Those were using XEP-0249 syntax but were sent from MUCs

  300. lovetox

    also whole discussion sounds like someone *wants* to find problems

  301. Zash

    Human language is complicated.

  302. flow

    Human is complicated

  303. lovetox

    lets just use codepoints and be finished with it, and questions like what if a graphem consists of mutliple codepoints and reference links into it

  304. lovetox

    yeah what then? nothing then, i apply bold to that and if what comes out is garbage

  305. lovetox

    i open a issue with the client that sent me that garbage

  306. lovetox

    but thats about it

  307. Zash

    yeah

  308. Zash

    Bugs will probably happen regardless

  309. flow

    I am undecided between codepoints and extended grapheme clusters, but I believe that if we use codepoints we should normalize the strings

  310. Zash

    Alternatively, pick a magic marker code point and replace that.

  311. flow

    cause otherwhise the codepoints may be different. Although this may be unlikely, I wouldn't risk it and I believe most platforms provide unicode normalization APIs, so it should be easy

  312. Zash

    or bring back xhtml-im and use <img>

  313. flow

    the rumors that xhtml-im is gone and needs to be brought back are exaggerated ;)

  314. Zash

    `git revert 48593ca5b8659553c02ce7b9e12fa7660436d9bc 4c5db548251a91d8e6c55b1add84f92765d172a3` and pretend nothing happened

  315. larma

    flow, I don't think the IETF mailing list issue is a real issue. Basically it says: PRECIS doesn't define the Unicode version to be used, so we are fucked. It's true that this is an issue in the standard, but also it shouldn't really matter in practice as long as you follow the rule of being strict on what you control and liberal what others send you. The issue of counting characters is much more imminent and will have real impact if not handled properly *now*. People are already using markup/reference XEP and do basically random stuff when there is bodys multi codepoint graphemes in place. Regarding normalizing: Clients probably should normalize before sending (and before determining markup/reference positions), however normalizing is Unicode version specific behavior, so a second normalizing by a different entity (using a different unicode version) might end up and further changes and thus this entity would be required to update the markup/reference positions. So it's probably better to just not do it when receiving or forwarding if you don't want to deal with that. Also note that normalizing might actually break things if the sender uses a newer unicode version for normalization.

  316. moparisthebest

    > as long as you follow the rule of being strict on what you control and liberal what others send you.

  317. moparisthebest

    you mean the thing you *shouldn't* do ? https://tools.ietf.org/html/draft-iab-protocol-maintenance-03

  318. Zash

    aka draft-postel-was-wrong or somesuch

  319. moparisthebest

    I liked the original working title better hehe https://tools.ietf.org/html/draft-thomson-postel-was-wrong

  320. moparisthebest

    +1 to Zash for having the best memory

  321. flow

    larma, I don't think we are fucked (mostly because I think what PRECIS does is sensible). All we need is agility regarding the supported Unicode standard in runtimes or libraries. In fact, chances are high that your system has a sufficiently recent unicode database in /usr/share/unicode(-data)

  322. flow

    And what the draft-iab-protocol-maintenance I-D says

  323. Zash

    Wait didn't that get RFC'd?

  324. Zash

    Huh, not yet I guess

  325. larma

    flow, sure for sending this is a sane thing to do, but for receiving you should be more liberal. After all your cannot ensure OS and/or client are of recent version.

  326. Zash

    be liberal or fail loudly

  327. Zash

    but also don't fail.

  328. moparisthebest

    > chances are high that your system has a sufficiently recent unicode database in /usr/share/unicode(-data)

  329. moparisthebest

    Any Redhat ever might surprise you!

  330. Zash

    Mmmmmmmm Enterprise

  331. flow

    moparisthebest, at least fedora has a unicode-ucd

  332. flow

    larma, I am not sure if you can be liberal, or, at least, if it wouldn't cause more problems in the long run. Being liberal in what to accept often sounds like a nice easy solution, but it sometimes causes unforeseen issues and in general causes the issues described in the I-D

  333. Zash

    Maybe the real answer is "it depends"

  334. flow

    as so often

  335. moparisthebest

    I don't know about unicode, but up to date redhat 7 has a curl that was released Feb 6 2013, and up to date still supported redhat 6 has a curl that was released in Nov 4 2009

  336. moparisthebest

    unicode is surely just as bad if not worse

  337. flow

    What implementations could do is to use an old unicode version when verifying and "generating" JIDs, to ensure maximum interoperability

  338. Zash

    strict mode when creating users and such?

  339. moparisthebest

    wouldn't that disallow things allowed by newer unicode versions?

  340. Zash

    yes, that's the point

  341. flow

    moparisthebest, yes, but if you prevent the user from even generating such JIDs you achieve maximum interop

  342. moparisthebest

    to ensure maximum interoperability maybe impls should just limit everyone to ASCII

  343. flow

    wanna create an new MUC? make sure to use unicode 6.0 (or so) to prepare and enforce the JID that you send to the MUC service

  344. Zash

    and now you're on the unicode upgrade threadmill! enjoy

  345. Zash

    them users gonna want those new codepoints, better upgrade

  346. flow

    it's software and protocols, we are always in the upgrade threadmill

  347. Zash

    Is CentOS 6 dead yet?

  348. moparisthebest

    I don't think so, redhat 6 isn't

  349. Zash

    https://cerdale.zash.se/upload/ilURA86kFBb66daT/image.png

  350. Zash

    There was something about ligatures but I don't remember the exact details.

  351. larma

    Zash, ligatures are a font only thing that affects displaying but not anything the toolkit is doing, so you can still select half of a ligature. Depending on toolkit, the selecting thing can already change how ligatures are displayed. I don't remember which, but I know I have once seen a messenger that manually rendered the cursor in the input field and this broke ligatures if the cursor was between the two characters that make up a ligature. And this actually can affect the two chars length (if they are shorter as a ligature) which could cause the multiline text field to wrap differently. Long story short: moving the cursor through the text field would actually cause the text in it to jump around.