BLU Discuss list archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- Subject: [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: mark at buttery.org (Shirley Márquez Dúlcey)
- Date: Sun, 8 Nov 2015 02:57:07 -0500
- In-reply-to: <563EA471.9030105@gmail.com>
- References: <v1q09cqnmfpg4saensypmrdq.1443230831986@email.android.com> <560D6491.9070804@gmail.com> <CA+h9Qs5roAn7EE_FT90fBoo9UL4MQES0Mud40atTw9NoOuLNkw@mail.gmail.com> <560D69EA.2040700@gmail.com> <560D76BB.9080704@mattgillen.net> <560D9050.3050906@gmail.com> <201510020110.t921Anlu021166@dsl092-065-009.bos1.dsl.speakeasy.net> <560DEBE2.5040206@gmail.com> <CAMdng5v3BvxyJPcLDCd779Vp4uKPbsew3KphXQ_qv4Cisb-Vmg@mail.gmail.com> <560DFFEF.6000408@gmail.com> <CAJFsZ=riNyJ6buKFqga=xhm8o_yNJtReEWPY0cAS0vEeZojoeQ@mail.gmail.com> <561299CC.6090200@gmail.com> <CAJFsZ=onALey9R4DWBVK4Lqcxz9wrdpWiM1y0d+=fDmO1wOKJw@mail.gmail.com> <5612B9F7.7070604@gmail.com> <874mh0ldi6.fsf@johnbyrnes.info> <563B780A.7030002@gmail.com> <CAMdng5uj4u5QGXV3XnkD7F878xy_ez6K=wW6xuZL9DGAGAUjSQ@mail.gmail.com> <563BAF21.1030301@gmail.com> <CAJFsZ=pN=z49MVwdMA_1Rqy9jk7C5W2HpwNERoE88vg1gQStSQ@mail.gmail.com> <563D865A.7060307@gmail.com> <CAJFsZ=o-RczabW0nYSi4=L1zfP1oKcWVwLNpjmFN+UZK0zBzGA@mail.gmail.com> <563EA471.9030105@gmail.com>
I think your interpretation of the TiVo situation is philosophically incorrect, even though there are no factual errors. The original intent of the GPL was to protect the freedom to use GPL software in any way you see fit, including the use of modified versions and sharing those modified versions with others if you wish. The TiVo people found a loophole that had not been envisioned when the GPLv2 was written; it allowed them to release the TiVo software as open source while still stopping modified software from being used in the intended manner - that is, to connect to the TiVo service. You characterize what RMS did with the GPLv3 as "fuck TiVo". But the reality is that TiVo had already fucked RMS by finding a way to violate the intent of the GPL. They were compliant with the letter of the law but not with its spirit. What RMS did with GPLv3 was close the loophole and restore the original intent of the license. Makers of routers don't have a similar problem; the way in which they use GPL software is not in any way incompatible with the intent of the license. Whether RMS's intent is a reasonable one is a separate debate. (I happen to believe that it is, and I suspect that Rich disagrees.) But I think that RMS has the right to keep his work from being used in a fundamentally closed way (as TiVo has done) if that is his wish. Now that cloud computing and software as a service are being a normal thing rather than an exception, the interesting question going forward is whether we will see more adoption of the GNU Affero license. For those unfamiliar with it, it is based on the GPLv3 but has an additional clause that requires the publication of source code when software is used as part of an online service such as a web site, even if the program binary is never actually distributed to the end users. On Sat, Nov 7, 2015 at 8:25 PM, Rich Pieri <richard.pieri at gmail.com> wrote: > On 11/7/2015 5:08 PM, Bill Bogstad wrote: >> >> software or FSF? lawsuits would make more sense to me. As it is, it >> seems to me that there must be some other reason that they don't just >> ship something like OpenWrt. I have my own theories involving the > > > Another reason is RMS. Despite TiVo being in full compliance with the GPLv2, > RMS took it upon himself to launch his fuck TiVo crusade. RMS and the GPLv3 > have demonstrated that using GPL software in commercial products is > dangerous to vendors. OpenWrt includes Samba and mini-httpd, both of which > are GPLv3. This makes OpenWrt a hot potato in the sense of a live hand > grenade: nobody wants to be holding it when RMS goes "boom!". > > It isn't any one reason. When you take all of the problems that go with > trying to use GPL software in commercial products -- warranties, support, > licenses, RMS' sanity, and so forth -- it's easy to come to the conclusion > that choosing free as in FSF software is the wrong choice. > > -- > Rich P. > > _______________________________________________ > Discuss mailing list > Discuss at blu.org > http://lists.blu.org/mailman/listinfo/discuss
- Follow-Ups:
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- References:
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: john at johnbyrnes.info (John Byrnes)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: mark at buttery.org (Shirley Márquez Dúlcey)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: bogstad at pobox.com (Bill Bogstad)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: bogstad at pobox.com (Bill Bogstad)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- From: richard.pieri at gmail.com (Rich Pieri)
- [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- Prev by Date: [Discuss] Debian adds another systemd dependency, Busybox drops it
- Next by Date: [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- Previous by thread: [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- Next by thread: [Discuss] Fwd: Hey FCC, Don't Lock Down Our Wi-Fi Routers | WIRED
- Index(es):