XSF Discussion - 2020-06-16

  1. mukt2 has left
  2. mukt2 has joined
  3. lskdjf has left
  4. Daniel has left
  5. Daniel has joined
  6. mukt2 has left
  7. alexis has left
  8. mukt2 has joined
  9. alameyo has left
  10. alameyo has joined
  11. sonny has left
  12. sonny has joined
  13. alexis has joined
  14. mukt2 has left
  15. arc has left
  16. arc has joined
  17. mukt2 has joined
  18. waqas has left
  19. arc has left
  20. arc has joined
  21. Maranda has left
  22. andrey.g has left
  23. mukt2 has left
  24. mukt2 has joined
  25. adiaholic_ has left
  26. mukt2 has left
  27. mukt2 has joined
  28. Wojtek has left
  29. Neustradamus has left
  30. arc has left
  31. arc has joined
  32. arc has left
  33. arc has joined
  34. mukt2 has left
  35. Neustradamus has joined
  36. mukt2 has joined
  37. alameyo has left
  38. Neustradamus has left
  39. mukt2 has left
  40. mukt2 has joined
  41. Neustradamus has joined
  42. mukt2 has left
  43. mukt2 has joined
  44. alameyo has joined
  45. _Neustradamus has joined
  46. _Neustradamus has left
  47. mukt2 has left
  48. mukt2 has joined
  49. Neustradamus has left
  50. Neustradamus has joined
  51. mukt2 has left
  52. mukt2 has joined
  53. Neustradamus has left
  54. Neustradamus has joined
  55. mukt2 has left
  56. mukt2 has joined
  57. sonny has left
  58. sonny has joined
  59. mukt2 has left
  60. mukt2 has joined
  61. bear has left
  62. mukt2 has left
  63. mukt2 has joined
  64. arc has left
  65. arc has joined
  66. mukt2 has left
  67. mukt2 has joined
  68. arc has left
  69. arc has joined
  70. Yagiza has joined
  71. mukt2 has left
  72. mukt2 has joined
  73. mukt2 has left
  74. andy has joined
  75. mukt2 has joined
  76. bear has joined
  77. mukt2 has left
  78. mukt2 has joined
  79. murabito has left
  80. murabito has joined
  81. sonny has left
  82. sonny has joined
  83. govanify has left
  84. govanify has joined
  85. mukt2 has left
  86. mukt2 has joined
  87. mimi89999 has left
  88. mimi89999 has joined
  89. mukt2 has left
  90. mukt2 has joined
  91. mukt2 has left
  92. mukt2 has joined
  93. Mikaela has joined
  94. mukt2 has left
  95. mukt2 has joined
  96. alameyo has left
  97. mukt2 has left
  98. mukt2 has joined
  99. lorddavidiii has joined
  100. mukt2 has left
  101. mukt2 has joined
  102. alameyo has joined
  103. mukt2 has left
  104. mukt2 has joined
  105. mukt2 has left
  106. mukt2 has joined
  107. mukt2 has left
  108. mukt2 has joined
  109. paul has joined
  110. sonny has left
  111. sonny has joined
  112. Mikaela has left
  113. wurstsalat has joined
  114. sonny has left
  115. sonny has joined
  116. Tobias has left
  117. Tobias has joined
  118. j.r has left
  119. j.r has joined
  120. DebXWoody I think it would be nice to have a MUC for new users listet here: https://xmpp.org/community/chat.html
  121. DebXWoody I'm quite new in the XMPP topic, but I also had some problems to get into xmpp. xmpp.org is very technical. jabber.org is not working.
  122. Neustradamus has left
  123. jonas’ DebXWoody, I think it would be nice to have a MUC for new users first
  124. jonas’ we don’t have that
  125. Jeybe has joined
  126. Nekit has joined
  127. Neustradamus has joined
  128. DebXWoody jonas’, I know. As I started to work on https://wiki.xmpp.org/web/Guide/de and I think I ask for a mailinglist for users-community, there was a Feedback like "XSF in not responsible for users". This would be fine also, but in such case "we" need to start with something which will take care of users.
  129. jonas’ eys
  130. jonas’ yes
  131. Neustradamus has left
  132. Neustradamus has joined
  133. Neustradamus has left
  134. Neustradamus has joined
  135. krauq has left
  136. LNJ has left
  137. lorddavidiii has left
  138. LNJ has joined
  139. lorddavidiii has joined
  140. DebXWoody I would volunteer for support of German Community.
  141. krauq has joined
  142. debacle has joined
  143. Maranda has joined
  144. karoshi has joined
  145. karoshi has left
  146. karoshi has joined
  147. Maranda has left
  148. Maranda has joined
  149. alexis has left
  150. andrey.g has joined
  151. mukt2 has left
  152. alexis has joined
  153. Guus has left
  154. Guus has joined
  155. karoshi has left
  156. karoshi has joined
  157. mukt2 has joined
  158. arc has left
  159. arc has joined
  160. karoshi has left
  161. karoshi has joined
  162. jcbrand has joined
  163. emus has joined
  164. adiaholic_ has joined
  165. karoshi has left
  166. karoshi has joined
  167. karoshi has left
  168. karoshi has joined
  169. bear has left
  170. sonny has left
  171. sonny has joined
  172. karoshi has left
  173. karoshi has joined
  174. Alex has joined
  175. Andrzej has joined
  176. karoshi has left
  177. Shell has joined
  178. karoshi has joined
  179. Shell has left
  180. Shell has joined
  181. mukt2 has left
  182. karoshi has left
  183. flow create an entity which acts as xmpp foss software hoster (gitlab) and discussion platform (discourse) that attracts developers and users likewise?
  184. alameyo has left
  185. alameyo has joined
  186. karoshi has joined
  187. mukt2 has joined
  188. karoshi has left
  189. karoshi has joined
  190. dwd has left
  191. dwd has joined
  192. andrey.g has left
  193. Daniel has left
  194. emus I thought so too for a while. I am also a fried of "centralized communication" but still having a decentral network
  195. Daniel has joined
  196. jonas’ ew discourse
  197. Shell has left
  198. Shell has joined
  199. karoshi has left
  200. flow jonas’, it's probably easier for end-user to use discourse than mailing lists
  201. emus I dont like mailing lists, too.
  202. flow I like them, but I also like discourse :)
  203. jonas’ discourse is very non-attractive to me
  204. emus I think DebXWoody point is a different one
  205. karoshi has joined
  206. alameyo has left
  207. alameyo has joined
  208. bear has joined
  209. karoshi has left
  210. Holger I don't get the point. There's rooms such as xmpp:jabber@conference.jabber.org?join already, and also mailing lists. Nobody uses those. Adding more venues on top will make people use them?
  211. Holger I would've thought normal end users won't use any of those. They'll complain on the app store if something doesn't work, that's it.
  212. karoshi has joined
  213. Holger For power users actually interested in XMPP (as opposed to just their app), there are rooms already, and they are actually used, no?
  214. Zash Probably because https://search.jabber.network/ can't index jabber.org atm, so people looking for generic discussion channels find whichever ones happen to sound interesting.
  215. jonas’ > There's rooms such as xmpp:jabber@conference.jabber.org?join cannot be found via s.j.n
  216. Holger Ok. So the fix is migrating jabber.org to Prosody, no?
  217. jonas’ maybe
  218. jonas’ depending on what’s going on in there
  219. jonas’ I wasn’t aware of that room until just now ;)
  220. Ge0rG maybe just removing invalid JIDs from the storage will already solve it?
  221. jonas’ yes
  222. jonas’ but that’s apparently hard
  223. jonas’ because M-Link
  224. Kev > Holger > Ok. So the fix is migrating jabber.org to Prosody, no? The problem with j.o isn't that it's not Prosody, but that it's been abandoned and not had any updates installed in about 4 years. Just for the record ;)
  225. Shell has left
  226. Shell has joined
  227. Shell has left
  228. Shell has joined
  229. Guus none-the-less, Holger does make a valid point.
  230. Guus jabber.org has the benefit of being very recognizable. If we can improve its utilization, that would be good.
  231. jonas’ agreed
  232. Kev jonas’: I'm not sure it's hard, is it? Someone just needs to delete the dodgy file off disk (which is pre-M-Link)
  233. flow I think end-users unable to use their xmpp client are probably also unable to join an xmpp based chat room. and yes the ML is used, but I'd argue mostly not by end-users
  234. karoshi has left
  235. jonas’ Kev, I have no idea
  236. Kev I'm a little offended that people are treating it as M-Link's fault that the jabber.org admins stopped adminning jabber.org.
  237. jonas’ I don’t have shell here, but that the problem persists for over a year now despite me providing an exact list of invalid JIDs makes me think that it’s hard
  238. karoshi has joined
  239. jonas’ I don’t have shell there, but that the problem persists for over a year now despite me providing an exact list of invalid JIDs makes me think that it’s hard
  240. Holger Kev: Sorry, I didn't mean it that way at all.
  241. Holger Sounds like it's actually ejabberd's fault 🙂
  242. jonas’ I also can’t judge if it’s M-Links (the software’s) fault or not. More likely it’s that nobody with M-Link experience is left to work on jabber.org
  243. Holger (If you took over borked data from ejabberd.)
  244. Kev I don't know if it's ejabberd's fault either, it could date back to jabberd for all I know :)
  245. Kev (Actually, it's MUC so it'd be the old MUC component, if of that era)
  246. Holger Whatever, I was just assuming a migration of the service would involve cleaning up the data.
  247. jonas’ it certainly would
  248. Guus What's the status of the migration?
  249. krauq has left
  250. jonas’ "In progress"
  251. Ge0rG jonas’: you mean similarly to how the last migration cleaned up invalid data?
  252. jonas’ Ge0rG, no, because this time people are aware
  253. karoshi has left
  254. karoshi has joined
  255. karoshi has left
  256. karoshi has joined
  257. karoshi has left
  258. arc has left
  259. arc has joined
  260. karoshi has joined
  261. xecks has joined
  262. DebXWoody I was not able to join jabber.org because of Server-to-server connection failed: Connecting failed: dh key too small
  263. jonas’ that, too, is an issue which is hopefully to be fixed with the migration.
  264. mukt2 has left
  265. karoshi has left
  266. DebXWoody new users should join xmpp:jabber@conference.jabber.org which can not be found on the website of xmpp.org. It's not possible to find via the search website and the most provider are not able to join the server at all. Is is correct?
  267. Holger So maybe add that room to <https://xmpp.org/community/chat.html>? Like <JUser@jabber.org> is listed on <https://xmpp.org/community/mailing-lists.html>?
  268. Shell has left
  269. Shell has joined
  270. DebXWoody +1 if the "Connecting failed: dh key too small" is sloved
  271. Holger Though I'm still not sure the "XMPP user" role makes much sense. Users use apps, not protocols. Is there an SMTP/IMAP forum for new Thunderbird users?
  272. Daniel > Though I'm still not sure the "XMPP user" role makes much sense. Users use apps, not protocols. Is there an SMTP/IMAP forum for new Thunderbird users? +1
  273. Shell has left
  274. Daniel To be fair that's partially our fault because we have been trying to market XMPP to end users
  275. Shell has joined
  276. pep. That ^
  277. Kev Which isn't necessarily wrong, depending what you consider 'end users' to be.
  278. Daniel we should probably stop that instead improving it
  279. Kev It's the properties of XMPP, rather than particular apps, that are the interesting part to many organisations wanting to use it.
  280. Daniel !developers
  281. karoshi has joined
  282. pep. Daniel, I do think there's room for more than just developers. But we don't need to target everybody for sure
  283. Kev That is - some orgs 'buy' XMPP, and then go to find clients/servers that satisfy their particular requirements.
  284. pep. Kev, I'm not sure that's something I'd target either tbh. XMPP is vast enough so that you'll eventually (very quickly) run into interop issues if you don't all use the same things and have a somewhat tailored server setup
  285. Holger I think it's fine to run such a room, list in on the web site, hang around in that room, and answer the occasional questions. I just don't share any hopes that go beyond that, i.e. building up an XMPP end-user 'community' or something.
  286. karoshi has left
  287. karoshi has joined
  288. adiaholic_ has left
  289. adiaholic_ has joined
  290. krauq has joined
  291. mukt2 has joined
  292. Shell has left
  293. Shell has joined
  294. robertooo has left
  295. jonas’ I don’t have any hopes for that, I just want to redirect the flow of new users from the technical rooms
  296. lskdjf has joined
  297. !XSF_Martin Didn't pep. plan to do some joinxmpp website which should serve as a starting point for new users?
  298. pep. yeah there's that, which doesn't get much attention (from me) atm. I was never happy with the name though. I'd say if it becomes a thing it would only represent a subset of XMPP servers/clients (somewhat like snikket, maybe the same, maybe not)
  299. pep. From what I understand this is not MattJ's intention to have Snikket become a thing to which users can openly register, so maybe not just like Snikket :)
  300. Shell has left
  301. Shell has joined
  302. mukt2 has left
  303. karoshi has left
  304. Mikaela has joined
  305. MattJ Indeed
  306. !XSF_Martin Yeah, XMPP is very broad and not really a snappy term you would give to 'normal users'. Snippet is better marketing wise but a too small subset of the XMPP ecosystem.
  307. !XSF_Martin Yeah, XMPP is very broad and not really a snappy term you would give to 'normal users'. Snikket is better marketing wise but a too small subset of the XMPP ecosystem.
  308. MattJ It's not out of the question that a public/semi-public service would use Snikket, but providing such a service is not the goal of Snikket
  309. !XSF_Martin Every single time I write snippet instead of snikket. 😂
  310. Shell has left
  311. Shell has joined
  312. Zash FWIW you can get around the dh key issue by giving ECDHE higher priority, which a soon to be released Prosody version will do by default.
  313. karoshi has joined
  314. krauq has left
  315. Neustradamus has left
  316. karoshi has left
  317. karoshi has joined
  318. karoshi has left
  319. karoshi has joined
  320. karoshi has left
  321. robertooo has joined
  322. lorddavidiii has left
  323. karoshi has joined
  324. lorddavidiii has joined
  325. Shell has left
  326. Shell has joined
  327. karoshi has left
  328. karoshi has joined
  329. mukt2 has joined
  330. Shell has left
  331. Shell has joined
  332. dwd has left
  333. dwd has joined
  334. karoshi has left
  335. karoshi has joined
  336. neshtaxmpp has joined
  337. Mikaela has left
  338. Mikaela has joined
  339. rion is going to make an emoji-oriented PR for https://xmpp.org/extensions/xep-0038.html If anyone is interested in the XEP, send me your ideas.
  340. krauq has joined
  341. govanify has left
  342. govanify has joined
  343. govanify has left
  344. govanify has joined
  345. karoshi has left
  346. karoshi has joined
  347. karoshi has left
  348. arc has left
  349. arc has joined
  350. Shell has left
  351. Shell has joined
  352. neshtaxmpp has left
  353. Shell has left
  354. Shell has joined
  355. Mikaela has left
  356. lorddavidiii has left
  357. karoshi has joined
  358. Shell has left
  359. Shell has joined
  360. lorddavidiii has joined
  361. Shell has left
  362. Shell has joined
  363. karoshi has left
  364. karoshi has joined
  365. karoshi has left
  366. karoshi has joined
  367. Nekit has left
  368. Mikaela has joined
  369. Nekit has joined
  370. rion Basically I want to add categories and maybe also subcategories. Also I will add options to show an icon is a variant of another icon (all those about skin color. In UI it supposes to show the original icon in the icon selector but with a capability to select a variant on a long click or any other way). I think to add search keywords in accordance to https://unicode.org/emoji/charts-13.0/emoji-list.html Also somewhat unrelated to emoji but still needed is a way to tell the application where an raster icon may be scaled when presented to the user or it's better to keep the original resolution.
  371. neshtaxmpp has joined
  372. xsf has left
  373. rion I'm also thinking about metadata features. Like where it's white and black, better looking on the white or black background. Maybe something related to color blindness too.
  374. Nekit has left
  375. intosi has left
  376. Nekit has joined
  377. karoshi has left
  378. karoshi has joined
  379. intosi has joined
  380. paul has left
  381. paul has joined
  382. Shell has left
  383. neshtaxmpp has left
  384. govanify has left
  385. govanify has joined
  386. Nekit has left
  387. Nekit has joined
  388. thorsten has left
  389. thorsten has joined
  390. Shell has joined
  391. jcbrand Recently I registered fedi.chat (like fediverse), thinking that it could potentially becomes a user friendly endpoint.
  392. karoshi has left
  393. jcbrand I also think it makes sense to come up with a new name for the federated network, to keep it separate from XMPP
  394. jcbrand Jabber is a good name, but trademarked
  395. karoshi has joined
  396. jcbrand So I thought maybe fedichat is better
  397. jcbrand But it's maybe still to technical
  398. karoshi has left
  399. karoshi has joined
  400. papatutuwawa has joined
  401. Link Mauve It sounds cool at least (to me).
  402. mimi89999 has left
  403. pep. I'm afraid it's gonna be associated with fediverse a bit too much and people are gonna be confused why they can't use one with the other
  404. Link Mauve Isn’t it already an issue with all of these “ActivityPub” software?
  405. pep. You mean MastodonPub?
  406. Link Mauve What is the trademark situation on “fediverse” btw?
  407. !XSF_Martin > So I thought maybe fedichat is better > But it's maybe still to technical For people not knowing it means federated chat it's just brand/name so still ok. I guess a lot of old people know only WhatsApp is the name of that chat app not knowing it's derived from the english 'What's up?'
  408. mimi89999 has joined
  409. Daniel So WhatsApp is like Hanuta?
  410. !XSF_Martin > I'm afraid it's gonna be associated with fediverse a bit too much and people are gonna be confused why they can't use one with the other I guess if you ask random people on the street most won't know about fediverse so that's probably not a big issue.
  411. !XSF_Martin > So WhatsApp is like Hanuta? No, I can't eat WhatsApp but I can eat a Haselnusstafel. 😂 But yeah, I guess for most elderly it's like that.
  412. Zash pep., I've heard some argue that "fediverse" means all federated things, but yeah, it's mostly associated with Mastodon atm
  413. pep. Zash, I've heard some argue that it's all the federated web things :P
  414. Zash It means whatever you want it to mean!
  415. pep. Fediverse is fediverse!
  416. pep. Fediverse means fediverse!
  417. Daniel Between the people who block omemo and those who enable it by default it seems we can't even agree on a common user experience. So I'm honestly not sure if coming up with a name is the most important step here
  418. krauq has left
  419. pep. this ^ (again)
  420. Steve Kille has left
  421. Kev has left
  422. jcbrand This can happen in parallel
  423. Guus I'm not sure if we need to come up with a common user experience?
  424. jcbrand Things can happen in parallel
  425. pep. Guus, I think "we" needs to be external to the XSF
  426. jcbrand I agree
  427. karoshi has left
  428. pep. I don't think the XSF should dictate UI/UX
  429. Guus agreed.
  430. pep. Snikket is a good experiment this way. There can be others
  431. jcbrand There is also modern.xmpp
  432. pep. It's "the same" (person)
  433. Daniel Obviously not the xsf. But I think if I installed a fedichat client I'd expect it to work with other fedichat clients
  434. jcbrand there are more people involved in modern.xmpp
  435. karoshi has joined
  436. jcbrand IMO, the UI sprint kinda fell under that initiative
  437. pep. I don't think the UI sprint was meant to be for modernxmpp in particular but it got picked up by modernxmpp (which is not a bad outcome)
  438. jcbrand Daniel: that's the nice thing about having a name... you can make it a certification. If you want to be able to give yourself the name (or at least be on the official site), then you need to conform to the established rules
  439. jcbrand i.e. any app that calls itself a fedicaht app needs to adhere to certain UI and UX rules
  440. pep. "pep.> I don't think the XSF should dictate UI/UX" also why I strongly disagree with having 393 as a draft btw :x
  441. Daniel jcbrand: I agree that fedichat or what ever could be a certification (or should even) but again it doesn't feel like we as a community will be able to come up with a consensus
  442. Daniel I mean omemo is arguably the most touchy subject but that will divide the 'modern xmpp crowd' in half
  443. jcbrand IMO you just need a sufficiently motivated group of people to start something and then others can either join or not. We don't need buy-in from the entire community
  444. Daniel That I generally agree with
  445. winfried has left
  446. winfried has joined
  447. thorsten has left
  448. thorsten has joined
  449. winfried has left
  450. winfried has joined
  451. krauq has joined
  452. winfried has left
  453. winfried has joined
  454. eevvoor has joined
  455. debacle has left
  456. winfried has left
  457. winfried has joined
  458. adiaholic_ has left
  459. karoshi has left
  460. winfried has left
  461. winfried has joined
  462. j.r has left
  463. j.r has joined
  464. karoshi has joined
  465. Kev has joined
  466. Mikaela has left
  467. adiaholic_ has joined
  468. winfried has left
  469. winfried has joined
  470. MattJ I agree that a "common user experience" is not something we're going to achieve, nor necessarily want to
  471. MattJ I've been considering breaking Modern XMPP up into "profiles"
  472. MattJ Similar to what we've started to do with the complaince suites
  473. MattJ We touched on this at the summit, during the discussion about (iirc) "rich status"
  474. MattJ For some audiences such a thing would be something like WhatsApp stories, for others it could just mean adding an emoji to your status message
  475. Daniel if you end up creating as many profiles as there are products I don’t see the benefits of marketing the profile instead of the product though
  476. MattJ Obviously the intention would not be to do that :)
  477. MattJ I mean, look at the situation on iOS where we have so many clients that would fall into the "personal messaging" category, but they all have vastly different terminology, UI patterns and feature sets
  478. Zash So, given the existence of both anti-omemo and pro-omemo-only folks, we can't have the most basic interop at all.
  479. Kev I don't think most folks are anti-omemo, just pro-things-that-omemo-prevents.
  480. Kev FWIW.
  481. papatutuwawa has left
  482. Shell has left
  483. Unlife has left
  484. Unlife has joined
  485. Zash I'm anti-removal-of-my-choice-in-clients.
  486. pep. fwiw I'd probably still be using poezio or similar, because "I know" and I can adapt to different "profiles"
  487. pep. (and poezio allows me to)
  488. pep. I don't have enough time to write a client per profile
  489. Zash Yay modularity
  490. pep. But I'm not (we're not) your random end-user
  491. moparisthebest what does omemo prevent?
  492. jonas’ moparisthebest, server side search for one
  493. moparisthebest and don't say history across devices because that just requires some not-yet-existing history sync
  494. pep. moparisthebest, "not encrypting" :P
  495. Zash using non-omemo clients becomes very painful
  496. Link Mauve moparisthebest, until recently, anything that wasn’t part of the body.
  497. jonas’ Link Mauve, and in practice, still, because implementations are not quite there yet. and the ecosystem has been damaged from that "but we can’t omemo that" attitude for a while now
  498. moparisthebest jonas’, why
  499. jonas’ moparisthebest, why what?
  500. moparisthebest yes no argument there Link Mauve , but that's fixed *soon*
  501. jonas’ why if messages are end-to-end encrypted you cannot do full-text search inside the encrypted data on the server?
  502. moparisthebest jonas’, server side search, why
  503. moparisthebest yea but you can on the client
  504. jonas’ that’s not "server side search"
  505. jcbrand moparisthebest: Any kinds of attachments (e.g. emoji-reactions or mentions) (at least until recently)
  506. jcbrand moparisthebest: Any kinds of references (e.g. emoji-reactions or mentions) (at least until recently)
  507. jonas’ moparisthebest, yeah, see how well that performs on mobile. conversations is extremely slow because it has to keep the fts index up-to-date
  508. moparisthebest and everyone running prosody or ejabberd on their rpi1 won't be very happy with FTS on the server, meh
  509. pep. Also because people whom it concerns are not saying it or are hiding behind other excuses I will for them (you can thank me later): OMEMO also non-GPL implementations (or at least makes it harder) :)
  510. pep. Also because people whom it concerns are not saying it or are hiding behind other excuses I will for them (you can thank me later): OMEMO also prevents non-GPL implementations (or at least makes it harder) :)
  511. jonas’ I suspect the portion of users doing that is *much* smaller than the portion of users running an XMPP IM client on a smartphone.
  512. jonas’ pep., not anymore it doesn’t
  513. jonas’ or did I miss something?
  514. Daniel to be fair as far as I understand it your situtation jonas’ is a bit special because you turn Conversations on once per week
  515. jonas’ Daniel, yes, because otherwise it’d drain my battery all the time for the same reason
  516. Daniel and Conversations is a bit shitty about the way MAM catchups are stored in sql
  517. pep. jonas’, dunno, just making fun of some who hide behind other excuses while that was actually a pretty obvious end-goal
  518. Daniel that can (and probably should) be optimized
  519. jonas’ and because I can’t stand my phone vibrating when I don’t want to pay attention to it
  520. moparisthebest so far I've heard valid reasons not to use historical omemo, and not much else, that seems right
  521. moparisthebest jonas’, that's what the quiet hours are for
  522. jonas’ moparisthebest, thanks for just ignoring server-side search and references as a valid reason.
  523. jonas’ moparisthebest, no, because I want to get non-XMPP text messages (and other stuff) still.
  524. moparisthebest references aren't an issue right?
  525. moparisthebest server-side search, yea, I think that's useless
  526. moparisthebest I guess if you want to offload search to some other more powerful device you can right?
  527. jonas’ moparisthebest, good argument there, love it /s
  528. jonas’ tunes out
  529. mukt2 has left
  530. Link Mauve moparisthebest, basically anything where the server would want to see the messages, be it for spam reasons, for long-term archiving, etc.
  531. moparisthebest did I misunderstand? I think both Link Mauve and jcbrand brought up good reasons why it wasn't ready to use historically, but that's solved in latest versions
  532. Link Mauve moparisthebest, also the issue of getting a new device and being unable to see previous history.
  533. moparisthebest ^ that just needs some history sync thing
  534. jonas’ "just"
  535. Link Mauve (Which for me would be a deal stopper.)
  536. moparisthebest I've heard WA has history sync, I wonder if they have any documents about how it works
  537. Daniel MAM sync between devices should be relatively easy (on paper)
  538. Daniel with a bit of luck I might get paid to implement that at some point
  539. MattJ Nice
  540. moparisthebest well and with omemo encrypting everything now, also actually safe
  541. adiaholic_ has left
  542. adiaholic_ has joined
  543. Daniel jingle; web rtc data channels; and encrypted xml streams (what's the name again)
  544. moparisthebest ok these are less impressive than you would have thought https://faq.whatsapp.com/android/chats/how-to-restore-your-chat-history https://faq.whatsapp.com/iphone/chats/how-to-restore-your-chat-history
  545. Daniel so in your home network it doesn’t even hit your server
  546. moparisthebest tl;dr "just back up to $creep-cloud then restore!"
  547. Daniel plus is reasonable secure
  548. mukt2 has joined
  549. karoshi has left
  550. karoshi has joined
  551. karoshi has left
  552. karoshi has joined
  553. Jeybe has left
  554. Nekit has left
  555. Nekit has joined
  556. winfried has left
  557. winfried has joined
  558. Mikaela has joined
  559. govanify has left
  560. govanify has joined
  561. waqas has joined
  562. karoshi has left
  563. waqas has left
  564. winfried has left
  565. winfried has joined
  566. karoshi has joined
  567. Neustradamus has joined
  568. thorsten has left
  569. winfried has left
  570. winfried has joined
  571. mukt2 has left
  572. mukt2 has joined
  573. winfried has left
  574. winfried has joined
  575. karoshi has left
  576. karoshi has joined
  577. winfried has left
  578. winfried has joined
  579. Shell has joined
  580. andrey.g has joined
  581. andy has left
  582. andy has joined
  583. j.r has left
  584. j.r has joined
  585. alexis has left
  586. winfried has left
  587. winfried has joined
  588. Shell has left
  589. Shell has joined
  590. karoshi has left
  591. karoshi has joined
  592. adiaholic_ has left
  593. adiaholic_ has joined
  594. andrey.g has left
  595. lovetox has joined
  596. govanify has left
  597. govanify has joined
  598. mukt2 has left
  599. mukt2 has joined
  600. winfried has left
  601. winfried has joined
  602. stpeter has joined
  603. jjrh I'm currently trying to work with a proprietary client that doesn't even display error messages :/ Like if you send to a invalid jid, one that doesn't exist, or in my usecase if the component is down, it doesn't inform the user at all.
  604. Zash Not great :(
  605. debacle has joined
  606. neshtaxmpp has joined
  607. debacle has left
  608. debacle has joined
  609. winfried has left
  610. winfried has joined
  611. andrey.g has joined
  612. lovetox has left
  613. jjrh Pretty bizarre I would have thought they would at least tell you if it was a invalid jid
  614. Shell has left
  615. Shell has joined
  616. pep. "invalid jid" and "jid that doesn't exist" are different things
  617. jjrh well it was happy to do test.example.com (a typo on my part)
  618. jjrh but yeah that's a fair point.
  619. Zash No indication if you e.g. message xmpp:someone@reject.badxmpp.eu ?
  620. jjrh not as far as I can see.
  621. Shell has left
  622. Shell has joined
  623. jjrh You see all this in the logs so I guess they just haven't implemented it in the gui
  624. !XSF_Martin https://xmpp.org/extensions/xep-0377.html#payload « I don't understand example 3. Shouldn't there also be an opening for the spam element and an JID in it?
  625. Maranda has left
  626. pep. !XSF_Martin, no it's just an empty <spam/>
  627. Maranda has joined
  628. pep. The text can be confusing yeah. And there's no schema of course
  629. !XSF_Martin So, I tell the server I receive spam but I won't reveal the spammers JID? Sounds like some academic example that doesn't make much sense. Or am I missing the point about sending a report like this?
  630. pep. Well you tell it in the blocking command
  631. pep. Well you tell it with 191
  632. goffi has joined
  633. pep. I also find sad that the two are not separate, but that's a start..
  634. !XSF_Martin Yeah, but that's only when you combine it with blocking, so it only works with your server, right? I had a look at the XEP because I was curious if you could implement in a client to also report spammers from remote servers to their server.
  635. lskdjf has left
  636. alameyo has left
  637. alameyo has joined
  638. Zash !XSF_Martin, pep., https://xmpp.org/extensions/xep-0268.html
  639. lskdjf has joined
  640. neshtaxmpp has left
  641. pep. Fancy CamelCase XML in there
  642. Zash also https://xmpp.org/extensions/xep-0287.html
  643. pep. Is that implemented anywhere?
  644. Zash Yes
  645. pep. Anywhere it matters for us?
  646. Zash Metronome IIRC
  647. Jeybe has joined
  648. Zash The IODEF could use an example of the minimum you'd actually need, ie JID and a reason
  649. Zash The IODEF XEP* could use an example of the minimum you'd actually need, ie JID and a reason
  650. pep. > A client software doesn't need to interrupt a user when processing such marked stanzas: for example, it may put them silently in "SPAM" folder, so a user can look through them at any time later.
  651. pep. Interesting. How do they implement a spam folder
  652. pep. (0287)
  653. Zash Similar to how you implement the inbox folder? :)
  654. pep. not
  655. Lance has joined
  656. !XSF_Martin Mickaël Rémond is one of the XEP-0268 authors so I would expect it to be supported by ejabberd…
  657. !XSF_Martin Uh, and MattJ too…
  658. Wojtek has joined
  659. Zash You can contribute to the XEP without implementing it :)
  660. !XSF_Martin Obviously. 😃
  661. winfried has left
  662. winfried has joined
  663. Guus Interessed to see how spam will play out after jabber.org gets a new server.
  664. Guus Pretty much all spam that I receive comes through that.
  665. Guus I wonder how fast updated spam lists will circulate.
  666. Jeybe has left
  667. !XSF_Martin You receive spam on your JID there or from spammers using that server?
  668. Ge0rG Wasn't IBR disabled on j.o a decade ago?
  669. karoshi has left
  670. Neustradamus Psi Stop Spam plugin is really good :)
  671. Neustradamus Since several years, I do not see spam messages
  672. Guus I receive spam on my j.o account. The senders are on other servers.
  673. Shell has left
  674. Shell has joined
  675. Neustradamus Guus: Same!
  676. karoshi has joined
  677. karoshi has left
  678. Daniel has left
  679. karoshi has joined
  680. Daniel has joined
  681. karoshi has left
  682. karoshi has joined
  683. papatutuwawa has joined
  684. karoshi has left
  685. adiaholic_ has left
  686. adiaholic_ has joined
  687. karoshi has joined
  688. karoshi has left
  689. neshtaxmpp has joined
  690. papatutuwawa has left
  691. eevvoor has left
  692. karoshi has joined
  693. karoshi has left
  694. karoshi has joined
  695. mukt2 has left
  696. Nekit has left
  697. karoshi has left
  698. karoshi has joined
  699. vanitasvitae has left
  700. neshtaxmpp has left
  701. vanitasvitae has joined
  702. karoshi has left
  703. karoshi has joined
  704. karoshi has left
  705. Nekit has joined
  706. vanitasvitae has left
  707. vanitasvitae has joined
  708. Ge0rG I've heard there are servers with sophisticated spam filters where the user doesn't need to do anything or solve captchas
  709. Tobias has left
  710. Tobias has joined
  711. karoshi has joined
  712. mukt2 has joined
  713. Zash Rule #1 of spam fighting: Don't talk about rules of spam fighting
  714. pep. Are you a reflection of myself?
  715. Zash Rule #2 of fight club: Don't assume anyone remembers the plot of fight club
  716. jonas’ Sam claims that the github permissions thing is confusing. Am I misreading this?
  717. jonas’ https://share.dreckshal.de/dpm/kEO0ibQ9V3wAql7HMkJMHF2CCk-poH0CzRhToyQrry4.png
  718. jonas’ below that, it shows a list of all orgs I’m part of
  719. jonas’ how can I read that except "that software will gain +rw on all things I can see on github"?
  720. Nekit has left
  721. pep. I think you read correctly
  722. pep. But maybe you can test for yourself with some oauth thing you build :x
  723. jonas’ suuure
  724. lovetox has joined
  725. Kev Yes, Github's lack of sensible roles is horrific.
  726. Nekit has joined
  727. Shell has left
  728. Shell has joined
  729. krauq has left
  730. Nekit has left
  731. Guus Isn't the go-to solution to create an account that has access only to the repository it needs to operate on?
  732. jonas’ Guus, yes, that would be worth a shot I guess
  733. jonas’ I won’t do that, and I won’t interact wtih that account though
  734. jonas’ for reasons I’d rather not disclose here
  735. Guus sounds like something that iteam wants to weigh in before we do anything anyway.
  736. jonas’ indeed
  737. jonas’ not that I’m not an iteam meamber ;)
  738. jonas’ it seems like a useful thing to have, also for potential future automation tasks like commenting on issues or stuff
  739. Zash service accounts eh?
  740. jonas’ they call it "machine accounts" in the ToS and you’re only allowed to have one per human
  741. wurstsalat has left
  742. wurstsalat has joined
  743. flow let's make babies then!
  744. paul has left
  745. jonas’ and it’s not quite clear to me if such a usage is a "machine account" or if you need more than just that
  746. jonas’ flow, that sounds like quite a drastic solution to the problem
  747. paul has joined
  748. moparisthebest woah flow , what a proposal :P
  749. flow well cloning isn't feasiable yet, so?
  750. jonas’ I’ll post that to the list, let’s see if Sam and Guus consider that too complicated, too ;)
  751. jonas’ Guus actually might have first-hand experience on that.
  752. Guus I hear the latter can be annoying
  753. Zash I hear some here actually have a head start on that
  754. Guus Sam's pretty cool though.
  755. flow But serious: Not that it matters, but I would favor a single git repository hosting solution, preferably gitlab
  756. jonas’ flow, *personally*, I’d also prefer to just switch over to gitlab, because it’s the easiest solution to the problem (for me, because I know GitLab CI from work and stuff, and what I’ve seen so far from GitHub Actions is not convincing me), but I hear the input from the others that it’ll be pretty disruptive for the community
  757. pep. flow, depending on how "human" is defined, they may only allow one per uniquely identifiable human(?) and thus discard cloning
  758. Daniel +1. If the editors think gitlab will help them do their job better we should just do that
  759. pep. ^ this (again)
  760. pep. Daniel stop agreeing with me today
  761. jonas’ notes that no consenting voices were seen on the mailing list
  762. Daniel I think that someone who edits a XEP should be able to setup a gitlab account
  763. flow pep., what about multiple personalities? do they count as uniquely identifiable human?
  764. Daniel It's not that hard
  765. flow pep., what about multiple personalities? do they count as uniquely identifiable humans?
  766. pep. yeah I also note that I haven't replied to the list
  767. pep. flow, I'll leave that for you to answer
  768. jonas’ Daniel, someone off-list mentioned to me that there are concerns about getting a company to allow you to use $platform, and it’s more likely that $company has already allowed GitHub than GitLab
  769. Kev Daniel: It's not so much that they *can't*, as that it's effort, and we need to balance the cost of contributing with the cost of Editor work. And if that means GitLab, so be it - but it's a tradeoff rather than a straight win, I believe.
  770. flow Plus, as always, you are not required to created an gitlab account to submit protoxeps and patches
  771. pep. You are indeed not required
  772. pep. Sending patches to editors is always possible
  773. flow Plus, as always, you are not required to created a gitlab account to submit protoxeps and patches
  774. pep. I'm happy to do/encourage this (as an editor) if that means we can allow editors to move more easily
  775. Daniel *If* it comes down to not burning out our editors VS losing a contribution it'd rather take the former
  776. Daniel Because without editors we can't do anything
  777. Kev Daniel: I think that's the point I made on list.
  778. jonas’ Thanks for the increasing amount of feedback here
  779. jonas’ I’d really like to get to a point where editors can just hit "Merge when pipeline succeeds" if a change passes all editorial requirements; A simple button function which github doesn’t even have :(
  780. flow hmm merge trains are not avaialble on gitlab.com, aren't they?
  781. flow hmm merge trains are not avaialble on gitlab.com, are they?
  782. jonas’ not for free, methinks
  783. jonas’ haven’t used them either, are they cool?
  784. flow well if we'd host our own gitlab we could get a license where they are available
  785. flow jonas’, I consider merge trains and building merge results a deal breaker
  786. jonas’ flow, that are two things right away which I’d not like us to have to
  787. jonas’ (self-host and license)
  788. jonas’ I’d prefer to buy the respective Tier at the SaaS offering
  789. flow Uh I probably should have written: I consider *not having* merge trains and building/CIing merge results a deal breaker
  790. jonas’ (FTR, merge trains are, for both SaaS and self-hosted, on the second tier, i.e. $19/user/month)
  791. flow works for me, although I believe we could self-host
  792. jonas’ what do you mean with "building/CIing merge results"?
  793. jonas’ this one? https://docs.gitlab.com/ee/ci/merge_request_pipelines/pipelines_for_merged_results/index.html
  794. flow jonas’, MRs and PRs are usually build against the branchs HEAD, and not against the merge result of source and destination branch of the MR/PR
  795. flow jonas’, I think this, yes
  796. jonas’ read up on it, sounds nice, but I don’t consider this a must-have
  797. jonas’ not for xeps anyways, because it is very unlikely to have a fast-forward-able merge which breaks things
  798. flow I wouldn't want to miss it for software projects
  799. jonas’ I can believe that
  800. jonas’ but build-wise, XEPs are fairly independent from one another
  801. jonas’ when merging two different changes on the same XEP, editors typically step in to handle the revision blocks manually anyways
  802. vanitasvitae has left
  803. flow jonas’, I think this mostly means that merge trains are not that interesting for the xeps repo, but not pipelines for merged results
  804. jonas’ I think what I said also applies for pipelines for merged results
  805. flow those should always provide in advantage compared to the standard behavior or github PRs and gitlab MRs
  806. vanitasvitae has joined
  807. flow assume we had linting in the XEPs repo, and you add a new lint check to master
  808. jonas’ aha, yeah, that
  809. jonas’ I see that one now
  810. flow assume we had linting to the XEPs repo, and you add a new lint check to master
  811. flow bbl
  812. jonas’ still I see it only as nice-to-have
  813. jonas’ I mean we don’t have that on GitHub and we survived thus far
  814. krauq has joined
  815. Zash The XSF got along before Github even
  816. jonas’ also true
  817. waqas has joined
  818. APach has left
  819. APach has joined
  820. eta has left
  821. eta has joined
  822. vanitasvitae has left
  823. vanitasvitae has joined
  824. Yagiza has left
  825. Shell has left
  826. Shell has joined
  827. mukt2 has left
  828. krauq has left
  829. Andrzej has left
  830. Andrzej has joined
  831. arc has left
  832. arc has joined
  833. Andrzej has left
  834. Andrzej has joined
  835. adiaholic_ has left
  836. adiaholic_ has joined
  837. pep. "XSF, P.O. Box 1641, Denver, CO 80201 USA" Is there still anybody at the other end of this box? (reading the IPR)
  838. pep. "Version 1.4 (2008-01-23): Updated legal notices to use modified MIT License rather than Creative Commons Attribution License for the purpose of enabling wider distribution of XEP text and examples, including incorporation into free software; added Disclaimer of Warranty and Limitation of Liability." Does someody know the origin of this change?
  839. mukt2 has joined
  840. Zash Can you mail XEP patches there? :)
  841. Nekit has joined
  842. pep. Like some challenge?
  843. pep. I just "grepped" for "IPR" in all 2007's subjects on standards and found nothing. There seem to only be stpeter's email in January 2008 saying "it's done!"
  844. jonas’ pep., IPR sounds more like a board matter
  845. jcbrand has left
  846. pep. Well yeah but somebody would have raised the issue somewhere else before
  847. pep. And then board taking action
  848. jonas’ not if board figured out themselves that CC + FLOSS licenses don’t mix well
  849. pep. CC + FLOSS does mix :x and is probably more appropriate to stuff that isn't "software"
  850. pep. Just as MIT says
  851. werdan has joined
  852. jonas’ pep., well, I recall that CC + FLOSS license mixing was not well understood in the 00s
  853. jonas’ and people were cautious
  854. jcbrand has joined
  855. Andrzej has left
  856. Andrzej has joined
  857. pep. btw how does versioning of the IPR work? There doesn't seem to be anything in the document saying "and you also accept any change of this document". Does that mean everybody needs to resign? Or that some XEPs are served under a CC and some under a MIT-like license?
  858. Andrzej has left
  859. Andrzej has joined
  860. pep. (and "you also accept any change to this document" is not legal in some legislations anyway.. like France aiui)
  861. jonas’ pep., AFAIK, all XEPs use the same IPR template
  862. pep. Yeah but you can't just change the terms of what people agree to if you don't say anything about it :x
  863. jonas’ indeed
  864. Kev That's why the policy is handing over IPR to the XSF, rather than licensing to the XSF.
  865. Kev (Or as close to it as a local jurisdiction allows)
  866. pep. I see. let me disgest that..
  867. pep. I see. let me digest that..
  868. Kev The contribution agreement isn't to license XEPs to the XSF, it's to give them.
  869. pep. hmm ok so CLA-like
  870. pep. jonas’, ^ so I doubt it's possible to do what we thought
  871. pep. (And yes it's actually handled as a CLA on github, but it's a bit confusing)
  872. jonas’ I obviously don’t know what happened back then, but I suppose if we had to do it again, it’d be a mixture of getting people to re-sign + fixing the rendering so that the difference is clear
  873. Jeybe has joined
  874. pep. Well as I understand it now, resign wouldn't be necessary because you agreed to give ownership to the XSF (that can then change licenses over your work at will). In legislations where this is even possible
  875. pep. (which is probably not in France, still, but..)
  876. andy has left
  877. pep. Thanks Kev, that helps.
  878. pep. Still curious why the last revision if anybody's got info
  879. Shell has left
  880. jonas’ yeah, I hadn’t read that yet
  881. Shell has joined
  882. jonas’ I think in Germany, you can do that; contracts with employers typically have something similar
  883. mukt2 has left
  884. pep. hmm that's a good point. I don't know to what extent one can bend french law to make this a reality though
  885. mukt2 has joined
  886. pep. labor law*. I think it's also possible but I don't know if submitting a XEP would fall under labor law :P
  887. arc has left
  888. arc has joined
  889. neshtaxmpp has joined
  890. Andrzej has left
  891. werdan has left
  892. andy has joined
  893. neshtaxmpp has left
  894. werdan has joined
  895. APach has left
  896. APach has joined
  897. Nekit has left
  898. thorsten has joined
  899. andy has left
  900. andy has joined
  901. Andrzej has joined
  902. govanify has left
  903. govanify has joined
  904. lorddavidiii has left
  905. Shell has left
  906. Shell has joined
  907. krauq has joined
  908. werdan has left
  909. Shell has left
  910. Shell has joined
  911. stpeter has left
  912. Shell has left
  913. Shell has joined
  914. bear has left
  915. Mikaela has left
  916. xsf has joined
  917. Shell has left
  918. Andrzej has left
  919. thorsten has left
  920. arc has left
  921. arc has joined
  922. stpeter has joined
  923. mukt2 has left
  924. keke has joined
  925. keke hello cant get confirmation for jabber id
  926. thorsten has joined
  927. mukt2 has joined
  928. keke has left
  929. andy has left
  930. alexis has joined
  931. lovetox has left
  932. arc has left
  933. arc has joined
  934. arc has left
  935. arc has joined
  936. thorsten has left
  937. LNJ has left
  938. thorsten has joined
  939. bear has joined
  940. alexis has left
  941. Nekit has joined
  942. andy has joined
  943. thorsten has left
  944. thorsten has joined
  945. alexis has joined
  946. Tobias has left
  947. goffi has left
  948. jcbrand has left
  949. robertooo has left
  950. robertooo has joined
  951. andy has left
  952. j.r has left
  953. j.r has joined
  954. andy has joined
  955. Lance has left
  956. LNJ has joined
  957. mukt2 has left
  958. j.r has left
  959. Lance has joined
  960. mukt2 has joined
  961. LNJ has left
  962. andy has left
  963. mukt2 has left
  964. mukt2 has joined
  965. alameyo has left
  966. eta has left
  967. Nekit has left
  968. j.r has joined
  969. neshtaxmpp has joined
  970. neshtaxmpp has left
  971. neshtaxmpp has joined
  972. eta has joined
  973. xecks has left
  974. neshtaxmpp has left
  975. Jeybe has left
  976. lskdjf has left
  977. paul has left
  978. j.r has left
  979. emus has left
  980. neshtaxmpp has joined
  981. karoshi has left
  982. karoshi has joined
  983. neshtaxmpp has left
  984. mukt2 has left