public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Peter Todd <pete@petertodd.org>
To: Gregory Maxwell <gmaxwell@gmail.com>, Mike Hearn <mike@plan99.net>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] patents...
Date: Mon, 19 May 2014 20:46:26 +0200	[thread overview]
Message-ID: <4f52185b-7fc3-4802-9ce5-824f9569c2bd@email.android.com> (raw)
In-Reply-To: <CAAS2fgRhEJUT4JEXtZSqnNnBV=tLFD4qjLFOQpeA-V2jA_UtHg@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256



On 19 May 2014 20:43:15 CEST, Gregory Maxwell <gmaxwell@gmail.com> wrote:

>There are other defensive approaches which are interesting than hoping
>to use patents as a counter attack: For one— filing a patent gets the
>work entered in the only database that USPTO examiners are
>_guaranteed_ to consult when doing a prior art search, so it may have
>a fighting chance of precluding someone else patenting the same
>material later (they may also search the internet and use other
>resources, but they're guaranteed to consult the existing patents and
>applications).

Interesting. Is that to say a viable strategy would be to apply for patents and let the application lapse?
-----BEGIN PGP SIGNATURE-----
Version: APG v1.1.1

iQFQBAEBCAA6BQJTelGCMxxQZXRlciBUb2RkIChsb3cgc2VjdXJpdHkga2V5KSA8
cGV0ZUBwZXRlcnRvZGQub3JnPgAKCRAZnIM7qOfwhQPlCACjJgJEyMYMtF+/dJJh
TgWfVuE7E7QmwgWoQMBo7/5LgO1W5PQt9d3jfQ7gkrdCqTWs4HtA3lcgjdeEQ6ZW
QvMFG5/xITVi85v2zlE9CteQZXLBTSI+J7VlkjqnJeftQkklvGjiDtNfaDDsTacV
ZNem06V4fmBxNgzqmit2Roilp+NMQb2iM9Ofkr5FbI0cT/kzD/IJd2+Crqsu/uDU
8r2YQY0bbEf2wqxVdq5TSf1rFqqnWKHB3lD1GGRJ8n5BciBmysZL43jct8YABSgi
BHFpJP2ii7gz076mRiBb+KwCo+1xKUYNpsJk1m7HND7PjqkXps+JHiNaWdr9vAxx
raFO
=L1oX
-----END PGP SIGNATURE-----




  reply	other threads:[~2014-05-19 18:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-17 15:31 [Bitcoin-development] Paper Currency Jerry Felix
2014-05-17 15:45 ` Matt Whitlock
2014-05-17 16:07 ` Chris Pacia
2014-05-17 16:40   ` Gregory Maxwell
2014-05-18 11:47     ` Alex Kotenko
2014-05-18 12:14       ` Andreas Schildbach
2014-05-18 12:51         ` Alex Kotenko
2014-05-19 13:06           ` Brooks Boyd
2014-05-19 13:50             ` Alex Kotenko
2014-05-18 13:50       ` Natanael
2014-05-18 18:47         ` Alex Kotenko
2014-05-18 20:10           ` Natanael
2014-05-19 10:26             ` Alex Kotenko
2014-05-19 12:55       ` Sergio Lerner
2014-05-19 13:34         ` Martin Sip
2014-05-19 13:53         ` Alex Kotenko
2014-05-19 14:47         ` [Bitcoin-development] patents Adam Back
2014-05-19 15:09           ` Mike Hearn
2014-05-19 18:27             ` Peter Todd
2014-05-19 18:40               ` Mike Hearn
2014-05-19 18:43             ` Gregory Maxwell
2014-05-19 18:46               ` Peter Todd [this message]
2014-05-19 18:49               ` Mike Hearn
2014-05-19 22:15             ` Bernd Jendrissek
2014-05-20 10:30           ` Jeff Garzik
2014-05-18 13:50 ` [Bitcoin-development] Paper Currency Andreas Schildbach
2014-05-19 12:21 ` Mike Hearn
2014-05-19 18:20   ` Justus Ranvier
2014-05-19 18:39     ` Peter Todd

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4f52185b-7fc3-4802-9ce5-824f9569c2bd@email.android.com \
    --to=pete@petertodd.org \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=gmaxwell@gmail.com \
    --cc=mike@plan99.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox