Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
On the other hand you rely on 3rd party services for the authentication that may also process the data in a manner that your your users may not want to. For example let me assume that instead of password you use google (gmail etc etc) for authentication in your app then:
You enforce your users to have google account in order to use your app.
You make your user to let google know that use your app, an information that the users may not want to give into google. Also google may use it in order to provide more ads to your users that also users may not want to.
Thank you. Though the first one: most people already use these services. Not just google. Say for example, Iβm an iOS dev and thus Sign In with Apple works cause for you to download the app, you already have an Apple ID. So providing multiple SDKs for that purpose: sign in with Google, Huawei, Twitter, Facebook, phone number, github, etc etc. For example this platform already implements that. You can sign in/up using either twitter or GitHub only.
On info privacy, ππΎ Thatβs awesome. Thank you. Though, cookies may still be a sellout?
Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
And because also via cookies google for example, may know that a user uses your app by giving also the authentication confirmation via OAuth also aids google to confirm its targeting.
Greedings I am Dimitrios Desyllas aka pc_magas.
I am a php software engineer in e-table.
I am interested in privacy enhancing technologies, cryptography and reverse engineering.
Location
Acharnes, Greece
Education
MSc at Digital Systems Security at Univercity Of Peireus
Pronouns
Yo Wazz up bro!
Work
Volunteer Sysadmin at ELLAK of Cyprus - open for opportunities.
On the other hand you rely on 3rd party services for the authentication that may also process the data in a manner that your your users may not want to. For example let me assume that instead of password you use google (gmail etc etc) for authentication in your app then:
Thank you. Though the first one: most people already use these services. Not just google. Say for example, Iβm an iOS dev and thus Sign In with Apple works cause for you to download the app, you already have an Apple ID. So providing multiple SDKs for that purpose: sign in with Google, Huawei, Twitter, Facebook, phone number, github, etc etc. For example this platform already implements that. You can sign in/up using either twitter or GitHub only.
On info privacy, ππΎ Thatβs awesome. Thank you. Though, cookies may still be a sellout?
And because also via cookies google for example, may know that a user uses your app by giving also the authentication confirmation via OAuth also aids google to confirm its targeting.
By google I mean any service that offers tagreted advertisement.