drac89

man... I was programming 8080 at school... time passing so fast

From the blog post I've recently read; https://thelocalstack.eu/posts/linkedin-identity-verificatio...

1. Request your data. Email idv-privacy@withpersona.com or privacy@withpersona.com. Under GDPR, they have 30 days to respond.

2. Request deletion. The verification is done. LinkedIn already has the result. There is no reason for Persona to keep your passport scan and facial geometry on their servers. Ask them to delete it.

3. Contact their DPO. dpo@withpersona.com — that’s their Data Protection Officer. If you want to object to them using your documents as AI training data under “legitimate interests,” this is where you do it.

4. Think twice before verifying. That blue badge might not be worth what you’re trading for it. A checkmark is cosmetic. Biometric data is forever.

maybe

It's useful in case like if you ever need to fill out a PR template with what you did or list the changes, it becomes so much easier. You don’t even have to remember exactly what was changed it’s all right there in the commit message.

With structured comments, you can even use the AI to fill out the PR template easily and precisely.

And the best part is, if you ever need to fill out a PR template with what you did or list the changes, it becomes so much easier. You don’t even have to remember exactly what was changed, it’s all right there in the commit message.

I agree maybe not adding the ticket link is better if you know that the system might not be available in the future.

You can not avoid it all the time but maybe It's better to use the PR description for that purpose.

Looks beautiful. And the best part is, if you ever need to fill out a PR template with what you did or list the changes, it becomes so much easier. You don’t even have to remember exactly what was changed, it’s all right there in the commit message.

Nope

The style of the video is very similar to my dreams.

Does anyone have similar feeling?

if anyone interested here is the Github link to the source code => https://github.com/tjukanovt/tjukanovt.github.io/blob/master...

You can start from wikipedia[1] and especially checkout references part.

Unfortunately as you go deep it's really hard to find articles in layman's language. I think it's because articles in layman's language are more targeting the average reader.

I hope someone can comment with a good article.

[1] https://en.wikipedia.org/wiki/Coronavirus_disease_2019

"Apple is like a ship with a hole in the bottom, leaking water and my job is to get the ship pointed in the right direction." - Gil Amelio

Seems similar for Linkedin but I don't think they will be able to find a "Steve Jobs" kind of strategy.

They get the power to change it something else.. something that could work or not failing ... in the end It wasn't a failed project anymore.

(sorry for the late comment)

What Do You Do With A Failed Product? -You could Open Source it. That's what I did.

http://showdiscontent.com --- here is some pictures about what happening..

I know, I have to work harder as always, even a rock star has always to learn something ... but my point is that many bad designers are dribbbler and many good designers sell their invites ...

I will work harder ... thank you...