public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft
Date: Tue, 1 Sep 2015 23:28:28 +0100	[thread overview]
Message-ID: <CADr=VrRbZXJ=6Z4AKHzYiC4hv90z=Gb+HUgN-o1KhTGPegN2pw@mail.gmail.com> (raw)
In-Reply-To: <CAAt2M1_qSs9UJ+sqjnvvmx7X29THW1jOFF4DjDbfzLLb+zSRTg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1645 bytes --]

Your points are interesting, but they are covered:

https://drive.google.com/file/d/0BwEbhrQ4ELzBMVFxajNZa2hzMTg/view?usp=sharing

Your general point: "Better just put everything in public domain" is the
reason why Bitcoin works, but taken to the extreme it is an argument
against attempts to obfuscate transaction ownership.

Regards,

Ahmed

On Tue, Sep 1, 2015 at 11:20 PM, Natanael <natanael.l@gmail.com> wrote:

>
> Den 2 sep 2015 00:03 skrev "Btc Drak via bitcoin-dev" <
> bitcoin-dev@lists.linuxfoundation.org>:
> >
> > I think it gets worse. Who are the copyright owners (if this actually
> > applies). You've got people publishing transaction messages, you've
> > got miners reproducing them and publishing blocks. Who are all the
> > parties involved? Then to take pedantry to the next level, does a
> > miner have permission to republish messages? How do you know? What if
> > the messages are reproducing others copyright/licensed material? It's
> > not possible to license someone else's work. There are plenty rabbit
> > holes to go down with this train of thought.
>
> Worse yet - transaction malleability creates derative works with multiple
> copyright holders (the original one, plus the author of the modification).
> Is that even legal to do? What to do if a miner unknowingly accepts an
> illegally modified transaction in a block? And can he who modified it ALSO
> sue anybody replicating the block for infringement?
>
> Better just put everything in public domain, or the closest thing to it
> you can get. Copyright in the blockchain is essentially the DVDCSS illegal
> prime mess all over again, but in a P2P network.
>

[-- Attachment #2: Type: text/html, Size: 2771 bytes --]

  reply	other threads:[~2015-09-01 22:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 13:30 [bitcoin-dev] Open Block Chain Licence, BIP[xxxx] Draft Ahmed Zsales
2015-09-01 13:43 ` Milly Bitcoin
2015-09-01 13:50 ` Bryan Bishop
2015-09-01 15:11   ` Ahmed Zsales
2015-09-01 16:05 ` Natanael
2015-09-01 17:39 ` Luke Dashjr
2015-09-01 18:12 ` Btc Drak
2015-09-01 19:36   ` Ahmed Zsales
2015-09-01 21:36     ` Milly Bitcoin
2015-09-01 22:02       ` Ahmed Zsales
2015-09-01 22:42         ` Milly Bitcoin
2015-09-01 23:21           ` Ahmed Zsales
2015-09-01 23:40             ` Milly Bitcoin
2015-09-01 22:02     ` Btc Drak
2015-09-01 22:11       ` Ahmed Zsales
2015-09-01 22:47         ` Btc Drak
2015-09-01 22:20       ` Natanael
2015-09-01 22:28         ` Ahmed Zsales [this message]
2015-09-01 21:51 ` Wladimir J. van der Laan
2015-09-01 23:39 ` hurricanewarn1
2015-09-02  8:56 ` Warren Togami Jr.
2015-09-02 20:28   ` Ahmed Zsales
2015-09-02 20:58     ` Milly Bitcoin

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='CADr=VrRbZXJ=6Z4AKHzYiC4hv90z=Gb+HUgN-o1KhTGPegN2pw@mail.gmail.com' \
    --to=ahmedzsales18@gmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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