Re: Call for Consensus: Anti-Fraud CG Charter

I support the charter.

--Andrew

On Tue, Feb 15, 2022 at 1:39 PM Ian Jacobs <ij@w3.org> wrote:

> Fine with the proposed change. Thanks!
>
> Ian
>
> > On Feb 15, 2022, at 2:19 PM, Steven Valdez <svaldez@google.com> wrote:
> >
> > I think that change to the charter seems reasonable. If the folks who
> have responded already are okay with the change, I can merge the change in
> and have it as part of the CfC.
> >
> > On Tue, Feb 15, 2022 at 3:14 PM Chris Wood <chriswood@cloudflare.com>
> wrote:
> > Following up on a message I sent to the use cases thread, I think it
> might be useful to slightly expand the Scope of Work section as follows:
> >
> > "The Community Group will discuss and document various forms of
> fraudulent activity on the web, as well as the properties of such
> activities that lend themselves to abuse, to establish a foundation for
> developing web APIs that assist in our mission. The focus is to enable
> scaled anti-fraud and solutions that are applicable across the ecosystem."
> >
> > Otherwise, the proposed charter looks like a reasonable start to me!
> >
> > Best,
> > Chris
> >
> >
> > On Tue, Feb 15, 2022 at 11:20 AM Zucker-Scharff, Aram <
> Aram.Zucker-Scharff@washpost.com> wrote:
> > Concur. Scope seems clear to me. Amendment for specific work items as a
> way to go forward also makes sense. I support the charter.
> >
> >
> >
> > -- Aram Zucker-Scharff
> >
> > The Washington Post
> >
> >
> >
> >
> >
> > From: Steven Valdez <svaldez@google.com>
> > Date: Tuesday, February 15, 2022 at 2:11 PM
> > To: Michael Tiffany <michael@humansecurity.com>
> > Cc: Ian Jacobs <ij@w3.org>, James Rosewell <james@51degrees.com>,
> public-antifraud@w3.org <public-antifraud@w3.org>
> > Subject: Re: Call for Consensus: Anti-Fraud CG Charter
> >
> > CAUTION: EXTERNAL SENDER
> >
> > re: abuse's meaning, Ian's reading is correct. Based on how wide the
> space is, the medium-term plan is to try sorting out more explicit use
> cases and looking into amending the charter based on that in the future.
> >
> >
> >
> > On Tue, Feb 15, 2022 at 2:05 PM Michael Tiffany <
> michael@humansecurity.com> wrote:
> >
> > +1. I particularly commend the wording scoping the mission. This mission
> statement strikes me as both ambitious and precise. Nicely done.
> >
> >
> >
> > On Tue, Feb 15, 2022 at 1:55 PM Ian Jacobs <ij@w3.org> wrote:
> >
> >
> >
> > > On Feb 15, 2022, at 12:52 PM, James Rosewell <james@51degrees.com>
> wrote:
> > >
> > > What does "abuse" mean in the context of the charter? Without a
> definition the "Goals" and "Scope of Work" sections are misaligned.
> >
> > The charter says: "Fraud and abuse can include web activity perpetrated
> by botnets, attackers impersonating users, unwanted traffic, and other
> activity that intends to deceive and harm users or compromise web services."
> >
> > I infer that the scope of work is therefore "activity that intends to
> deceive and harm users or compromise web services.”
> >
> > Ian
> >
> > >
> > > -----Original Message-----
> > > From: Ian Jacobs <ij@w3.org>
> > > Sent: 15 February 2022 18:38
> > > To: Steven Valdez <svaldez@google.com>
> > > Cc: public-antifraud@w3.org
> > > Subject: Re: Call for Consensus: Anti-Fraud CG Charter
> > >
> > > +1 to the charter. Thank you to the editors,
> > >
> > > Ian
> > >
> > >> On Feb 15, 2022, at 11:52 AM, Steven Valdez <svaldez@google.com>
> wrote:
> > >>
> > >> This email is to announce a Call for Consensus (CfC) on the
> Anti-Fraud CG Charter:
> > >>
> > >> https://antifraudcg.github.io/charter.html [antifraudcg.github.io]
> > >>
> > >> This charter would serve as an initial foundation for the anti-fraud
> community group and can be amended in the future as the state of the CG
> changes.
> > >>
> > >> This CfC will conclude in 14 days on March 1st, 2022. All feedback is
> encouraged on the charter, both positive support and any objections or
> request for changes. While non-responses by CG members implies no objection
> to the charter, the Chairs would prefer explicit support/feedback on the
> charter to make sure sufficient folks have reviewed/read the charter.
> Please provide feedback/support by replying to this thread (via
> public-antifraud@w3.org). If there is consensus for the charter, we'll
> adopt it at the end of the CfC for the March 4th meeting, otherwise we'll
> iterate on the feedback via the Github (
> https://github.com/antifraudcg/antifraudcg.github.io/blob/main/charter.html
> ).
> > >>
> > >> -Steven
> > >>
> > >> --
> > >>
> > >> Steven Valdez |       Chrome Privacy Sandbox |
> svaldez@google.com |    Cambridge, MA
> > >
> > > --
> > > Ian Jacobs <ij@w3.org>
> > > https://www.w3.org/People/Jacobs/ [w3.org]
> > > Tel: +1 917 450 8783
> > >
> > >
> > >
> > >
> > >
> > >
> > > This email and any attachments are confidential and may also be
> privileged. If you are not the named recipient, please notify the sender
> immediately and do not disclose, use, store or copy the information
> contained herein. This is an email from 51Degrees.mobi Limited, Davidson
> House, Forbury Square, Reading, RG1 3EU. T: +44 118 328 7152; E:
> info@51degrees.com; 51Degrees.mobi Limited t/as 51Degrees.
> > >
> >
> > --
> > Ian Jacobs <ij@w3.org>
> > https://www.w3.org/People/Jacobs/ [w3.org]
> > Tel: +1 917 450 8783
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> >
> >
> >
> >  Steven Valdez |
> >
> >  Chrome Privacy Sandbox |
> >
> >  svaldez@google.com |
> >
> >  Cambridge, MA
> >
> >
> >
> >
> >
> > --
> >
> >  Steven Valdez |       Chrome Privacy Sandbox |
> svaldez@google.com |    Cambridge, MA
>
> --
> Ian Jacobs <ij@w3.org>
> https://www.w3.org/People/Jacobs/
> Tel: +1 917 450 8783
>
>
>
>
>
>
>