July 2015 - cypherpunks - lists.cpunks.org

"Google is to surveillance capitalism what GM was to managerial capitalism"
by Razer 07 Jul '15

07 Jul '15

> Big Other: Surveillance Capitalism and the Prospects of an Information > Civilization > > Shoshana Zuboff, Berkman Center for Internet & Society; Harvard > Business School > > April 4, 2015 > > Abstract: > This article describes an emergent logic of accumulation in the > networked sphere, ‘surveillance capitalism,’ and considers its > implications for ‘information civilization.’ Google is to surveillance > capitalism what General Motors was to managerial capitalism. Therefore > the institutionalizing practices and operational assumptions of Google > Inc. are the primary lens for this analysis as they are rendered in > two recent articles authored by Google Chief Economist Hal Varian. > > Varian asserts four uses that follow from computer-mediated > transactions: ‘data extraction and analysis,’ ‘new contractual forms > due to better monitoring,’ ‘personalization and customization,’ and > ‘continuous experiments.’ > > An examination of the nature and consequences of these uses sheds > light on the implicit logic of surveillance capitalism and the global > architecture of computer mediation upon which it depends. This > architecture produces a distributed and largely uncontested new > expression of power that I christen: ‘Big Other.’ It is constituted by > unexpected and often illegible mechanisms of extraction, > commodification, and control that effectively exile persons from their > own behavior while producing new markets of behavioral prediction and > modification. Surveillance capitalism challenges democratic norms and > departs in key ways from the centuries long evolution of market > capitalism. > > Number of Pages in PDF File: 15 > > Keywords: surveillance capitalism, big data, Google, information > society, privacy, internet of everything http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2594754

1 0

