Get the latest update on our Vizio court case
●News
Press Releases
Press
Blog
Vizio Lawsuit in the News
Our Issues in the News
●About
Sponsors
Sustainers
Board of Directors
Staff
Evaluation Committee
Outside Counsel, et alia
Transparency
Contact
●Our Work
Copyleft Compliance
We defend and uphold the rights of software users and consumers under copyleft licenses.
Impact Litigation
We defend the legal rights of software users. Learn the details, status, and stakes of our court cases.
Give Up GitHub
We urge FOSS Developers to Give Up GitHub! Learn why.
Outreachy
We offer internships for anyone who faces underrepresentation, systemic bias, or discrimination in the tech industry.
FOSSY
Our annual community-oriented conference focused on the creation and impact of free and open source software.
●Tools
Member Projects
We provide non-profit infrastructure and services to our members creating Free/Libre and Open Source Software.
Use The Source
Our tool for evaluating the source code candidates companies must provide for GPLed software.
OpenWrt One
We designed and built the first ever wireless Internet router designed with software freedom and right to repair in mind.
●Learn
The Corresponding Source
A bi-weekly oggcast about legal, policy, and many other issues in the Free, Libre, and Open Source Software (FLOSS) world.
Glossary of Terms
A list of terms you might be unfamiliar with but occur frequently in our work.
FAQ About the Vizio Lawsuit
Your most frequently asked questions about the Vizio lawsuit, answered in one place.
●
Donate
●News
Press Releases
Press
Blog
Vizio Lawsuit in the News
Our Issues in the News
●About
Sponsors
Sustainers
Board of Directors
Staff
Evaluation Committee
Outside Counsel, et alia
Transparency
Contact
●Our Work
Copyleft Compliance
We defend and uphold the rights of software users and consumers under copyleft licenses.
Impact Litigation
We defend the legal rights of software users. Learn the details, status, and stakes of our court cases.
Give Up GitHub
We urge FOSS Developers to Give Up GitHub! Learn why.
Outreachy
We offer internships for anyone who faces underrepresentation, systemic bias, or discrimination in the tech industry.
FOSSY
Our annual community-oriented conference focused on the creation and impact of free and open source software.
●Tools
Member Projects
We provide non-profit infrastructure and services to our members creating Free/Libre and Open Source Software.
Use The Source
Our tool for evaluating the source code candidates companies must provide for GPLed software.
OpenWrt One
We designed and built the first ever wireless Internet router designed with software freedom and right to repair in mind.
●Learn
The Corresponding Source
A bi-weekly oggcast about legal, policy, and many other issues in the Free, Libre, and Open Source Software (FLOSS) world.
Glossary of Terms
A list of terms you might be unfamiliar with but occur frequently in our work.
FAQ About the Vizio Lawsuit
Your most frequently asked questions about the Vizio lawsuit, answered in one place.
●Donate
Thanks to so many donors, we met our largest match donation ever of $211,939.
Two generous anonymous donors have provided another $40,012ofadditional matching funds.
Give now to help us reach this stretch goal!
For only 4 more days, the
next $13,079offinancial support we receive will be matched!
$26,933 matched!
$13,079 to go!
$211,927 fully matched!
Home / News / Blog
Trump's Social Media Platform and the Affero General Public License (of Mastodon)
byBradley M. Kühn
on October 21, 2021
An analysis: Trump's Group has 30 days to remedy the violation, or their rights in the
software are permanently terminated
In 2002, we used phrases like “Web 2.0” and “AJAX”
to describe the revolution that was happening in web technology for average
consumers. This was just before names like Twitter
and Facebook became famous worldwide. Web 2.0 was the groundwork
infrastructure of the “social media” to come.
As software policy folks, my colleagues and I knew that these technologies
were catalysts for change. Software applications, traditionally purchased on
media and installed explicitly, were now implicitly installed through web
browsers — delivered automatically, or even sometimes run on the user's
behalf on someone else's
computer. As copyleft
activists specifically, we knew that copyleft licensing would have to adjust,
too.
In late 2001, I sat and read and reread section 2(c) of the GPLv2. After
much thought, I saw how it could be adapted, using the geeky computer
science
concept called a
quine — a program that has a feature to print its own source code
for the user. A similar section to GPLv2§2(c) could be written that
would assure that every user of a copylefted program on the Internet would
be guaranteed the rights and freedoms to copy, modify, redistribute and/or
reinstall their software — which was done by offering a source-code
provision feature to every user on the network. The key concept behind
the Affero GPL (AGPL)
version 1 was born. Others drafted and released AGPLv1 based on my
idea. Five years later, I was proudly in the “room where it
happened”
when Affero
GPL version 3 was drafted. Some of the words in that section are ones
I suggested.
We were imagining a lot about the future in those days; the task of
copyleft licensing drafting requires trying to foresee how others might
attempt to curtail the software rights and freedoms of others. Predicting
the future is difficult and error-prone. Today, a piece of Affero GPLv3's
future came to pass that I would not have predicted back in November
2007 at its release.
I invented that network source code disclosure provision of the
AGPL — the copyleft
license later applied to the Mastodon
software — in 2002 in light of that very problem: parties who
don't share our values might use (or even contribute to) software written by the FOSS community. The
license purposefully treats everyone equally (even people we don't like or
agree with), but they must operate under the same rules of the copyleft
licenses that apply to everyone else.
Today, we saw the Trump Media and Technology Group ignoring those important rules
— which were designed for the social good. Once caught in the act,
Trump's Group scrambled and took the site down.
Early evidence strongly supports that Trump's Group publicly launched a
so-called “test site” of their “Truth Social”
product, based on the AGPLv3'd Mastodon
software platform. Many users were able to create accounts and use it
— briefly. However, when you put any site on the Internet licensed
under AGPLv3, the AGPLv3
requires that you provide (toevery user) an opportunity to
receive the entire Corresponding Source for the website based on that code.
These early users did not receive that source code, and Trump's Group
is currently ignoring their very public requests for it. To comply with this important FOSS license,
Trump's Group needs to immediately make that Corresponding Source available to all who used the site today while it was live.
If they fail to do this within 30 days, their rights and permissions in the software are automatically and permanently
terminated. That's how AGPLv3's cure provision works — no exceptions —
even if you're a real estate mogul, reality television star, or even a
former POTUS.
I and my colleagues at Software Freedom Conservancy are experts at
investigating non-compliance with copyleft license and enforcing those
licenses once we confirm the violations. We will be following this issue
very closely and insisting that Trump's Group give the Corresponding Source
to all who use the site.
Finally, it's worth noting that we could find no evidence that someone
illegally broke into the website. All the evidence available on the Internet
(as of 2021-10-22) indicates that the site was
simply deployed live early as a test, and without proper configuration (such
as pre-reserving some account names). Once discovered, people merely used the
site legitimately to register accounts and use its features.
Update (2021-10-22): Some have asked us
how this situation relates to our Principles of
Community-Oriented GPL Enforcement, since we are publicly analyzing a
copyleft violation publicly. Historically, we did similarly with the Canonical, Ltd., Cambium,
Ubiquiti, and Tesla (twice!) violations. We do believe
that “confidentiality can increase receptiveness and
responsiveness”, but once a story is already made widely known to the public by a
third-party, confidentiality is no longer
possible, since the public already knows the details. At that moment, the need to educate the public supersedes any value in non-disclosure.
[permalink]
Tags:
conservancy,
GPL,
licensing
Please email any comments on this entry to
info@sfconservancy.org.
Other Conservancy Blog entries…
Blog Index by Year
●2026
●2025
●2024
●2023
●2022
●2021
●2020
●2019
●2018
●2017
●2016
●2015
●2014
●2013
●2012
●2011
●2010
Blogs by Tag
●conservancy
●GPL
●supporter
●licensing
●conferences
●law
●events
●software freedom for everyone
●Member Projects
●Outreachy
●FOSS Sustainability
●diversity
●resources
●Copyleft Conf
●ContractPatch
●Filings
●Godot
●Reproducible Builds
●Year In Review 2016
●fundraiser
●CLA
●Wine
●Year In Review 2015
●Kallithea
●QEMU
●Selenium
●Google Summer of Code
●Homebrew
●inkscape
●patent
●security
●Clojars
●Git
●Hackfests
●Racket
●cyborg
●phpMyAdmin
●pypy
●volunteer
●Accounting
●LibreHealth
●Shotwell
●inclusion
●jQuery
●microblocks
●sourceware
Blogs by Author
●Vladimir Bejdo
●Kate Chapman
●Pamela Chestek
●Denver Gingerich
●Bradley M. Kühn and Denver Gingerich
●Will Hawkins
●Fred Jennings
●Deb and Karen
●Jeff King
●Bradley M. Kühn
●Conservancy + Bro LT
●Christine Lemmer-Webber
●Deb Nicholson
●Sourceware PLC
●Rick Sanders
●Bradley M. Kühn and Karen M. Sandler
●Karen Sandler
●Tony Sebro
●Sage A. Sharp
●Brett Smith
●Conservancy's Staff
●Daniel Takamori
●Outreachy Team
●Marina Zhurakhinskaya
●Molly deBlanc
●Main Page
●Contact
●Sponsors
●RSS Feed
●
Software Freedom Conservancy is a 501(c)(3) non-profit charity.
Privacy Policy last updated 22 December 2020.
This page and its contents are licensed under a Creative Commons Attribution-Share Alike 4.0 International License.