Conversation
Notices
-
Idea: to ease burden of FSF licensing team, instead of pestering FSF directly I will pass annoying license ?s to @fontana as #trolldonations
- Richard Fontana likes this.
- Richard Fontana repeated this.
-
Here's one: if proper AGPL compliance is to put source link on every page, what about an AGPL JSON API? /cc @fontana #trolldonations
-
Is best practice to encode a source link in every response like {"source": "http://example.org/source"} #trulynotatrolldonation
-
=]
-
I don't think that a JSON API qualifies as an "interactive user interface".
-
@cwebber Best way is for AGPLv3 JSON APIs compliance is a custom HTTP header with the source code. No link; the entire app source in base64
-
Interesting. We don't embed links to source in our machine-targeted formats (RDF, RSS, Atom, JSON, XML); do you think that's wrong?
-
is "curl -i -X OPTIONS host" interacting? And a HEAD request? Typically those don't have bodies, link to src in HTTP headers of response?
-
how ya been, @evan?
-
Evan Prodromou and Christopher Allan Webber like this.
-
Seriously though, I'd suggest something like an "X-Source" header to point to the complete corresponding source code.
Stanley Crokry likes this. -
-
@cwebber I dispute the premise that putting a source link on every page is proper AGPL compliance. It may be *one* proper way.
Christopher Allan Webber likes this. -
Great, thanks for asking.
-
Good to know that we've got a brief reprieve before the @bkuhn hammer comes down.
Christopher Allan Webber likes this. -
I wonder if a new link-rel as in RFC5988 makes sense. "source" implies "the source of this data" rather than "source of generator".
-
Now that I think about it, "generator" might be good enough. See http://identi.ca/url/69281237 for an example.
-
In http://identi.ca/url/69281257 we name the generator but don't give a link.
-
What about something non-HTTP over a socket, but still interactive, like a MUD over telnet? #notatrolldonation
-
certainly not. base64 is most definitely not the "preferred medium for modification," which is what the gpl requires. U…
-
*appends #ianal and #FontanaKnowsBest*
-
@tekk I'd think serializations would be okay, otherwise wouldn't that also mean that gzipped tarballs aren't preferred form of modification?
-
@fontana I'd be interested in knowing a list of non-link, acceptable AGPL compliance methods!
-
... that aren't base64 encoding source into your http headers
-
ah, good point.
-
@cwebber Fortunately @evan set a fairly low standard: just indirectly link to generic project site. !notatroll !AGPL
Christopher Allan Webber likes this. -
Richard Fontana
GNU Affero General Public Licence
, Bradley M. Kuhn
, Tom "spot" Callaway
, Richard Fontana
@bkuhn oh you mean thread 3 years later? @spot & I resolved that, I think. Add'l permission to give source in 2 wks on affirmative request.
-
@fontana, if I didn't have to do all bookkeeping work at #Conservancy, I'd have more time to answer your threads. Have you donated to help?
All Identi.ca content and data are available under the