For facebook users:
http://www.facebook.com/FlowerStandard
On Tue, Dec 4, 2012 at 11:18 AM, Pars Mutaf wrote:
> Dear all,
>
> FYI, I designed the following standard myself. It completes IETF RFC 3161.
>
> www.flower-standard.org
>
> Cheers,
> Pars Mutaf
>
On Tue, Dec 4, 2012 at 11:18 AM, Pars Mutaf wrote:
> Dear all,
>
> FYI, I designed the following standard myself. It completes IETF RFC 3161.
>
> www.flower-standard.org
>
> Cheers,
> Pars Mutaf
>
More info about the design rational. I provide this information h
on, I personally don't know
how to design it (or, which design might be the best one). I hope this would
be
of interest to the IETF. Comments appreciated either here or please
subscribe to the following mailing list:
https://www1.ietf.org/mailman/listinfo/humanresolvers
Thanks
pars mutaf
Hello,
On 25 Sep 2007 16:33:32 -, John Levine <[EMAIL PROTECTED]> wrote:
>
> >1. The querier user types the target user's "human name" (as if he were
> > consulting a phonebook), or a pseudoynm.
> >2. The pairing request is forwarded to the target phone.
> >3. The query, along with the queri
On 9/25/07, Pars Mutaf <[EMAIL PROTECTED]> wrote:
>
> Hello,
>
> On 25 Sep 2007 16:33:32 -, John Levine <[EMAIL PROTECTED]> wrote:
> >
> > >1. The querier user types the target user's "human name" (as if he were
> > > consulti
On 9/25/07, Daniel Senie <[EMAIL PROTECTED]> wrote:
>
> At 03:02 PM 9/25/2007, Pars Mutaf wrote:
>
>
>
> On 9/25/07, *Pars Mutaf* <[EMAIL PROTECTED]> wrote:
> Hello,
>
> On 25 Sep 2007 16:33:32 -, John Levine < [EMAIL PROTECTED]> wrote:
> >
Hi Suresh,
On 9/25/07, Suresh Krishnan <[EMAIL PROTECTED]> wrote:
>
> Hi Pars,
>
> Pars Mutaf wrote:
> > Model of operation
> >
> > 1. The querier user types the target user's "human name" (as if he were
> >consulting a phonebook), o
On 9/25/07, Daniel Senie <[EMAIL PROTECTED]> wrote:
>
> At 03:25 PM 9/25/2007, Pars Mutaf wrote:
>
>
>
> On 9/25/07, *Daniel Senie* <[EMAIL PROTECTED]> wrote:
> At 03:02 PM 9/25/2007, Pars Mutaf wrote:
>
>
>
> On 9/25/07, Pars Mutaf <[EMAIL PRO
On 9/26/07, John L <[EMAIL PROTECTED]> wrote:
>
> >> I have a list of 250,000 people here (scraped off web sites) to whom
> >> I'd just love to make recorded phone calls. Can I use your protocol
> >> to ask them all if it's OK? If not, why not, and how are you going to
> >> stop me?
> >
> > Using
the query
and avoid solving an unnecessary Turing test.
On 9/26/07, Bill McQuillan <[EMAIL PROTECTED]> wrote:
>
>
> On Tue, 2007-09-25, Pars Mutaf wrote:
>
> > On 9/25/07, Suresh Krishnan <[EMAIL PROTECTED]> wrote:
> > Pars Mutaf wrote:
> >> Mod
On 9/26/07, John L <[EMAIL PROTECTED]> wrote:
>
> > You can enable this protocol when you need to pair your phone
> > with another user's phone. Because manual exchange is difficult.
>
> Now I don't understand what problem you are trying to solve. If the two
> phones are physically close to each o
On 9/26/07, John L <[EMAIL PROTECTED]> wrote:
>
> >>> Using a Turing test (CAPTCHA) for example.
> >>> http://en.wikipedia.org/wiki/Captcha
> >>
> >> There are many well known ways to defeat CAPTCHAs, unfortunately.
> >
> > It depends on the CAPTCHA you are using and your application.
> > You may w
On 9/26/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> >Please refer to my first mail. There are three basic problems that I
> see.
>
> >1. You don't want to publish your private information
> >2. Manual exchange is difficult
>
> Ridiculous! I give my phone to the other person and ask
> them
Regarding the CAPTCHA discussion I would like to clarify one point:
CAPTCHA is today used for against ballot stuffing or casual trolling/spam.
In the proposed pairing protocol, CAPTCHA (or perhaps other solutions)
defeats someone who wants to disturb you by displaying a bogus pairing
message on y
Hello,
A statement about IP addressable mobile nodes may be useful ?
(since we expect billions of them).
Regards,
pars
On Nov 12, 2007 5:30 PM, Thomas Narten <[EMAIL PROTECTED]> wrote:
> Hi.
>
> A little more background/context that got me here.
>
> My original thinking was to do something like
15 matches
Mail list logo