Re: [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork
by Eugen Leitl 07 Jul '15

07 Jul '15

----- Forwarded message from Adam Back <adam(a)cypherspace.org> ----- Date: Mon, 15 Jun 2015 20:03:25 +0200 From: Adam Back <adam(a)cypherspace.org> To: Mike Hearn <mike(a)plan99.net> Cc: Bitcoin Dev <bitcoin-development(a)lists.sourceforge.net> Subject: Re: [Bitcoin-development] questions about bitcoin-XT code fork & non-consensus hard-fork Message-ID: <CALqxMTFC7zBN9GvHAZLQj4SbXjzkCAM9meSErd3qn7uCoON98Q(a)mail.gmail.com> Hi Mike Well thank you for replying openly on this topic, its helpful. I apologise in advance if this gets quite to the point and at times blunt, but transparency is important, and we owe it to the users who see Bitcoin as the start of a new future and the$3b of invested funds and $600m of VC funds invested in companies, we owe it to them that we be open and transparent here. I would really prefer on a personal nor professional basis to be having this conversation period, never mind in public, but Mike - your and Gavin's decision to promote a unilateral hard-fork and code fork are extremely high risk for bitcoin and so there remains little choice. So I apologise again that we have to have this kind of conversation on a technical discussion list. This whole thing is hugely stressful and worrying for developers, companies and investors. I strongly urge that we return to the existing collaborative constructive review process that has been used for the last 4 years which is a consensus by design to prevent one rogue person from inserting a backdoor, or lobbying for a favoured change on behalf of a special interest group, or working for bad actor (without accusing you of any of those - I understand you personally just want to scale bitcoin, but are inclined to knock heads and try to force an issue you see, rather than work collaboratively). For you (and everyone) - Should there be a summit of some kind, that is open attendance, and video recorded so that people who are unable to attend can participate too, so that people can present the technical proposals and risks in an unbiased way? (It is not theoretical question, I may have a sponsor and host - not Blockstream, an independent, its a question for everyone, developers, users, CTOs, CEOs.) So here I come back to more frank questions: Governance The rest of the developers are wise to realise that they do not want exclusive control, to avoid governance centralising into the hands of one person, and this is why they have shared it with a consensus process over the last 4 years. No offence but I dont think you personally are thinking far enough ahead to think you want personal control of this industry. Maybe some factions dont trust your motives, or they dont mind, but feel more assured if a dozen other people are closely reviewing and have collective review authority. - Do you understand that attempting to break this process by unilateral hard-fork is extremely weakening of Bitcoin's change governance model? - Do you understand that change governance is important, and that it is important that there be multiple reviewers and sign-off to avoid someone being blackmailed or influenced by an external party - which could potentially result in massive theft of funds if something were missed? - Secondarily do you understand that even if you succeed in a unilateral fork (and the level of lost coins and market cap and damage to confidence is recoverable), that it sets a precedent that others may try to follow in the future to introduce coercive features that break the assurances of bitcoin, like fungibility reducing features say (topically I hear you once proposed on a private forum the concept of red-lists, other such proposals have been made and quickly abandoned), or ultimately if there is a political process to obtain unpopular changes by unilateral threat, the sky is the limit - rewrite the social contract at that point without consensus, but by calculation that people will value Bitcoin enough that they will follow a lead to avoid risk to the system? Security As you probably know some extremely subtle bugs in Bitcoin have at times slipped past even the most rigorous testings, often with innocuous but unexpected behaviours, but some security issues Some extremely intricate and time-sensitive security defect and incident response happens from time to time which is not necessarily publicly disclosed until after the issue has been rolled out and fixed, which can take some time due to the nature of protocol upgrades, work-arounds, software upgrade via contacting key miners etc. We could take an example of the openSSL bug. - How do you plan to deal with security & incident response for the duration you describe where you will have control while you are deploying the unilateral hard-fork and being in sole maintainership control? - Are you a member of the bitcoin security reporting list? On 15 June 2015 at 11:56, Mike Hearn <mike(a)plan99.net> wrote: > I will review both and mostly delegate to Gavin's good taste around the > details, unless there is some very strong disagreement. But that seems > unlikely. > ... > Feedback will be read. There are no NACKS in Bitcoin XT. Patch requests > aren't scored in any way. The final decision rests with the maintainer as in > ~all open source projects. As you know the people who have written 95% of the code (and reviewed, and tested, and formally proved segments etc) are strenuously advising not to push any consensus code into public use without listening to and addressing review questions which span beyond rigorous code & automated guided fuzz testers, simulation and sometimes formal proofs, but also economics, game-theory and critically very subtle determinism/consensus safety that they have collectively 4-5 years experience of each. - Will you pause your release plans if all of the other developers insist that the code or algorithm is defective? - Please don't take this the wrong way, and I know your bitcoinj work was a significant engineering project which required porting bitcoin logic. But If the answer to the above question is no, as you seemed to indicate in your response, as you not have not written much bitcoin core code yourself (I think 3 PRs in total), do you find yourself more qualified than the combination of peer review of the group of people who have written 95% of it, and maintained it and refactored most of it over the last 4-5 years? I presume from your security background you are quite familiar with the need for review of crypto protocol changes & rigorous code review. That is even more the case with Bitcoin given the consensus criticality. >> - On the idea of a non-consensus hard-fork at all, I think we can >> assume you will get a row of NACKs. Can you explain your rationale >> for going ahead anyway? The risks are well understood and enormous. > > If Bitcoin runs out of capacity it will break and many of our users will > leave. That is not an acceptable outcome for myself or the many other > wallet, service and merchant developers who have worked for years to build > an ecosystem around this protocol. That you are frustrated, is not a sufficient answer as to why you are proposing to go ahead with a universally acknowledged extreme network divergence danger unilateral hard-fork, lacking wide-spread consensus. People are quite concerned about this. Patience, caution and prudence is necessary in a software system with such high assurance requirements. So I ask again: - On the idea of a non-consensus hard-fork at all, I think we can assume you will get a row of NACKs. Can you explain your rationale for going ahead anyway? The risks are well understood and enormous. Note the key point is that you are working on a unilateral hard-fork, where there is a clear 4 year established process for proposing improvements and an extremely well thought out and important change management governance process. While there has been much discussion, you nor Gavin, have not actually posted a BIP for review. Nor actually was much of the discussion even conducted in the open: it was only when Matt felt the need to clear the air and steer this conversation into the open that discussion arose here. During that period of private discussion you and Gavin were largely unknown to most of us lobbying companies with your representation of a method that concerns everyone of the Bitcoin users. Now that the technical community aware aware they are strenuously discouraging you on the basis of risks. Openness - Do you agree that bitcoin technical discussions should happen in the open? - As this is a FOSS project, do you agree that companies should also be open, about their requirements and trade-offs they would prefer? - Can you disclose the list of companies you have lobbied in private whether they have spoken publicly or not, and whether they have indicated approval or not? - Did you share a specific plan, like a BIP or white paper with these companies, and if so can we see it? - If you didnt submit a plan, could you summarise what you asked them and what you proposed, and if you discussed also the risks? (If you asked them if they would like Bitcoin to scale, I expect almost everyone does, including every member of the technical community, so that for example would not fairly indicate approval for a unilateral hard-fork) I and others will be happy to talk with the CTO and CEOs of companies you have lobbied in private, for balance to assure ourselves and the rest of the community that their support was given - and with full understanding of the risks of doing it unilaterally, without peer review, benefit of maintenance and security inidence management, and what exactly they are being quoting as having signed up for. (This maybe more efficiently and openly achieved by the open process, on a mailing list, maybe a different one even special purpose to this topic, with additional option of the open public meeting I proposed at the top). - Do you agree that it would be appropriate, that companies be aware of both the scaling opportunities (of course, great everyone wants scalability) as well as the technical limits and risks with various approaches? And that these be presented by parties from a range of views to ensure balance? - Do you consider your expression of issues to hold true to the ideal of representing balanced nuanced view of all sides of a technical debate, even when under pressure or feeling impatient about the process? You may want to review the opening few minutes of your epicenter 82 bitcoin for example where you claimed and I quote "[the rest of the technical community] dont want capacity to ever increase and want it to stay where it is and when it fills up people move to other systems". - Do you think that is an accurate depiction of the complex trade-offs we have been discussing on this list? (For the record I am not aware of a single person who has said they do not agree with scaling Bitcoin. Changing a constant is not the hard-part. The hard part is validating a plan and the other factors that go into it. It's not a free choice it is a security/scalability tradeoff. No one will thank us if we "scale" bitcoin but break it in hard to recover ways at the same time.) - Were you similarly balanced in your explanations when talking to companies in private discussions? - Do you understand that if we do not work from balanced technical discussion, that we may end up with some biased criteria? Authority Neither you nor Gavin have any particular authority here to speak on behalf of Bitcoin (eg you acknowledge in your podcast that Wladimir is dev lead, and you and Gavin are both well aware of the 4 year established change management consensus decision making model where all of the technical reviewers have to come to agreement before changes go in for security reasons explained above). I know Gavin has a "Chief Scientist" title from the Bitcoin Foundation, but sadly that organisation is not held in as much regard as it once was, due to various irregularities and controversies, and as I understand it no longer employs any developers, due to lack of funds. Gavin is now employed by MIT's DCI project as a researcher in some capacity. As you know Wladimir is doing the development lead role now, and it seems part of your personal frustration you said was because he did not agree with your views. Neither you nor Gavin have been particularly involved in bitcoin lately, even Gavin, for 1.5 years or so. - Do you agree that if you presume to speak where you do not have authority you may confuse companies? > If Bitcoin runs out of capacity it will break and many of our users will > leave. That is not an acceptable outcome for myself or the many other > wallet, service and merchant developers who have worked for years to build > an ecosystem around this protocol. But I think this is a false dichotomy. As I said in previous mail I understand people are frustrated that it has taken so long, but it is not the case that no progress has been made on scalability. I itemised a long list of scalability work which you acknowledged as impressive work (CPU, memory, network bandwidth/latency) and RBF, CPFP fee work, fee-estimation, and so on, which you acknowledged and are aware of. There are multiple proposals and BIPs under consideration on the list right now. - what is the reason that you (or Gavin) would not post your BIP along side the others to see if it would win based on technical merit? - why would you feel uniquely qualified to override the expert opinion of the rest of the technical community if your proposal were not considered to have most technical merit? (Given that this is not a simple market competition thing where multiple hard-forks can be considered - it is a one only decision, and if it is done in a divisive unilateral way there are extreme risks of the ledger diverging.) Network Divergence Risk >> - How do you propose to deal with the extra risks that come from >> non-consensus hard-forks? Hard-forks themselves are quite risky, but >> non-consensus ones are extremely dangerous for consensus. > > The approach is the same for other forks. Voting via block versions and then > when there's been >X% for Y time units the 1mb limit is lifted/replaced. But this is not a soft-fork, it is a hard-fork. Miner voting is only peripherally related. Even if in the extremis 75% of miners tried a unilateral hard-fork but 100% of the users stayed on the maintained original code, no change would occur other than those miners losing reward (mining fork-coins with no resale value) and the difficulty would adjust. The miners who made an error in choice would lose money and go out of business or rejoin the chain. However if something in that direction happens with actual users and companies on both sides of it users will lose money, the ledger will diverge as soon as a single double-spend happens, and never share a block again, companies will go instantly insolvent, and chaos will break out. This is the dangerous scenario we are concerned about. So the same question again: - How do you propose to deal with the extra risks that come from non-consensus hard-forks? Hard-forks themselves are quite risky, but non-consensus ones are extremely dangerous for consensus. Being sensitive to alarming the market It is something akin to Greece or Portugal or Italy exiting the euro currency in a disorderly way. Economists and central bank policy makers are extremely worried about such an eventuality and talk about related factors in careful, measured terms, watch Mario Draghi when he speaks. Imagine that bitcoin is 10x or 100x bigger. Bitcoin cant have people taking unilateral actions such as you have been proposing. It is not following the consensus governance process, and not good policy and it is probably affecting bitcoin confidence and price at this moment. >> - Do you have contingency plans for what to do if the non-consensus >> hard-fork goes wrong and $3B is lost as a result? > > Where did you get the $3B figure from? The fork either doesn't happen, or it > happens after quite a long period of people knowing it's going to happen - > for example because their full node is printing "You need to upgrade" > messages due to seeing the larger block version, or because they read the > news, or because they heard about it via some other mechanisms. This is not a soft-fork, and the community will not want to take the risks once they understand them, and they have months in which to understand them and at this point you've motivated and wasted 100s of developer man hours such that we will feel impelled to make sure that no one opts into a unilateral hard-fork without understanding the risks. It would be negligent to allow people to do that. Before this gets very far FAQs will be on bitcoin.org etc explaining this risk I would imagine. Its just starting not finished. What makes you think the rest of the community may not instead prefer Jeff Garzik's BIP after revisions that he is making now with review comments from others? Or another proposal. Taken together with a deployment plan that sees work on decentralisation tying into that plan. - If you persisted anyway, what makes you think bitcoin could not make code changes defensively relating to your unilateral fork? (I am sure creative minds can find some ways to harden bitcoin against a unilateral fork, with a soft-fork or non-consensus update can be deployed much faster than a hard-fork). I tried to warn Gavin privately that I thought he was under-estimating the risk of failure to his fork proposal due to it being unilateral. Ie as you both seem sincere in your wish to have your proposal succeed, then obviously the best way to do that is to release a BIP in the open collaborative process and submit it to review like everyone else. Doing it unilaterally only increases its chance of failure. The only sensible thing to do here is submit a BIP and stop the unilateral fork threat. Scalability Plans > Let me flip the question around. Do you have a contingency plan if Bitcoin > runs out of capacity and significant user disruption occurs that results in > exodus, followed by fall in BTC price? The only one I've seen is "we can > perform an emergency hard fork in a few weeks"! Yes people have proposed other plans. Bryan Bishop posted a list of them. Jeff Garzik has a proposal, BIP-100 which seems already better than Gavin's having benefit of peer review which he has been incorporating. I proposed several soft-fork models which can be deployed safely and immediately, which do not have ledger risk. I have another proposal relating to simplified soft-fork one-way pegs which I'll write up in a bit. I think there are still issues in Jeff's proposal but he is very open and collaborating and there maybe related but different proposals presently. >> As you can probably tell I think a unilateral fork without wide-scale >> consensus from the technical and business communities is a deeply >> inadvisable. > > Gavin and I have been polling many key players in the ecosystem. The > consensus you seek does exist. All wallet developers (except Lawrence), all > the major exchanges, all the major payment processors and many of the major > mining pools want to see the limit lifted (I haven't been talking to pools, > Gavin has). It does not seem to me that you understand the issue. Of course they want to increase the scalability of bitcoin. So does everyone else on this mailing list. That they would support that is obvious. If you presented your unilateral action plan without explaining the risks too. I think I covered this further above. If you would like to share the company list, or we can invite them to the proposed public physical meeting, I think it would be useful for them to have a balanced view of the ledger divergence risks, and alternative in-consensus proposals underway, as well as the governance risks, maintenance risks, security incident risks. Note that other people talk to companies too, as part of their day to day jobs, or from contacts from being in the industry. You have no special authority or unique ability to talk with business people. Its just that the technical community did not know you were busy doing that. I can not believe that any company that would listen to their CTO, CSO or failing that board would be ok with the risks implied by what you are proposing on full examination. > This notion that the change has no consensus is based on you polling the > people directly around you and people who like to spend all day on this > mailing list. It's not an accurate reflection of the wider Bitcoin community > and that is one of the leading reasons there is going to be a fork. A small > number of people have been flatly ignoring LOTS of highly technical and > passionate developers who have written vast amounts of code, built up the > Bitcoin user base, designed hardware and software, and yes built companies. I know you want scale bitcoin, as I said everyone here does. I think what you're experiencing is that you've had more luck explaining your pragmatic unilateral plan to non-technical people without peer review, and so not experienced the kind of huge pushback you are getting from the technical community. The whole of bitcoin is immensely complicated such that it takes an uber-geek CS genius years to catchup, this is not a slight of any of the business people who are working hard to deploy Bitcoin into the world, its just complicated and therefore not easy to understand the game-theory, security, governance and distributed system thinking. I have a comp sci PhD in distributed systems, implemented p2p network systems and have 2 decades of applied crypto experience with a major interest in electronic cash crypto protocols, and it took me a several years to catchup and even I have a few hazy spots on low-level details, and I addictively into read everything I could find. Realistically all of us are still learning, as bitcoin combines so many fields that it opens new possibilities. What I am expecting that yourself and Gavin are thinking is that you'll knock heads and force the issue and get to consensus. However I think you have seriously misjudged the risks and have not adequately explained them to companies you are talking with. Indeed you do not fully seem to acknowledge the risks, nor to have a well thought out plan here of how you would actually manage it, nor the moral hazards of having a lone developer in hugely divisive circumstances in sole control of bitcoins running code. Those are exactly the reasons for the code change governance process! Even though you are trying to help, the full result is you are not helping achieve anything by changing a constant and starting a unilateral hard-fork (not to trivialise the work of making a patch to do that). The work to even make the constant change be feasible was a result of 1000s of hours of work by others in the development community, that is emphatically and unilaterally telling you that hard-forks are hugely inadvisable. You are trying to break the code change governance security procedure that were put in place for good reason for the security of $3b of other peoples money, even if you have a pragmatic intent to help, this is flat out unacceptable. There are also security implications to what you are proposing, which I have heard you attempting to trivialise, that are core to Bitcoins security and core functionality. > the overwhelming impression I get from a few > others here is that no, they don't want to scale Bitcoin. They already > decided it's a technological dead end. I think this is a significant mischaracterisation, and I think almost everybody is on board with a combination plan: 1. work to improve decentralisation (specific technical work already underway, and education) 2. create a plan to increase block-size in a slow fashion to not cause system shocks (eg like Jeff is proposing or some better variant) 3. work on actual algorithmic scaling In this way we can have throughput needed for scalability and security work to continue. As I said you can not scale a O(n^2) broadcast network by changing constants, you need algorithmic improvements. People are working on them already. All of those 3 things are being actively worked on RIGHT NOW, and in the case of algorithmic scaling and improve decentralisation have been worked on for months. You may have done one useful thing which is to remind people that blocks are only 3x-4x below capacity such that we should look at it. But we can not work under duress of haste, nor unilateral ultimatums, this is the realm of human action that leads to moral hazard, and ironically reminds us of why Satoshi put the quote in the genesis block. Bitcoin is too complex a system with too much at stake to be making political hasty decisions, it would be negligent to act in such a way. Again please consider that you did your job, caused people to pay attention, but return to the process, submit a BIP, retract the unilateral hard-fork which is so dangerous and lets have things be calm, civil and collaborative in the technical zone of Bitcoin and not further alarm companies and investors. Adam ------------------------------------------------------------------------------ _______________________________________________ Bitcoin-development mailing list Bitcoin-development(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development ----- End forwarded message -----

12 29

NSA liquid cooled computing
by grarpamp 07 Jul '15

07 Jul '15

http://www.grcooling.com/wp-content/uploads/2015/06/NSA-The-Next-Wave.pdf

1 0

Re: [Cryptography] Crypto Wars
by grarpamp 07 Jul '15

07 Jul '15

>> elephant wrote: >> Would anyone be able to recommend me good literature on the Crypto Wars? >> Both historical and theoretical accounts (if they exist) would be great, >> digital or printed. Either stuff on the Crypto Wars I or II would be fab. > gnu wrote: > gone from > the Cryptome site, the JYA.com site, and the EFF.ORG sites. But http://cryptome.org/jya/cracking-des/cracking-des.htm http://web.archive.org/web/20000409094154/http://www.heise.de/tp/english/in… "I believe we must soon address the risks posed by electronic distribution of encryption software... unless we address this situation, use of the Internet to distribute encryption products will render [our] controls immaterial." -- 1999: USA, FVEY, et al https://www.google.com/search?tbm=isch&q=not+dead+yet https://www.google.com/search?tbm=isch&q=kill+it

1 0

Re: There's this really kewl mesh network that's being deployed world-wide...
by Shelley 06 Jul '15

06 Jul '15

On July 5, 2015 8:46:53 AM Seth <list(a)sysfu.com> wrote: > > This is true. For those that don't have the time or desire or watch, some > takeaways: TY for the summary. I block all things goog but suspected this was the topic; agree with your comments. Yes, because they have neglected the basic infrastructure for decades & discourage the use of individual solar/etc., some otherwise sensible people are welcoming the idea of these spy boxes - because their bullshit propaganda is designed to appeal to those of us who are concerned about the environment. Oh sure, why would I mind if "the grid" reschedules my laundry to an "off-peak" time? It'll save me money (*always* the hook, if the environmental concern-troll act fails), and I'm not home anyway, right? Oh wait, they know when I'm not home... they also know: when I wake up, which appliances I use and when, whether I have had an overnight guest, when I leave and for how long I am gone, (which they can combine with transit pass records- which some employers have integrated with electronic, RFID-polluted work IDs so there is almost no avoiding it unless you take active measures to do so, which then invites further spook scrutiny), credit card purchases and surveillance cam info (interconnected by TrapWire [0] to know where I've been & what I've been doing all day, so even if you leave your universal tracking device at home, walk/bike everywhere and pay with cash/BTC, you are still tracked-as-fuck), when I get home, what I read or watch and listen to, when I go to sleep, and with whom ... If your municipality hasn't yet deployed these spy boxes, do what you can to slow their roll out! Is this what you want (in addition to the very real detrimental health effects already mentioned?) I live in one of the most liberal, progressive cities around and initially they'd treated us as some conspiracy theorists when a few of us raised concerns about the unnecessary collection of data, the security of the transmission of said data & who will have access to it and the health concerns. Now they've been scheduling dog & pony show community meetings to "address our concerns," and attending one probably puts you on the same list as going to a 2600 meeting... They are supposed to begin the deployment of these spy boxes here in 2016-17 and I'll be damned if they'll put one on my abode. For being such an inconvenient troublemaker, they'll charge $50 or more per billing cycle (final amount is as yet undecided.) This is total bullshit. They can upgrade "the grid" without making it a universal spying network, but why would they when sheeple don't complain and push back? [0] https://publicintelligence.net/unravelling-trapwire/ http://www.wired.com/2012/08/trapwire-strafor-biz/ -S > The biggest takeaway is that jig is up with the current business model of > centralized power distribution. The growth of decentralized power > production (home solar etc) is driving a stake into the heart of the beast. > > The power company execs know this openly admit as much. So they are > changing business models to one of CENTRALIZED DATA HARVESTING AND > SURVEILLANCE. > > 'smart meters' are a massive and global offensive thrust of the 'Internet > of Things' surveillance state and control grid directly into the home. > They form a mesh network on the 900Mhz band. They are supposed to have > 2.4Ghz radio (not yet widely activated) for extracting surveillance data > and controlling 'smart' appliances in the home. > > I use the term 'smart' in quotes because it is a goddamn propaganda term > and needs to be replaced in the popular culture as soon as possible with > something more apt and mocking, say 'evil-genius'. I will use the term > 'evil-genius' meters from now on. > > Anyways, these evil-genius meters douse your house with something on the > order of 40,000 microwave pulses a day. The meters are built in China, and > allegedly have not had any real safety testing done on them. > > The AC-DC converters used to power the evil genius brain in these devices > is supposedly a crap one and generates a significant power waste along > with 'dirty electricity' (that is a choppy or rough sine wave instead of > smooth clean one) which radiates throughout the home via the electrical > wiring. > > The legal principle of 'implied consent' being used to justify the stealth > installation of the meters world wide is a very shaky one. The vast > majority of people that are having these meters installed on their homes > by the power company are complete unaware of what is going on. It's a > classic trojan horse. > > It's also a contractual violation. To have a valid contract there must be > an offer, consideration, and acceptance. There is none of this with the > evil-genius meter roll-outs. They simply are putting them in without > asking the customer for permission. > > Depending on the jurisdiction, you can refuse the evil-genius meter, but > then you're hit with an extortionate monthly 'meter reading' fee, which > was not charged before the evil-genius meter roll-out began. > > Some people in the Los Angeles area that have refused evil-genius meter > installation, have been locked into months long battle with the utility > company and consequently LIVING WITHOUT ELECTRICITY for months on end. Now > that is some crazy shit, now matter how you slice it. > > WHY are the companies so adamant about having these devices installed to > the point where they're willing to cut off a resister's power for months > on end, and foregoing that revenue? Perhaps to make an example out of them? > > I could go on and on. > > If you anybody that sleeps in a room next to one of these devices, > *especially* if they are pregnant women or young children, get them the > fuck away from it as soon as possible, ideally by having the device > removed and replaced with an analog one, or by changing rooms or living > locations.

5 4

Will Greece goo boom?
by Georgi Guninski 06 Jul '15

06 Jul '15

I am wondering: Will Greece go boom relatively soon? The reasons are Greece owns significant amounts of money (like the u$a) and they can't pay. This might be an opportunity to see how a country goes boom in modern times (after we know know what happens to cities like Detroit).

1 1

Dead Tree Lovers -- Call for Books
by Moritz 05 Jul '15

05 Jul '15

DEAD TREE LOVERS -- CALL FOR BOOKS _________________________________________________________ ||-------------------------------------------------------|| ||.--. .-._ .----. || |||==|____| |H|___ .---.___|""""|_____.--.___ || ||| |====| | |xxx|_ |+++|=-=|_ _|-=+=-|==|---||| |||==| | | | | \ | | |_\/_| | | ^ ||| ||| | | | | |\ \ .--. | |=-=|_/\_|-=+=-| | ^ ||| ||| | | | | |_\ \_( oo )| | | | | | ^ ||| |||==|====| |H|xxx| \ \ |''| |+++|=-=|""""|-=+=-|==|---||| ||`--^----'-^-^---' `-' "" '---^---^----^-----^--^---^|| ||-------------------------------------------------------|| ||-------------------------------------------------------|| || ___ .-.__.-----. .---.|| || |===| .---. __ .---| |XX|<(*)>|_|^^^||| || , /(| |_|III|__|''|__|:x:|=| | |=| ||| || _a'{ / (|===|+| |++| |==| | | | | | ||| || '/\\/ _(|===|-| | |''| |:x:|=| | | | ||| ||_____ -\{___(| |-| | | | | | | | | | ||| || _(____)|===|+|[I]|DK|''|==|:x:|=|XX|<(*)>|=|^^^||| || `---^-^---^--^--'--^---^-^--^-----^-^---^|| ||-------------------------------------------------------|| ||_______________________________________________________|| tl;dr: We want your books. Send them to us. In December 2014, over 500 books were brought to Chaos Communication Congress in Hamburg for an experiment: During the busy days of Congress, with over 12.000 visitors, how will people react to a library of dead trees? In partnership with La Quadrature Du Thé and the Congress team, a cozy reading area was set up on the fourth floor. For us Dead Tree Lovers, to see all seats and carpet space occupied almost 24/7 by interested readers filled us with delight. The library lives on! And has considerably grown since. The database now contains over 666 titles. As a travelling library, we will bring it to places near you, to hacker events and hackerspaces, to other public spaces. It is currently hosted and accessible around the clock at OpenLab Augsburg, Germany, for free borrowing or cheap purchase, replacing existing books by other used copies. The database is limited in that it does not yet contain all of the historical material that we have so far collected on the earlier days of hacking, pre-80s. Thanks to Werner Pieper, a friend of Wau Holland and publisher, we have started to add rare material from the good old times when hacking was part of the broader political counterculture movement and not yet mainstream. Thanks to the CCC, we are now hosting a complete paper archive of the Chaos Computer Club publication 'Die Datenschleuder'. The Humanistische Union (HU) donated most (all?) of their publications. WE WANT MORE. The library needs your help. Please send us your books and reading suggestions for us to hunt down paper copies! Or better yet, send us offers first. We're open for anything tech, political, scifi, as long as you feel it influenced your life profoundly and is worth reading. The focus is hacker culture and its history in the broader sense. It is not necessary to give your books away forever, we can log the source and return it if and when you want it back. Dead Tree Lovers c/o OpenLab Augsburg e.V. Elisenstrasse 1 D-86159 Augsburg, Germany JOIN! We have started a mailing list to discuss all kinds of book matters: book scanning, library software (or lack thereof), book recommendations etc. the DTL team // July 2015 --------------------------------------------------------- irc.hackint.org #deadtreelovers https://wiki.hackerspaces.org/Dead_Tree_Lovers https://www.librarything.com/catalog/hacklib https://lists.hackerspaces.org/mailman/listinfo/deadtreelovers rss: https://www.librarything.com/rss/recent/hacklib twitter: https://twitter.com/hacklibrary

1 0

Stop Watching Us
by grarpamp 05 Jul '15

05 Jul '15

Other video... from 2013... https://www.youtube.com/results?search_query=stop+watching+us https://www.youtube.com/watch?v=0cxPEf9ZWIo Protests always generate interesting youtube chats with many people.

1 0

Bitcoin Book Review
by John Young 04 Jul '15

04 Jul '15

http://www.nytimes.com/2015/07/05/books/review/nathaniel-poppers-digital-go… Quote: The most poignant moment in the book comes when Popper contrasts a conference for the more ideologically minded Bitcoiners at a racetrack on the outskirts of Austin, where Ulbricht grew up, with the gathering of the rich and powerful at the South by Southwest festival, where Ulbrichts mother is politely dismissed as she pleads for funds to help defray her sons legal costs. It was an unhappy reminder of a side of Bitcoin that its new adherents wanted to put behind them, Popper writes. And as he notes, If this was the new world, it didnt seem all that different from the old one at least not yet. Nor can Digital Gold be a tale with a satisfying ending, because the future of Bitcoin is unknowable right now. As the venture capitalist Barry Silbert says at a Goldman Sachs conference, Bitcoin is either going to change everything, or nothing. But if Bitcoin doesnt change everything, people will keep trying to find something that will, and so Poppers book stands as necessary reading, and very intriguing at that, regardless of the eventual fate of his subject. Unquote.

3 2

Announcement: Replicated Encrypted PasteBin
by ryan.pear＠ownbay.net 04 Jul '15

04 Jul '15

It's been a while since code was announced on cypherpunks... RepBin: https://github.com/repbin/repbin/tree/v0.0.1 Repbin is an encrypted pastebin for the command line that runs over Tor! Repbin servers form a distributed network where nodes sync posts with each other (like in Usenet or BBS/Fido systems). This makes Repbin resilient and scalable. Repbin focuses on privacy (encrypted messages) and anonymity (padding and repost chains). Features -------- - Forward secure encryption of posts using DHE-curve25519. Even a compromised long-term key does not allow to decrypt old posts. - Integrity protection of posts using HMAC-SHA256. You can be sure that posts have not been tampered with. - Confidentiality of posts using AES256-CTR. Without the recipient key, nobody can read the post. - All posts are padded to a common size. That means that posts are not distinguishable by their size when looking ``on the wire''. - Post are replicated between all servers in the Repbin network. - Optional constant receiver keys for post-box functionality. - Receiver key attributes for synchronization and post-box authentication. - Resource control via hashcash (sha256) and ed25519. - Some privacy protection by using Tor for all communication and ephemeral keys. - undocumented goodies. Post a file ----------- $ cat FILE | repclient As a response you will receive output like this: Pastebin Address: http://bvuk3xmvslx3idcj.onion/3x77hJtt42MkGbs18e1ZvBw9oAftAUrr9K9x4E8rQzed_… Simply give the Pastebin Address to whoever should gain access to the file. Fetch: $ repclient http://bvuk3xmvslx3idcj.onion/3x77hJtt42MkGbs18e1ZvBw9oAftAUrr9K9x4E8rQzed_… Installation ------------ Client software to send and receive file: $ go get -u github.com/repbin/repbin/cmd/repclient Peering ------- If you are an experienced UNIX sysadmin, please consider running your own Repbin server to help the Repbin network. While running a server requires hardly any interaction, setting up a server in the Repbin network requires at least one manual peering agreement with another server in the network. This is a time-tested architecture which is used successfully to run the Internet, the Usenet, and BBS networks like FidoNet. To set up a peering you have to exchange public peering keys with another server and configure your server accordingly. To get in touch with us for peering send a message to 7VW3oPLzQc7VS2anLyDtrdARDdSwa7QTF7h3N2t6J2VN_AjWZQfHoqK3yNqvXPkcswLNXSzFrCzJuRRKZKvY71UWT and don't forget to put your own key into the message. The server installation and the peering process is described in detail in the documentation. Here be dragons... ------------------ Dive deeper into the documentation and the code, if you want to figure out how to send repost messages (remailer style) and how to run your own reposter service! WARNING ------- THIS SOFTWARE HAS NEVER BEEN AUDITED OR REVIEWED. IT HAS NOT BEEN TESTED. THE AUTHORS ARE AMATEURS AND YOU SHOULD NOT USE THIS SOFTWARE FOR ANYTHING IMPORTANT. YOU SHOULD NOT RELY ON THE SOFTWARE TO WORK AT ALL, OR IN ANY PREDICTABLE WAY, NOR SHOULD YOU ASSUME THAT THE FEATURES CLAIMED ARE THE FEATURES IMPLEMENTED. THIS SOFTWARE IS FULL OF ERRORS, THE ARCHITECTURE AND DESIGN ARE BROKEN. UNLESS SOME EXPERT CLAIMS OTHERWISE.

1 0