Feature Request: Add support for XMPP identifiers #1

errhammr commented 2020年11月13日 16:21:14 +01:00

I'm using XMPP as my preferred chat platform. I'd love to add my XMPP ID to my qCard. The vCard 3.0 standard seems to support two methods of including such an identifier:

• IMPP
• X-JABBER

I don't know much about the vCard standard or the best way to implement this.

I'm using XMPP as my preferred chat platform. I'd love to add my XMPP ID to my qCard. The vCard 3.0 standard seems to support two methods of including such an identifier: * IMPP * X-JABBER I don't know much about the vCard standard or the best way to implement this.

arran commented 2020年11月13日 17:19:48 +01:00

Hey,

Thanks for making a feature request, I'm happy to add this.

Hey, Thanks for making a feature request, I'm happy to add this.

vv01f commented 2020年11月13日 17:23:49 +01:00

Remember that x-name values are not intended for general use and are unlikely to interoperate.

@errhammr if you want to transport that information reliably and cannot ensure the application on the receiving end (supporting a certain standard), better add it as e.g. a note note;quoted-printable:xmpp:user@domain.tld– maybe less convenient but should do the job. Best link to a (customized) website and give contact-specific information there, vcard should be rather small as should the content of qr codes.

a generator for the example X-JABBER is https://www.datlicht.de/wp/tools/qr-code-generator/ – just rarely applicatons will support that, you may test yours.
(although the UI takes them for the internal DB) thunderbird 68.* address book drops such information on import and also does not include im-adresses with VCF-export.

[Remember that x-name values are not intended for general use and are unlikely to interoperate.](https://tools.ietf.org/html/rfc6350) @errhammr if you want to transport that information reliably and cannot ensure the application on the receiving end (supporting a certain standard), better add it as e.g. a note `note;quoted-printable:xmpp:user@domain.tld`– maybe less convenient but should do the job. Best link to a (customized) website and give contact-specific information there, vcard should be rather small as should the content of qr codes. a generator for [the example](https://tools.ietf.org/html/rfc4770#section-3) `X-JABBER` is https://www.datlicht.de/wp/tools/qr-code-generator/ – just rarely applicatons will support that, you may test yours. (although the UI takes them for the internal DB) *thunderbird 68.\** address book drops such information on import and also does not include im-adresses with VCF-export.

errhammr commented 2020年11月13日 23:24:47 +01:00

I tested a bit with the Android default contacts app (LineageOS 17.1) and it uses the X-JABBER tag. For maximum portability a small web page with proper <a/> tags would probably be the best but then I wouldn't need qCard anyway.

I tested a bit with the Android default contacts app (LineageOS 17.1) and it uses the `X-JABBER` tag. For maximum portability a small web page with proper `<a/>` tags would probably be the best but then I wouldn't need qCard anyway.

arran commented 2020年12月29日 19:37:59 +01:00

Thank you both for your input, I really appreciate the points made - I'm torn..

As @vv01f has pointed out, Keeping the size of the QR Small for maximum readability is a priority, and I don't want to inundate the user with too many fields upon QCard creation.

However I would like to include XMPP and Matrix links, but am stuck on an implementation detail:

• What value would be set to the href attribute of the <a> tag?

Which leads me to believe, the already existing comment field is sufficient.

**Thank you both for your input, I really appreciate the points made - I'm torn..** As @vv01f has pointed out, Keeping the size of the QR Small for maximum readability is a priority, and I don't want to inundate the user with too many fields upon QCard creation. However I would like to include XMPP and Matrix links, but am stuck on an implementation detail: - What value would be set to the `href` attribute of the `<a>` tag? Which leads me to believe, the already existing `comment` field is sufficient.

arran commented 2020年12月29日 19:42:39 +01:00

I've now seen xmpp.org uses the following for tags:

<a href="xmpp:contact@example.com">XMPP</a>

Is this widely supported? I am not an XMPP user and not familiar.

I've now seen [xmpp.org](https://xmpp.org/about/xmpp-standards-foundation) uses the following for <a> tags: ```html <a href="xmpp:contact@example.com">XMPP</a> ``` Is this widely supported? I am not an XMPP user and not familiar.

errhammr commented 2020年12月29日 22:53:15 +01:00

@arran

I've now seen xmpp.org uses the following for tags:

<a href="xmpp:contact@example.com">XMPP</a>

Is this widely supported? I am not an XMPP user and not familiar.

I think this is correct. Popular Android clients like Conversations and it's various forks use the xmpp: URI like that.

@arran >I've now seen [xmpp.org](https://xmpp.org/about/xmpp-standards-foundation) uses the following for <a> tags: > >```html ><a href="xmpp:contact@example.com">XMPP</a> >``` > >Is this widely supported? I am not an XMPP user and not familiar. I think this is correct. Popular Android clients like Conversations and it's various forks use the `xmpp:` URI like that.

arran commented 2020年12月30日 12:48:44 +01:00

I've added the XMPP field under X-JABBER.

See b8badd1c01 if you're curious on implementation detials. 🐐

I've added the `XMPP` field under `X-JABBER`. See https://codeberg.org/arran/QCard/commit/b8badd1c01a49a5f000531b394aa82e94cf2ebc9 if you're curious on implementation detials. 🐐