solutions for source code take downs due to DMCA?
brief github session: --- python-iview.gitm $ git fetch Username for 'https://github.com': zenaan Password for 'https://zenaan@github.com': remote: Repository unavailable due to DMCA takedown. remote: See the takedown notice for more details: remote: https://github.com/github/dmca/blob/master/2015-10-27-Python-iview.md. fatal: unable to access 'https://github.com/vadmium/python-iview.git/': The requested URL returned error: 503 --- My last change is: caf726732 2015-07-02 (HEAD, master) Humax retired; change to Panasonic feed I had plans to use it, but never quite got a round tuit, but I did grab a clone last year, to make sure I had a copy in case and or when I wanted or needed it. A DMCA takedown has happened since then. Finding alternative repos is not hard, but finding one which is updated is not something I have achieved - it looks like the DMCA ogre has wielded his club and squashed this probject, AFAICT. That's not good. It's not healthy for our (global) community. This feels like a problem we should be able to solve. Further info on this DMCA takedown: https://github.com/vadmium/python-iview https://github.com/github/dmca/blob/master/2015-10-27-Python-iview.md https://theconversation.com/python-iview-copyright-crusader-or-vigilante-ope... http://www.mibus.org/2012/09/18/letter-to-the-abc-re-the-takedown-of-python-... http://www.mibus.org/2012/09/23/doctor-who-sans-python-iview/ A foundational thought re freedom of information and freedom of culture and freedom to share comes to mind - are there any papers about any form of shock-test resistant hidden server design, e.g. with some number of trusted entry points into the TOR network to hide behind? It seems "we" have yet to design a functional hidden service? Zenaan
Dnia sobota, 19 marca 2016 13:04:55 Zenaan Harkness pisze:
brief github session: (...)
1. use a centralized, corporate-operated service; 2. be surprised when corporate exercises their power based on centralisation by taking something down; 3. be completely appalled, write an angry blog post or e-mail; 4. start using a different centralized service; 5. rinse, repeat.
It seems "we" have yet to design a functional hidden service?
It seems "we" have yet to take our heads out of our asses and stop using centralized shit because "it's convenient". -- Pozdrawiam, Michał "rysiek" Woźniak Zmieniam klucz GPG :: http://rys.io/pl/147 GPG Key Transition :: http://rys.io/en/147
On 3/29/16, rysiek
Dnia sobota, 19 marca 2016 13:04:55 Zenaan Harkness pisze:
brief github session: (...)
1. use a centralized, corporate-operated service; 2. be surprised when corporate exercises their power based on centralisation by taking something down; 3. be completely appalled, write an angry blog post or e-mail; 4. start using a different centralized service; 5. rinse, repeat.
It seems "we" have yet to design a functional hidden service?
It seems "we" have yet to take our heads out of our asses and stop using centralized shit because "it's convenient".
Good points, fair enough. I've promoted the "run it yourself or you don't control it and it will be used against you" principle a few times now... Is there a pseudonymous (all we can seem to even hope for at the moment) git hosting network, with discoverability? Perhaps my searching is simply not adequate, perhaps it's only relevant to those who do the development. I am aware that if you are a high-profile target, it's almost impossible to host anything - but perhaps tor hidden services are "adequate" for "entertainment industry" take downs?
Hi, Dnia środa, 30 marca 2016 08:03:19 Zenaan Harkness pisze:
It seems "we" have yet to design a functional hidden service?
It seems "we" have yet to take our heads out of our asses and stop using centralized shit because "it's convenient".
Good points, fair enough.
I've promoted the "run it yourself or you don't control it and it will be used against you" principle a few times now...
Is there a pseudonymous (all we can seem to even hope for at the moment) git hosting network, with discoverability?
There are attempts: http://gitchain.org/ https://github.com/cjb/GitTorrent Also, a decentralized, distributed package manager: https://github.com/whyrusleeping/gx The fact that all of these projects are hosted on GitHub says a lot, though.
Perhaps my searching is simply not adequate, perhaps it's only relevant to those who do the development. I am aware that if you are a high-profile target, it's almost impossible to host anything - but perhaps tor hidden services are "adequate" for "entertainment industry" take downs?
Perhaps. But what I believe and will keep saying over and over, and over again, is that we *need* to decentralize the application layer (and redecentralize all the lower OSI layers, but that's another thing). Hence my interest in stuff like Twister: http://twister.net.co/ -- Pozdrawiam, Michał "rysiek" Woźniak Zmieniam klucz GPG :: http://rys.io/pl/147 GPG Key Transition :: http://rys.io/en/147
On 3/30/16, Zenaan Harkness
perhaps tor hidden services are "adequate" for "entertainment industry" take downs?
Trackerless bittorrent contained entirely within i2p / tor / phantom networks works fine. There are some trackers in operation too. AFAIK nothing related to torrenting multimedia therein has ever disappeared under suspicion of takedown.
On Tue, Mar 29, 2016 at 4:07 PM, rysiek
Dnia sobota, 19 marca 2016 13:04:55 Zenaan Harkness pisze:
brief github session: (...)
1. use a centralized, corporate-operated service; 2. be surprised when corporate exercises their power based on centralisation by taking something down; 3. be completely appalled, write an angry blog post or e-mail; 4. start using a different centralized service; 5. rinse, repeat.
It seems "we" have yet to design a functional hidden service?
It seems "we" have yet to take our heads out of our asses and stop using centralized shit because "it's convenient".
Convenience of the developer is secondary to convenience of the user. If the user has to take a bunch of extra steps to download or contribute to your software, your project is far more likely to die of that than it would be to get taken down on some centralized service. And even if your software is hosted on some decentralized service, it still needs to be discoverable in some way. If it's primarily discovered by word of mouth, some parasite will register a domain and pretend to be the authoritative host of it, then serve some malware-infested or backdoored build, if it's even your software at all. That happens even with centrally-hosted software when the developers don't pay enough attention to SEO.
participants (5)
-
grarpamp -
mo -
rysiek -
Sean Lynch -
Zenaan Harkness