- From: Marcos Caceres <marcos@marcosc.com>
- Date: Fri, 28 Jun 2019 00:15:26 +1000
- To: Ian Jacobs <ij@w3.org>
- Cc: Adrian Hope-Bailie <adrian@coil.com>, Payments WG <public-payments-wg@w3.org>
> On 27 Jun 2019, at 23:14, Ian Jacobs <ij@w3.org> wrote: > > Hi Marcos, > >> On Jun 27, 2019, at 12:54 AM, Marcos Caceres <marcos@marcosc.com> wrote: >> >> .. for instance, it's not necessary to query ~200 data-points from the device to create a fingerprint: instead, asking the browser to give a unique identifier for the purpose of payment that the user controls would achieve the same goal, and prevent brittle fingerprinting... that's privacy preserving, keeps users in control, and should give payment providers the assurance they need to mitigate fraud aspects. > > Do you have any pointers to standards work going on in that space? Something like Apple’s IDFA and Android’s AAID. > Or even browser-specific work in that space? We don’t provide anything like it in browsers, but we could for payment requests potentially. > Thanks! > > ian > > -- > Ian Jacobs <ij@w3.org> > https://www.w3.org/People/Jacobs/ > Tel: +1 718 260 9447 > > > >
Received on Thursday, 27 June 2019 14:15:57 UTC