XSF Discussion - 2020-07-08

https://cnnumerique.fr/files/uploads/2020/2020.07.06.ra_cnnum_concurrence_web.pdf

(fr)

i'm looking for a SIP (chat/messaging) to XMPP transport, do you know any ?

edhelas, eta build a asterisk to xmpp bot and presented it at the last berlin meetup, not sure if that is what you looking for

but a VoIP component (not a bot), that is discoverable by clients and bridges to the PTSN sounds very interesting

then you could "dial" via your xmpp client

Jitsi-meet provides numbers to call to right? How do they do it

edhelas, but you question reads like you only look for a SIP transport that is able to gateway textual content

yes, no A/V, basically forwarding text messages

I think Openfire's Asterisk plugin did this, but it's outdated and incompatible with modern versions of both Openfire and Asterisk

XEP-0048 declares it uses XEP-0223 in its examples. It uses a 'storage' element to wrap a 'conference' bookmark, when used inside of a PEP item. XEP-0223 does not use that 'storage' element (it adds the 'conference' directly to the 'item').

Guus, note that '223 is informational and does not define wire format

'48 is normative regarding bookmarks, in '223 it is really only an example on how private data in pep may be used

sure, but '48 explicitly states it uses '223 in its examples

> It is RECOMMENDED to use Publish-Subscribe (XEP-0060) [4] for data storage, specifically through the use of personal data nodes hosted at the user's virtual publish-subscribe service as described in Best Practices for Persistent Storage of Private Data via Publish-Subscribe (XEP-0223) [5] and illustrated in the following sections.

Guus, which means that you should very much configure the node correctly

'223 does not define wire format, only node configuration recommendations

which is what '48 uses

'48 does not use any wire format from '223, because '223 does not define wire format :)

I know examples are not normative, but how is https://xmpp.org/extensions/xep-0048.html#storage-pubsub-upload not using a wire format?

isn't that example just plain wrong, if just above the XEP states that it uses `223 for illustration purposes?

at the very least, it's wildly confusing.

what

'223 has zero to do with bookmarks

the example is in '48 and it defines wire format (with the storage element and everything)

but that has nothing to do with '223

the only thing '48 uses from '223 is the node config and the fact that pep is used

Okay, in that case it's wildly confusing that `223 uses in its examples bookmarks in a different way than `48 does: https://xmpp.org/extensions/xep-0223.html#example-1

maybe '223 should be clearer that the example is made up and has nothing to do with '48

the '223 example bases on the old '48 I think

Guus, patches welcome I suppose :)

So, the intended behavior is to have a single bookmark per pep item, wrapped in a 'storage' element?

in '48, yes

Guus, XEP-0402 does it differently

(and better)

Agreed. '48 should reference '402 - I completely missed it.

Guus, indeed, now that '402 is Draft, we should consider deprecating '48

and listing '402 as replacement

Guus, care to file a PR? I don’t have my credentials with me right now, and it’d be good to have a PR to track that

or at least drop me an email to the address I use on-list so that I can add it to next weeks council agenda (today may be a bit short notice) ✏

I've sent off a quick email to you

thanks

yeah deprecating 48 if no server fully support 402 is maybe a bit early

it's like deprecating 0071 when no other clients supported anything else :-°

I have a question or more

No audio messages please.

https://upload.yax.im/upload/Io2b3Q7fzA_bz521/20200708_200105169.m4a

lol

It's like having a feature you are not allowed to use.

*Sigh*

Anyone having knowlegde on the topic who wanne do a call with me on rooms and servers and such?

pep., no, '71 was obsoleted ;)

that’s worse and different

worse! indeed

nevermind, it was deprecated

but I think the initial move was to obsolete it and that was avoided

https://upload.yax.im/upload/NXOANOMP3RKQ4zPV/20200708_200503533.m4a

I think deprecation when a replacement exists is ok

Okay so I think I made a room

jesusisgodalmighty.life@chat.yax.im

So is it under my control now?

Hmmm should shorten the url i guess or room name

to be honest if you have questions you'd be better off to just ask them in the appropriate rooms via text, since that's how most of us communicate

What about deaf users? Or just listening to music? Or using a device without speakers?

or sitting next to kids and therefore being unwilling to broadcast unknown sounds out loud...

Why does F-Droid have a tracker?

https://upload.yax.im/upload/0Ix2VlGjrIVyEHov/Screenshot_2020-07-08-23-47-49.png

This seems a bit off-topic for the XMPP Standards Foundation?