jdev - 2022-02-02


  1. admin has joined
  2. larma has left
  3. Apollo has left
  4. Millesimus has joined
  5. doge has joined
  6. Apollo has joined
  7. pulkomandy has joined
  8. doge has left
  9. debacle has left
  10. alacer has left
  11. alacer has joined
  12. atomicwatch has left
  13. xecks has left
  14. alacer has left
  15. pulkomandy has left
  16. pulkomandy has joined
  17. jubalh has left
  18. alacer has joined
  19. atomicwatch has joined
  20. pulkomandy has left
  21. pulkomandy has joined
  22. alacer has left
  23. alacer has joined
  24. doge has joined
  25. pulkomandy has left
  26. pulkomandy has joined
  27. doge has left
  28. pulkomandy has left
  29. pulkomandy has joined
  30. thomaslewis has joined
  31. thomaslewis has left
  32. thomaslewis has joined
  33. Millesimus has left
  34. thomaslewis has left
  35. jonathan has left
  36. SouL has left
  37. pulkomandy has left
  38. pulkomandy has joined
  39. thomaslewis has joined
  40. thomaslewis has left
  41. pulkomandy has left
  42. pulkomandy has joined
  43. marc0s has left
  44. marc0s has joined
  45. Millesimus has joined
  46. pulkomandy has left
  47. pulkomandy has joined
  48. pulkomandy has left
  49. pulkomandy has joined
  50. J Marinaro has left
  51. admin has left
  52. Millesimus has left
  53. pulkomandy has left
  54. pulkomandy has joined
  55. admin has joined
  56. J Marinaro has joined
  57. xnamed has left
  58. admin has left
  59. Millesimus has joined
  60. pulkomandy has left
  61. pulkomandy has joined
  62. Millesimus has left
  63. atomicwatch has left
  64. atomicwatch has joined
  65. sonny has left
  66. sonny has joined
  67. Millesimus has joined
  68. doge has joined
  69. doge has left
  70. doge has joined
  71. Millesimus has left
  72. doge has left
  73. doge has joined
  74. doge has left
  75. doge has joined
  76. pulkomandy has left
  77. pulkomandy has joined
  78. Millesimus has joined
  79. pulkomandy has left
  80. pulkomandy has joined
  81. Yagizа has joined
  82. doge has left
  83. Millesimus has left
  84. doge has joined
  85. Millesimus has joined
  86. doge has left
  87. al has joined
  88. mac has joined
  89. Millesimus has left
  90. alacer has left
  91. alacer has joined
  92. Millesimus has joined
  93. Millesimus has left
  94. al has left
  95. Millesimus has joined
  96. doge has joined
  97. thomaslewis has joined
  98. serge90 has left
  99. thomaslewis has left
  100. doge has left
  101. atomicwatch has left
  102. nephele has joined
  103. atomicwatch has joined
  104. nephele has left
  105. serge90 has joined
  106. SouL has joined
  107. msavoritias has joined
  108. Millesimus has left
  109. pasdesushi has joined
  110. Millesimus has joined
  111. me9 has joined
  112. marc0s has left
  113. marc0s has joined
  114. Millesimus has left
  115. me9 has left
  116. Yagizа has left
  117. Yagizа has joined
  118. Millesimus has joined
  119. mac has left
  120. mac has joined
  121. sonny has left
  122. marc0s has left
  123. marc0s has joined
  124. wurstsalat has joined
  125. thomaslewis has joined
  126. thomaslewis has left
  127. debacle has joined
  128. Alex has left
  129. Alex has joined
  130. doge has joined
  131. emus has joined
  132. goffi has joined
  133. rafasaurus has left
  134. rafasaurus has joined
  135. mac has left
  136. marmistrz has left
  137. Millesimus has left
  138. Kev has joined
  139. mac has joined
  140. doge has left
  141. SouL has left
  142. SouL has joined
  143. marc0s has left
  144. marc0s has joined
  145. jubalh has joined
  146. Millesimus has joined
  147. doge has joined
  148. SouL has left
  149. SouL has joined
  150. marc0s has left
  151. marc0s has joined
  152. nephele has joined
  153. nephele has left
  154. nephele has joined
  155. FireFly has joined
  156. doge has left
  157. nephele has left
  158. lovetox has left
  159. Martin has left
  160. Martin has joined
  161. lovetox has joined
  162. doge has joined
  163. FireFly has left
  164. pep. Nobody cared much I guess, but https://xmpp.org/extensions/inbox/pubsub-ns.html#example-4 'text-multi' isn't correct here is it. Should be list-something?
  165. lauranna has left
  166. jonas’ doesn't list-something imply that the options are fixed by the server?
  167. pep. Here they are, it's a list returned by the server to say what pubsub#type (now) it hosts
  168. Millesimus has left
  169. flow Zash, hmm isn't idna punnycode and doesn't punnycode just encode unicode, and there is no unicode in foo@bar/baz
  170. flow not that I have all the encoding rules always in my head, so I very well be wrong here
  171. flow Zash, which error did you expect?
  172. jubalh has left
  173. pep. I'll leave text-multi. Maybe in a few years somebody will come up saying it was wrong all along..
  174. jonas’ no, text-multi makes sense
  175. jonas’ list-multi would imply <option/>
  176. jonas’ and that doesn't make much sense
  177. pep. Also in here https://bouah.net/specs/pubsub-filter.html ?
  178. flow hmm didn't we had the text-multi vs. list-multi discussion also wrt to MAM ID queries?
  179. pep. (I should add an anchor on that example)
  180. drops has left
  181. drops has joined
  182. pep. I'm curious because in 0004 it says text-mutli is a single string split
  183. pep. aiui
  184. Millesimus has joined
  185. flow pep., IIRC you are right
  186. pep. And here (both cases) it's multiple values
  187. paul has left
  188. drops has left
  189. drops has joined
  190. flow text-multi is that unintuitive field type which is basically "text with multiple newlines"
  191. flow and not "multiple different values of text"
  192. pep. So what's "multiple different values of text"?
  193. flow list-multi
  194. flow see also xep313
  195. pep. Ok
  196. Kev list-multi if they're selections from a list.
  197. drops has left
  198. flow "selections from a list" in the broadest sense
  199. Kev And there isn't one if what you want is the ability to provide multiple values that aren't selections from a list.
  200. pep. They're not actual selections. I mean there's no UI associated, at least in the first case. There might be in the second, who knows
  201. flow in xep313 we use list-multi to select from an unknown list of IDs
  202. flow also this note:
  203. flow A special note about the 'ids' field: this field is of type 'list-multi' which typically is used to allow the client to select from a provided list of options. In this case the list of all possible ids MUST NOT be provided by the server, as it is likely to be extremely large. Instead the server MUST include a Data Forms Validation (XEP-0122) [8] <validate/> element that signals the list is open to arbitrary values provided by the client.
  204. Kev Indeed.
  205. pep. hmm
  206. edhelas has left
  207. pep. Right because a client will use this form to reply right
  208. flow so what you want is list-multi + validate open
  209. flow so what you want is list-multi + validate open
  210. pep. Not in my case
  211. drops has joined
  212. flow so what you probably want is list-multi + validate open
  213. edhelas has joined
  214. pep. My first example is just the server saying "that's all I support"
  215. pep. My first example is just the server saying "that's all I host"
  216. pep. And in the second, it's the client saying "I want to filter these"
  217. pep. So there's no response. A form isn't really necessary
  218. pep. But it's what commonly used I thought
  219. drops has left
  220. drops has joined
  221. lovetox has left
  222. doge has left
  223. lovetox has joined
  224. pep. Also it's the only way to add info into disco#info no? 0004 Alongside <feature/>s
  225. Wojtek has joined
  226. flow pep., I am sorry but I am a bit lost :/ which ProtoXEP are we talking about?
  227. jubalh has joined
  228. pep. pubsub-ns. Which was rejected but I'm going to submit again on a different form (now that pubsub#type has been """clarified""")
  229. pep. I already have https://github.com/xsf/xeps/pull/1156 PR'd
  230. pep. Second one incoming
  231. flow is there a rendered version somewhere?
  232. pep. link in the PR
  233. pep. Also linked above
  234. pep. https://bouah.net/specs/pubsub-filter.html
  235. msavoritias has left
  236. msavoritias has joined
  237. qwestion has left
  238. flow I tend to say that this should be list-multi instead of text-multi, if it helps
  239. pep. Thanks. I'm updatin git
  240. flow nit: I am not really happy with the usage of the term "blocked" (and allowed) here
  241. pep. What would you rather see?
  242. flow but it's about filtering, so it's tricky as the best you could probably do is "filter" and "filter-out"
  243. flow "filter" will always be ambigous, as it's not immediatly clear if the filter removes those elements or only allows those elements through
  244. pep. Especially since I'm reusing these terms in the following XEP that's about restricting the type of nodes that can be created on a service :/
  245. pep. (where it's more appropriate)
  246. pep. Hopefully the text clarifies it a bit
  247. flow "filter" will always be ambiguous, as it's not immediatly clear if the filter removes those elements or only allows those elements through
  248. pulkomandy "include"/"exclude" ?
  249. pep. Then it's confusing for the following sister XEP I'd say? Should I use different terms nonetheless?
  250. mac has left
  251. Zash flow, ICU returns UIDNA_ERROR_DISALLOWED for @ and /
  252. jonas’ idna2003 or idna2008? :)
  253. Zash 2008
  254. jonas’ python does 2003 IIRC
  255. jgart has left
  256. larma has joined
  257. sonny has joined
  258. pep. flow, updated with list-multi thanks
  259. pep. Also any clue about the TODO after the example? https://bouah.net/specs/pubsub-filter.html#example-1
  260. jubalh has left
  261. doge has joined
  262. Alex has left
  263. spectrum has left
  264. Alex has joined
  265. paul has joined
  266. xecks has joined
  267. marc0s has left
  268. marc0s has joined
  269. flow pep., I'd slightly favor "filter-type" and "filter-out-type" for pubsub-filter
  270. marc0s has left
  271. marc0s has joined
  272. Zash Did anyone ever point at this vaguely related thing: https://xmpp.org/extensions/xep-0045.html#impl-service-traffic
  273. jubalh has joined
  274. pep. Dunno if that's what should be used, but I'm thinking MUC could use something similar to pubsub#type indeed
  275. pep. (channel vs groupchats etc.. and others)
  276. homebeach has left
  277. Matrix Traveler (bot) has left
  278. Matrix Traveler (bot) has joined
  279. homebeach has joined
  280. flow pep., is the empty form of any value? if not, then forbid it?
  281. TheCoffeMaker has left
  282. pep. It's equivalent to <field type='boolean' var='include-empty'><value>true</value></field> because I declare a default value in the spec
  283. pep. So it's of some value I guess
  284. pep. Isn't it
  285. pep. Can a list-multi field be empty btw
  286. pep. ("no elements proposed")
  287. rafasaurus has left
  288. rafasaurus has joined
  289. flow pep., so the empty field would only return pubsub items without type?
  290. pep. Yeah
  291. flow btw, I would also mandate return an error if both are set and not "ignore one"
  292. pep. hmm, I can see why (to prevent imlementations thinking they're doing something and not another), and I might add it, but there's also value in not returning an error I guess. To let implementations code it however they want.
  293. pep. At the bare minimum I think it should be specified, so here it is.
  294. pep. I might change that later
  295. paul has left
  296. flow code *what* however they want? it appears that's always an issue
  297. sonny has left
  298. sonny has joined
  299. sonny has left
  300. sonny has joined
  301. doge has left
  302. TheCoffeMaker has joined
  303. doge has joined
  304. doge has left
  305. marmistrz has joined
  306. paul has joined
  307. Wojtek has left
  308. FireFly has joined
  309. jubalh has left
  310. TheCoffeMaker has left
  311. pep. What's always an issue? You mean this comes back often? To error or not error?
  312. Wojtek has joined
  313. pep. I don't know I'm not in people's minds. I know I can make my compiler prevent me from doing such a thing (including both), so this wording is fine by me even if it's less forbidding, maybe. I'm sorry for people who use a lesser language (/s but not really). Errors do happen nonetheless I agree
  314. pep. I'll change it anyway. Not going to die on this hill :)
  315. paul has left
  316. flow My line of thought is like: If an implementation includes both in the form, then in the best case it just wastes bandwith, but in the worst case it wrongly expects a certain semantic
  317. flow but the receiving entity can not tell which case it is, so it should lean towards the safe side of erroring out
  318. paul has joined
  319. pep. Well yes the receiving entity can tell since it's specified
  320. marc0s has left
  321. marc0s has joined
  322. Alastair Hogge has left
  323. Alastair Hogge has joined
  324. antranigv has joined
  325. kikuchiyo has left
  326. TheCoffeMaker has joined
  327. kikuchiyo has joined
  328. TheCoffeMaker has left
  329. cdcode has joined
  330. atomicwatch has left
  331. flow how can the receiving entity tell the potentially wrong assumptions of the sending entity?
  332. serge90 has left
  333. flow otoh, it's hard to come up with an example of such a wrong assumption in this case
  334. doge has joined
  335. debacle has left
  336. jubalh has joined
  337. debacle has joined
  338. J Marinaro has left
  339. J Marinaro has joined
  340. mac has joined
  341. doge has left
  342. TheCoffeMaker has joined
  343. paul has left
  344. jonathan has joined
  345. TheCoffeMaker has left
  346. TheCoffeMaker has joined
  347. sonny has left
  348. sonny has joined
  349. larma has left
  350. doge has joined
  351. TheCoffeMaker has left
  352. TheCoffeMaker has joined
  353. Laura has left
  354. cdcode has left
  355. cdcode has joined
  356. cdcode has left
  357. cdcode has joined
  358. cdcode has left
  359. cdcode has joined
  360. cdcode has left
  361. cdcode has joined
  362. cdcode has left
  363. cdcode has joined
  364. cdcode has left
  365. cdcode has joined
  366. kikuchiyo has left
  367. marmistrz has left
  368. Laura has joined
  369. doge has left
  370. lovetox has left
  371. antranigv has left
  372. lovetox has joined
  373. xnamed has joined
  374. J Marinaro has left
  375. J Marinaro has joined
  376. mac has left
  377. larma has joined
  378. kikuchiyo has joined
  379. TheCoffeMaker has left
  380. TheCoffeMaker has joined
  381. paul has joined
  382. lauranna has joined
  383. Apollo has left
  384. Wojtek has left
  385. xnamed has left
  386. mac has joined
  387. sonny has left
  388. sonny has joined
  389. marc0s has left
  390. marc0s has joined
  391. me9 has joined
  392. Apollo has joined
  393. rafasaurus has left
  394. rafasaurus has joined
  395. kikuchiyo has left
  396. xnamed has joined
  397. marc0s has left
  398. marc0s has joined
  399. marc0s has left
  400. marc0s has joined
  401. antranigv has joined
  402. larma has left
  403. larma has joined
  404. kikuchiyo has joined
  405. Wojtek has joined
  406. xnamed has left
  407. Holger has left
  408. xnamed has joined
  409. spectrum has joined
  410. Millesimus has left
  411. Holger has joined
  412. xnamed has left
  413. doge has joined
  414. marc0s has left
  415. marc0s has joined
  416. xnamed has joined
  417. Millesimus has joined
  418. me9 has left
  419. selurvedu has joined
  420. Wojtek has left
  421. Wojtek has joined
  422. nephele has joined
  423. nephele has left
  424. nephele has joined
  425. thomaslewis has joined
  426. Millesimus has left
  427. thomaslewis has left
  428. TheCoffeMaker has left
  429. admin has joined
  430. doge has left
  431. TheCoffeMaker has joined
  432. nephele has left
  433. Millesimus has joined
  434. pep. Is <value></value> (or <value/>, they are equivalent right?) valid? To designate the empty value
  435. mac has left
  436. pep. (looking up XML Schemas..)
  437. Zash Empty string in most cases
  438. pep. Yeah empty string is good
  439. pep. There's this in the spec: “Note: The empty string is not a member of the ·value space· of language. Some constructs which normally take language codes as their values, however, also allow the empty string. The attribute xml:lang defined by [XML] is one example; there, the empty string overrides a value which would otherwise be inherited, but without specifying a new value.”
  440. pep. It may need to be defined specifically in the schema? (with <xs:simpleType><xs:restriction base="xs:string"><xs:enumeration value=""/>//)
  441. Zash That is a thing I've seen in some places
  442. pep. Which 0004 doesn't have
  443. mac has joined
  444. pep. There's an 'empty' type defined but it's not used for value
  445. pep. hmm. I guess I'll submit submit using this, and somebody will correct the XEP someday because their lib broke or sth :/
  446. pep. Unless anybody knows how to do that
  447. jubalh has left
  448. thomaslewis has joined
  449. xnamed has left
  450. xnamed has joined
  451. pep. flow, I updated the PR with your comments. Thanks! Still missing a change on allow/block.. not entirely sure what to do here
  452. pep. I explain in the XEP what they're supposed to be.. and if a lib wants to wrap them and make them clearer then that's what it'll do.. I was ok with include/excluse I guess
  453. thomaslewis has left
  454. lovetox has left
  455. lovetox has joined
  456. Wojtek has left
  457. Wojtek has joined
  458. FireFly has left
  459. FireFly has joined
  460. xecks has left
  461. marc0s has left
  462. marc0s has joined
  463. emus has left
  464. emus has joined
  465. marc0s has left
  466. marc0s has joined
  467. marc0s has left
  468. marc0s has joined
  469. xecks has joined
  470. TheCoffeMaker has left
  471. TheCoffeMaker has joined
  472. thomaslewis has joined
  473. marmistrz has joined
  474. Sam has left
  475. Sam has joined
  476. TheCoffeMaker has left
  477. TheCoffeMaker has joined
  478. jgart has joined
  479. atomicwatch has joined
  480. Yagizа has left
  481. Yagizа has joined
  482. Wojtek has left
  483. Wojtek has joined
  484. nephele has joined
  485. nephele has left
  486. nephele has joined
  487. nephele has left
  488. nephele has joined
  489. jubalh has joined
  490. Kev has left
  491. larma has left
  492. nephele has left
  493. nephele has joined
  494. thomaslewis has left
  495. mac has left
  496. nephele has left
  497. lovetox has left
  498. thomaslewis has joined
  499. lovetox has joined
  500. thomaslewis has left
  501. paul has left
  502. thomaslewis has joined
  503. thomaslewis has left
  504. jubalh has left
  505. paul has joined
  506. larma has joined
  507. COM8 has joined
  508. COM8 has left
  509. marc0s has left
  510. marc0s has joined
  511. Wojtek has left
  512. pulkomandy has left
  513. pulkomandy has joined
  514. Wojtek has joined
  515. jubalh has joined
  516. PapaTutuWawa has joined
  517. marc0s has left
  518. marc0s has joined
  519. Wojtek has left
  520. Wojtek has joined
  521. thomaslewis has joined
  522. Apollo has left
  523. alacer has left
  524. thomaslewis has left
  525. antranigv has left
  526. alacer has joined
  527. thomaslewis has joined
  528. thomaslewis has left
  529. marc0s has left
  530. marc0s has joined
  531. Apollo has joined
  532. marc0s has left
  533. marc0s has joined
  534. antranigv has joined
  535. kikuchiyo has left
  536. xnamed has left
  537. larma has left
  538. larma has joined
  539. TheCoffeMaker has left
  540. TheCoffeMaker has joined
  541. me9 has joined
  542. kikuchiyo has joined
  543. Wojtek has left
  544. Yagizа has left
  545. larma has left
  546. xnamed has joined
  547. larma has joined
  548. larma has left
  549. antranigv has left
  550. me9 has left
  551. x51 has joined
  552. PapaTutuWawa has left
  553. x51 has left
  554. pasdesushi has left
  555. pasdesushi has joined
  556. TheCoffeMaker has left
  557. me9 has joined
  558. antranigv has joined
  559. TheCoffeMaker has joined
  560. pulkomandy has left
  561. pulkomandy has joined
  562. msavoritias has left
  563. pasdesushi has left
  564. debacle has left
  565. debacle has joined
  566. emus has left
  567. marc0s has left
  568. marc0s has joined
  569. emus has joined
  570. me9 has left
  571. admin has left
  572. marmistrz has left
  573. lovetox has left
  574. lovetox has joined
  575. goffi has left
  576. lovetox has left
  577. lovetox has joined
  578. xecks has left
  579. xecks has joined
  580. thomaslewis has joined
  581. lovetox has left
  582. lauranna has left
  583. Navlost has joined
  584. Navlost has left
  585. cdcode has left
  586. nav has joined
  587. antranigv has left
  588. nav Is anybody aware of any clients (mobile in particular, but also desktop) implementing XEP-0080 (User Location)?
  589. nav https://xmpp.org/extensions/xep-0080.html
  590. nav …or any similar XEP?
  591. doge has joined
  592. nav The reason I'm asking is because I'm thinking it might be convenient to teach my webhooks component to recognise OsmAnd (https://osmand.net/) / Traccar (https://www.traccar.org/) position logging messages.
  593. nav That way, you can have a JID representing a person or asset and track it via PEP (XEP-0080).
  594. Alex has left
  595. jubalh has left
  596. Millesimus has left
  597. nav I am aware of Blabber.im and derivatives, which can interpret and display geo: URIs (https://datatracker.ietf.org/doc/html/rfc5870). That is great functionality for one-off positions, but not really for sending constant updates.
  598. doge has left
  599. wurstsalat has left
  600. nav Psi+ knows about PEP geolocation and shows much of the relevant info, which is great. If it displayed it in some kind of map widget à la Blabber.im that would be just ideal. 🙂
  601. larma has joined
  602. emus has left