From: Aaron Wolf <wolftune@riseup.net>
To: John Sullivan <johns@fsf.org>
Cc: Mike Gerwitz <mtg@gnu.org>, libreplanet-discuss@libreplanet.org
Subject: Re: Adding [A]GPLv3+ code to Quake-based code base
Date: Thu, 31 Aug 2017 12:49:03 -0700 [thread overview]
Message-ID: <fa77bb71-3b55-beb8-e252-61f1f0b436fc@riseup.net> (raw)
In-Reply-To: <87pobbikuf.fsf@wjsullivan.net>
On 08/31/2017 12:43 PM, John Sullivan wrote:
> Aaron Wolf <wolftune@riseup.net> writes:
>
>> Thanks. But damnit. Sounds like the AGPL has an unfortunate flaw here.
>> Is there not even a requirement that people get any notice that the
>> software being run is under AGPL at all, unless it's modified??
>
> Put a source link in the code. Then if anyone removes it in the version
> they are offering over the network, it's a modified version. AFAICT,
> most AGPL programs have such notices (not sure why you wouldn't).
>
> -john
>
Yes, of course. And you mean explicitly *a user-facing source-link in
the UI* (a link in just the source code is no good if you don't have the
source code). But this still means that we can have this bad (though
unlikely) situation:
1. Service A goes up with code under AGPL
2. Service B goes up with unmodified code
3. Source host goes down
4. Service B remains running indefinitely with no source available, and
service B can refuse to provide it
In fact, a single
_______________________________________________
libreplanet-discuss mailing list
libreplanet-discuss@libreplanet.org
https://lists.libreplanet.org/mailman/listinfo/libreplanet-discuss
prev parent reply other threads:[~2017-08-31 19:49 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-29 9:53 Adding [A]GPLv3+ code to Quake-based code base Lyberta
2017-08-29 16:12 ` Aaron Wolf
2017-08-29 21:58 ` Lyberta
2017-08-29 22:18 ` Isaac David
2017-08-29 23:06 ` Aaron Wolf
2017-08-29 23:30 ` Isaac David
2017-08-29 23:43 ` Aaron Wolf
2017-08-30 0:51 ` Isaac David
2017-08-30 1:43 ` Aaron Wolf
2017-08-30 3:07 ` Isaac David
2017-08-30 3:19 ` Isaac David
2017-08-30 9:15 ` Lyberta
2017-08-30 16:19 ` Aaron Wolf
2017-08-31 1:54 ` Mike Gerwitz
2017-08-31 4:48 ` Aaron Wolf
2017-08-31 5:10 ` Mike Gerwitz
2017-08-31 5:23 ` Aaron Wolf
2017-08-31 19:43 ` John Sullivan
2017-08-31 19:49 ` Aaron Wolf [this message]
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://lists.gnu.org/mailman/listinfo/libreplanet-discuss
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fa77bb71-3b55-beb8-e252-61f1f0b436fc@riseup.net \
--to=wolftune@riseup.net \
--cc=johns@fsf.org \
--cc=libreplanet-discuss@libreplanet.org \
--cc=mtg@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.
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).