maltfield

joined 1 year ago
[–] [email protected] 1 points 6 months ago (1 children)

oh, I got too excited. The instance sidebar says image uploads are available 4 weeks after account creation, though :(

[–] [email protected] 1 points 6 months ago

This is false.

In the case of the article, the image was never sent to other servers. In fact, that is the last thing it does.

[–] [email protected] 1 points 6 months ago (3 children)

How? I want to block my app from being able to upload images.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

Author here. A "KYC Selfie" is a selfie photo where you hold-up a State-issued photo-identity document next to your face. This is not a US-specific thing; it's also used in the EU.

I used to work for a bank in Europe where we used KYC seflies for authentication of customers opening new accounts (or recovering accounts from lost credentials), including European customers. Most KYC Selfies are taken with a passport (where all the information is on one-side), but if your ID has data on both sides then the entity asking you for the KYC seflie may require you to take two photos: showing both sides.

Some countries in the EU have cryptographic authentication with eIDs. The example I linked-to in the article is Estonia, who has made auth-by-State-issued-private-key mandatory for over a decade. Currently MEPs are deciding on an eID standard, which is targeting making eIDs a requirement for all EU Member States by 2016.

I recommend the Please Identify Yourself! talk at 37c3 about the state of eID legislation as of Dec 2023 (and how to learn from India, who did eID horribly wrong):

[–] [email protected] 1 points 6 months ago

They definitely should remove it, at least until moderation tools are available.

[–] [email protected] 1 points 6 months ago

That’s a great idea :) Maybe you can submit a feature request for this on GitHub?

[–] [email protected] 1 points 6 months ago

Better to publish such issues on a public website than let it get buried in matrix. People other than devs & instance admins need to be aware of the risks that they’re taking when using Lemmy.

[–] [email protected] 2 points 6 months ago* (last edited 6 months ago)

Under GDPR you can just send a request for them to send you all of the data that they’ve stored about you on their backend.

[–] [email protected] 1 points 6 months ago (1 children)

It's also hard for admins to delete it from their own instance:

[–] [email protected] 1 points 6 months ago

If you want this to be fixed, please tell the devs on the relevant GitHub Ticket

For some reason they think I'm literally the only person who wants it? At least that's what they keep saying as the reason for why they won't work on it.

[–] [email protected] 1 points 6 months ago

It would be possible to locally save the delete tokens of every image you upload, so that you can request that they be removed later. I don’t know of any clients that can do this yet, though (if someone knows of one, feel free to mention it).

@[email protected] I'm told Boost does this.

view more: next ›