unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jambunathan K <kjambunathan@gmail.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: rms@gnu.org, lennart.borgman@gmail.com, emacs-devel@gnu.org,
	monnier@iro.umontreal.ca, carsten.dominik@gmail.com,
	julien@danjou.info
Subject: Re: Google modules integration
Date: Sun, 12 Sep 2010 15:04:03 +0530	[thread overview]
Message-ID: <8139tfi9v8.fsf@gmail.com> (raw)
In-Reply-To: <AANLkTimp4c22snqpZ0Q0r=rQAYeh9HFNZfYr2eD3hdYw@mail.gmail.com> (Juanma Barranquero's message of "Sun, 12 Sep 2010 03:42:40 +0200")


Juanma Barranquero <lekktu@gmail.com> writes:

> On Sun, Sep 12, 2010 at 02:36, Glenn Morris <rgm@gnu.org> wrote:
>
>>    (b) using the Maps APIs. In this case, you understand and agree that
>>    Google will treat your use of the Maps APIs as acceptance of the Terms
>>    from that point onwards.
>
> IANAL, but it seems quite fishy. Assume you argue that you used the
> APIs without reading that. Yeah, I know, ignorantia juris non excusat,
> but that's not the law, that's a license agreement. So, what would be
> your crime, "using an API without reading the license"? :-)
>
> (What I mean is, has someone really tried to defend that kind of
> license on a tribunal? Did it work?)

I agree that it is infeasible or futile for a big corporation to run
behind individuals (possibly of no 'consequence'). That doesn't preclude
the possibility that it wouldn't or couldn't happen as a practical
deterrent or what the limits of liability would be. (If I can pay more
damages, will they claim more damages? Don't know ...)

I believe there are two things that came up in this thread worth making
a note:

1. Using anonymous proxies so that Google couldn't nail the individual
   user [1].

2. Google using the users to beef up it's database and there being no
   explicit policy on whether these databases would continue to remain
   publicly accessible [2].

That said, plugins under discussion are tools. When these tools are so
simple as to be built with limited effort, withholding of the
availability of the tool within the GNU's official distribution is
unlikely to cause these tools to be hacked or easily available
elsewhere.

Let me also add that, as a small-time Emacs user, it is my moral
obligation that I live without these tools from within the official
distribution or package servers. I am willing to suffer some
inconvenience for locating the package, building it myself or paying for
it as a token of appreciation to how much value I have derived from
software that comes from GNU's stable.

There goes my 2 cents to the donation box :-).

Jambunathan K.




  parent reply	other threads:[~2010-09-12  9:34 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 20:23 Google modules integration Julien Danjou
2010-09-09 22:25 ` Stefan Monnier
2010-09-09 22:56   ` Lennart Borgman
2010-09-09 23:36     ` Ted Zlatanov
2010-09-09 23:43     ` Jambunathan K
2010-09-10  6:36       ` Glenn Morris
2010-09-11  5:29         ` Richard Stallman
2010-09-12  0:36           ` Glenn Morris
2010-09-12  1:42             ` Juanma Barranquero
2010-09-12  2:29               ` Óscar Fuentes
2010-09-12  9:34               ` Jambunathan K [this message]
2010-09-12 10:12                 ` Jeff Clough
2010-09-13  2:07                   ` Richard Stallman
2010-09-12 17:27               ` Stephen J. Turnbull
2010-09-13  7:18                 ` Richard Stallman
2010-09-12 11:24             ` Richard Stallman
2010-09-12 18:35               ` Glenn Morris
2010-09-13  7:18                 ` Richard Stallman
2010-09-13 16:22                   ` Jambunathan K
2010-09-14  8:16                     ` Richard Stallman
2010-09-10  6:29     ` Julien Danjou
2010-09-10  6:43       ` Glenn Morris
2010-09-11  5:29       ` Richard Stallman
2010-09-11 12:28         ` Stefan Monnier
2010-09-12 11:23           ` Richard Stallman
2010-09-09 23:33   ` Sebastian Rose
2010-09-10  6:17   ` Julien Danjou
2010-09-10  8:30     ` Andreas Schwab
2010-09-10 11:00     ` Stefan Monnier
2010-09-11  5:30       ` Richard Stallman
2010-09-10  8:08 ` Andy Wingo
2010-09-10 11:26   ` Thierry Volpiatto
2010-09-13 14:36   ` James Cloos
2010-09-10 15:42 ` Richard Stallman
2010-09-10 17:47   ` Thomas Lord
2010-09-10 18:03     ` Chad Brown
2010-09-10 18:10       ` Thomas Lord
2010-09-11 15:50         ` Richard Stallman
2010-09-10 19:07       ` Sebastian Rose
2010-09-11 15:49         ` Richard Stallman
2010-09-11 20:03           ` Sebastian Rose
2010-09-11 15:50     ` Richard Stallman
2010-09-13 19:07       ` Thomas Lord
2010-09-13 19:09         ` Thomas Lord
2010-09-15  2:39           ` Richard Stallman
2010-09-14 12:38         ` Stephen J. Turnbull
2010-09-15  2:39         ` Richard Stallman
2010-09-11  5:38   ` Stephen J. Turnbull
2010-09-12 11:24     ` Richard Stallman
2010-09-12 17:21       ` Stephen J. Turnbull
2010-09-20  0:16         ` Richard Stallman
2010-09-21  5:40           ` Stephen J. Turnbull
2010-09-19  9:34 ` Julien Danjou
2010-09-21 16:01   ` Chong Yidong
2010-09-21 16:30     ` Julien Danjou
2010-09-21 16:50       ` Chong Yidong
2010-09-21 17:24         ` Thierry Volpiatto
2010-09-21 17:25       ` Sebastian Rose

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=8139tfi9v8.fsf@gmail.com \
    --to=kjambunathan@gmail.com \
    --cc=carsten.dominik@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=julien@danjou.info \
    --cc=lekktu@gmail.com \
    --cc=lennart.borgman@gmail.com \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.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.
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).