I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’ve written
before about how discussions began at FSF in January 2002 to address the
“ASP loophole of the GPL”. In those months that
followed, when I came up with the idea for what would (later be named)
the Affero clause, I naïvely thought that a license term for the
software would “solve” the Software as a Service (SaaS)
problem. Indeed, I considered the problem fully addressed upon publication of the original AGPL, and it was much later before I realized the problem was more complex.
The AGPLv3 is only one (albeit essential) part of what must
be a multi-pronged strategy to address the freedom implications and
concerns of SaaS.
At Auotonomo.us,
we have published The Franklin Street Statement on Freedom and Network Services (named for the place it
was declared — the location of post-Temple-Place FSF offices). The Statement is a manifesto (of sorts) outlining the
concerns that must be addressed and the beginnings of some ideas for
solutions. I hope you will read it and begin considering this
issue if you haven’t already, and that you will endorse the statement if you already understand the issue. We hope to be publishing more on that site as
the year goes on!
I’m personally excited because the software for the system, Laconica, is under the license that I
originally drafted back in 2002, the Affero GPL (which was updated
as part of the GPLv3 process, and is now available as AGPLv3).
This marks the first time I’ve seen a company release its product under
a network service freedom-defending license from the start.
His launch comes at an interesting time. Twitter has had no
Jabber-based updates for more than a month, and Identica allows updates
via Jabber. Thus, in a way, it’s more fully featured than Twitter is
right now!
I’m personally excited because the software for the system, Laconica, is under the license that I
originally drafted back in 2002, the Affero GPL (which was updated
as part of the GPLv3 process, and is now available as AGPLv3).
This marks the first time I’ve seen a company release its product under
a network service freedom-defending license from the start.
His launch comes at an interesting time. Twitter has had no
Jabber-based updates for more than a month, and Identica allows updates
via Jabber. Thus, in a way, it’s more fully featured than Twitter is
right now!
The collective thoughts of the interwebz
Manage Consent
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.