unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Elias Mårtenson" <lokedhs@gmail.com>
To: rms@gnu.org
Cc: schwab@suse.de, Joakim Verona <joakim@verona.se>,
	emacs-devel@gnu.org, Lars Magne Ingebrigtsen <larsi@gnus.org>,
	m@ahungry.com
Subject: Re: Using xwidget to play youtube videos
Date: Sun, 14 Feb 2016 20:21:21 +0800	[thread overview]
Message-ID: <CADtN0WLUkXEy6j_fKVyDvfRexSqaf-KKL4RhW9-1Ta69=WPrJA@mail.gmail.com> (raw)
In-Reply-To: <E1aUcC8-0005kb-6l@fencepost.gnu.org>

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

On 13 Feb 2016 23:34, "Richard Stallman" <rms@gnu.org> wrote:

> In general, breaking a contract is not illegal.

I don't know if there are any lawyers on this list, but reading this thread
raised some questions for me.

In this case (user using youtube-dl to get the underlying link) is there
even a contract to break? The user certainly never saw a contract.

Try as I may, the best I can come up with is Google having a case against
the maker of youtube-dl for creating a tool to facilitate copyright
infringement. But then again, the copyrights are owned by the content
creators, not Google.

Am I correct in this?

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

  reply	other threads:[~2016-02-14 12:21 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-09  5:58 Using xwidget to play youtube videos Lars Ingebrigtsen
2016-02-09  9:38 ` joakim
2016-02-09 22:55   ` Lars Ingebrigtsen
2016-02-10 14:14     ` Richard Stallman
2016-02-10 14:41       ` Andreas Schwab
2016-02-11  5:18         ` Marcin Borkowski
2016-02-11  9:51           ` Andreas Schwab
2016-02-11 18:21           ` Richard Stallman
2016-02-21 17:17             ` Nix
2016-02-22  3:56               ` Lars Ingebrigtsen
2016-02-22  9:27                 ` joakim
2016-02-22 16:26                   ` Eli Zaretskii
2016-02-23  1:24                   ` Lars Ingebrigtsen
2016-02-22 16:09                 ` Eli Zaretskii
2016-02-22 18:59                   ` joakim
2016-02-22 18:59                   ` John Wiegley
2016-02-12  3:43           ` Matthew Carter
2016-02-12 13:05             ` Marcin Borkowski
2016-02-13 15:33               ` Richard Stallman
2016-02-14 12:21                 ` Elias Mårtenson [this message]
2016-02-14 12:33                   ` Dmitry Gutov
2016-02-14 15:32                     ` Elias Mårtenson
2016-02-15 10:26                   ` Richard Stallman
2016-02-15 10:42                     ` Marcin Borkowski
2016-02-11  3:48       ` Lars Ingebrigtsen
2016-02-11 18:21         ` Richard Stallman
2016-02-11 18:46           ` joakim
2016-02-12 12:34             ` Richard Stallman
2016-02-09 16:31 ` raman
2016-02-09 22:59   ` Lars Ingebrigtsen
2016-02-10  8:03     ` joakim
2016-02-09 16:51 ` Eli Zaretskii
2016-02-09 23:00   ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to='CADtN0WLUkXEy6j_fKVyDvfRexSqaf-KKL4RhW9-1Ta69=WPrJA@mail.gmail.com' \
    --to=lokedhs@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=larsi@gnus.org \
    --cc=m@ahungry.com \
    --cc=rms@gnu.org \
    --cc=schwab@suse.de \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).