@yarmo What about displaying your contact details on an Epaper Business Card ? https://www.paulschow.com/2016/08/epaper-business-card.html

@arran

@Doudouosm @yarmo Even better, render the QR code the epaper card 😂

Thats a cool project

@yarmo Thanks! Exactly, I have a couple screenshots or the QR codes on my homrscreen for different purposes - Eg work and hobbies.

@edavies @arran that's a valid point, curious to the answer. I probably wouldn't put my email in there anyway, just a link to my website.

@edavies @yarmo

Definitely open to suggestions to make this more private! Thanks for your concern.

So using a fragment identifier, it's guaranteed it won't be sent to the web server?

@edavies @yarmo

I did some research and I will make this change today.

Thanks for pointing it out, it's a big help

@arran @edavies @yarmo @Doudouosm > just another centralized webshit instead of encoding vcard into a qr code directly

@L29Ah Agreed for the simple use case. However, there's no reason an application can't ignore the web site and use the “https://qcard.link/?v=” prefix simply to identify the Q code as a base64-encoded vcard. I.e., treat it as a URI rather than a URL.

@arran @yarmo @Doudouosm

@edavies @L29Ah @yarmo @Doudouosm

That's exactly why I chose the format, here's an example of creating one in python:

https://codeberg.org/arran/qcard/src/branch/master/examples/QCardGeneration.md

@edavies @L29Ah @yarmo @Doudouosm

An example of decoding the URL is also in the readme.

https://codeberg.org/arran/qcard

@arran @yarmo Excellent, thanks for that.

Not quite a guarantee but a strong pointer that the fragment should not be sent, RFC 3986 section 3.5 says: “…instead, the fragment identifier is separated from the rest of the URI prior to a dereference, and thus the identifying information within the fragment itself is dereferenced solely by the user agent, regardless of the URI scheme.” The surrounding text gives useful context.

@edavies @yarmo

Updated, now we're using the Fragment Identifier!

@edavies @arran @yarmo

I'm confused why it needs to go to a server at all - couldn't all data be embedded in the code, e.g. like with https://www.qr-code-generator.com/solutions/vcard-qr-code/ ?

@raboof @edavies @yarmo

You're right, technically it could be - But I found when testing many QR apps don't recognise it, so I opted for a client side web approach for ubiquity.

It also doesn't force the recipient into saving the contact data on their phone, if they just wanted their email for example.

@L29Ah

@vv01f Thanks. It's private in regards to it's all client side without a server collecting the any contact data.