Re: [Standards] XEP-0372 References: Real JID used for groupchat messages
I would always prefer stable identifier. If it is OK to 'leak' the real jid I’d prefer to use that. In MIX channels I’d be OK with using the stable id that MIX provides. But semi anon mucs and their unstable nicks are a pain. I don’t want to join as 'daniel' and get notifications about historic mentions of another 'daniel' Somewhat related; I had the issue in Conversations the other day where someone joined a muc as 'user' and had historic messages show up as sent by him that were really send by another 'user'. I’m really looking forward to having stable ids in MIX. cheers Daniel P.S.: In regards to actually rewording of that XEP and to make it agnostic towards MIX vs MUC it should probably mention that people should prefer 'a stable JID if available' where 'available' includes 'safe to leak' Am Do., 7. März 2019 um 08:47 Uhr schrieb JC Brand : > > Hi everyone > > In section 3.2 of XEP-0372, the groupchat example includes the real JID of the > participant, instead of their room JID. > > See https://xmpp.org/extensions/xep-0372.html#usecase_mention > > For anonymous or semi-anonymous rooms this is a privacy leak. > > Is there any particular reason why the room JID is not used, and is there a > use-case where one would want to NOT use the room JID, but instead use the > real > JID of the participant? > > Regards > JC > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
[Standards] XEP-0372 References: Real JID used for groupchat messages
Hi everyone In section 3.2 of XEP-0372, the groupchat example includes the real JID of the participant, instead of their room JID. See https://xmpp.org/extensions/xep-0372.html#usecase_mention For anonymous or semi-anonymous rooms this is a privacy leak. Is there any particular reason why the room JID is not used, and is there a use-case where one would want to NOT use the room JID, but instead use the real JID of the participant? Regards JC ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Is the World Ready for Compliance Suites 2019?
* Guus der Kinderen [2019-03-07 09:26]: > I'm very much in favor of not applying changes to the 2019 suite that can > wait for the 2020 edition. Alright, I'm convinced. Let's not further delay XEP-0412, and then let's hope client implementors will move away from the horrible mess that the 0066 hack is until October 2019, so that the problem will have solved itself by then. Georg signature.asc Description: PGP signature ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Is the World Ready for Compliance Suites 2019?
I'm very much in favor of not applying changes to the 2019 suite that can wait for the 2020 edition. On Thu, 7 Mar 2019 at 08:39, Daniel Gultsch wrote: > Am Mi., 6. März 2019 um 21:07 Uhr schrieb Georg Lukas : > > Example 1: "Modern" Use of OOB for Inline Images > > > > https://xmpp.org/theme/images/xmpp-logo.svg > > > > https://xmpp.org/theme/images/xmpp-logo.svg > > > > > > > > While XEP-0066 is less than ideal for the purpose of embedding images, > > and the body=url requirement isn't written down anywhere, it is > > something that client developers should know about, at least to > > implement it on the receiving side. > > Independently of whether or not you want the Compliance Suite to > become a document describing the quirks of a particular client (which > I don’t think is a good idea) I'd wait with those modifications for > the 2020 compliance suite. > Just get the 2019 out now and then start working on 2020. > > That’s the thing about the compliance suites. There will always be one > more new thing that should be documented. But at some point we will > have to decide that we are done for the year. That's why we are > planning on doing this every year. > > For the future I'd actually suggest that we do some kind of 'feature > freeze' in ~October and then spend the remainder of the year clearing > up the wording and getting it to Draft. > > cheers > Daniel > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
Re: [Standards] Is the World Ready for Compliance Suites 2019?
XEP-0385 is a travesty. On Thu, 7 Mar 2019, 12:09 Timothée Jaussoin, wrote: > What about using a proper XEP like SIMS ( > https://xmpp.org/extensions/xep-0385.html) for that case? > > This look like a hack to me. > Le 06/03/2019 à 22:05, Georg Lukas a écrit : > > * Tedd Sterr [2019-03-06 > 21:30]: > > Naysayers are invited to comment now, or forever hold their piece. > > because I love to be the naysayer, here is one: > > "Modern" clients are using a small subset of XEP-0066, namely §3, to > communicate inline images in messages. A small subset of those clients, > furthermore, requires the value to be equal to the message > for this to work, apparently to enforce compatibility with legacy > clients. > > Example 1: "Modern" Use of OOB for Inline Images > > https://xmpp.org/theme/images/xmpp-logo.svg > > https://xmpp.org/theme/images/xmpp-logo.svg > > > > While XEP-0066 is less than ideal for the purpose of embedding images, > and the body=url requirement isn't written down anywhere, it is > something that client developers should know about, at least to > implement it on the receiving side. > > > Georg > > > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > > ___ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > ___ > ___ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org ___
