Re: How to go about sharing (was: one of a dozen threads about Cryptome)
Each depends on the situation, and whether or not fair use applies. If there are mechanisms in place to sell or license the content, fair use is less likely to apply. So far, I haven't had any big problems with IA despite 100k+ items, several TB of data and 1% their text library. Will somethings be an issue? Maybe, but I'll cross that bridge when I come to it and not worry about it until I know what chasm I have to cross and where. Provenance etc. is situation dependent, no categorical answer exists that isn't a bald faced lie. On Sun, Oct 11, 2015 at 10:25 PM, Travis Biehn <tbiehn@gmail.com> wrote:
Unnecessary for what threats? Who is the arbiter / granter of authority on 'copyright' or 'DMCA' takedowns? What is this 'violation'? Do I, as an oppressive regime worker, simply need to put 'Copyright the TLAs, all rights reserved" next to my TS stamp to keep it off your website?
Hosting over HTTP(s) provides neither anonymity, nor metadata anonymity. There isn't much you can do to change this, except loudly inform your userbase of these properties, provide them with mechanisms to ensure the integrity of the resource and provide alternative protocols which possess these desired qualities.
How do you attest to the data provenance, your attestation or guarantee of integrity AND completeness?
Archive.org is not 'censorship resistant'.
-Travis
On Sun, Oct 11, 2015 at 10:11 PM, Michael Best <themikebest@gmail.com> wrote:
Thoughts - All good advice in it's own way, but mostly it seems unnecessary. Aside from copyright and reprint issues, 99% of what's on Cryptome is not only open source, it's not really objectionable in terms of hosting it.
TheCthulhu does a great job of distributing large amounts of data, but that's it's own thing and requires an ongoing budget and infrastructure.
I figure with Archive.org I can distribute 99.9% of material and not worry about copyright, bandwidth, etc. If it turns out there's a violation I missed, the item gets taken down - not the entire site or all the uploads. On the rare occasion that there's something else, I'd rather take whatever steps are needed to distribute it then rather than try to build my own independent infrastructure ahead of time.
Things to add? Holes to poke in my logic?
On Mon, Oct 12, 2015, at 12:32 PM, Travis Biehn wrote:
* You can start by re-posting the leaked traffic logs... (Editorial *>* discretion is frowned upon amongst the idealists.) *> * Maybe set up an onion, host on i2p, freenet (hehehe), ethereum, the * * blockchain, torrents. Spread it far and wide, set up a PKI, set up a *>* WOT, keep it all offline. *> * If you're a real masochist you'll host the docs on some crazy *>* 'website' with no indirection protecting you from legal/illegal/TLA *>* action. Keep the info off the dark web, off the deep web and in the *>* search indexes. *> * Warrant canary (which won't work), encryption (you won't be safe) and *>* signatures (secrets will be stolen.) *> * If you think you can survive as well as JYA, Deb & fare better than * * Assange, go for it. Be prepared. *> * It doesn't pay very well. You'd have to be crazy to do this. * Or you can be like TheCthulhu and run your own data centre with good lawyers. Alfie
-- Twitter <https://twitter.com/tbiehn> | LinkedIn <http://www.linkedin.com/in/travisbiehn> | GitHub <http://github.com/tbiehn> | TravisBiehn.com <http://www.travisbiehn.com> | Google Plus <https://plus.google.com/+TravisBiehn>
participants (1)
-
Michael Best