Create

http://www.bbc.com/news/world-35961422

We begin therefore where they are determined not to end, with the question whether any form of democratic self-government, anywhere, is consistent with the kind of massive, pervasive, surveillance into which the Unites States government has led not only us but the world.

This should not actually be a complicated inquiry.

https://www.theguardian.com/technology/2014/may/27/-sp-priva...

Employee is held on suspicion of ‘extracting confidential information’ from law firm at centre of Panama Papers

https://www.theguardian.com/world/2016/jun/15/mossack-fonsec...

https://www.linuxjournal.com/content/nsa-linux-journal-extre...

http://www.dw.com/en/david-petraeus-the-washington-elite-hav...

https://www.theguardian.com/world/2014/feb/04/us-nsa-gerhard...

In February 2014, the Swiss voted in a referendum to introduce quotas for all migrants in Switzerland. The referendum, which requires Switzerland to have annual quotas for immigrants, does not take effect immediately but requires the Swiss government to implement a quota system within three years.

Nothing to do with regional unemployment offices.

https://en.wikipedia.org/wiki/Freedom_of_movement_for_worker...

You are suggesting, that Malta^2 is to command the ECB?

^1 https://en.wikipedia.org/wiki/Languages_of_the_European_Unio... -- working is not the same as official

^2 or Ireland for that matter...

Second thought: maybe English could merit a semi-official status though (if May succeeds). But most certainly not a working language (neither an official one).

brexit means brexit: since English is not native to any remaining EU member country, drop it as an EU working language. With special regard to the European Central Bank (banking passport system). Irish could still remain as an official language^1, but the semi-official Welsh would need to go too.

^1 For Preventing The Children of Poor People in Ireland From Being a Burden to Their Parents or Country, and For Making Them Beneficial to The Public

https://www.youtube.com/watch?v=j7zzQpvoYcQ https://www.cmu.edu/randyslecture/book/

I consider myself lucky to have had the opportunity to work with you and learn an awful lot along the way. Thanks!

Four 3Gbps SATA connections

Two PCI Express root complexes

http://www.ti.com/devnet/docs/catalog/thirdpartydevtoolfolde...

https://github.com/hoglet67/PiTubeClient/tree/master/NS32016

...hopefully they will find their way back to BeebEm for Unix and run PanOS with BCPL

http://cpu-ns32k.net/Panos.html

The Parliament was and still is weaker than the Commission and the Council, the latter two usually work in tandem anyway. (Actually, the swpat rejection by the EP wasn't about values, but rather an attempt to demonstrate capabilities, unseen before or after for that matter, see belgacom).

https://www.theguardian.com/world/2013/nov/07/nsa-gchq-surve...

What was the consequence for those behind?

https://www.theguardian.com/world/2015/nov/06/security-and-l...

In a democracy you need to be informed (see NHS campaign). That is incompatible with W. Lippmann's Society of the Spectacle, privacy and freedom of thought.

McCreevy, déçu de voir ses arguments taillés en pièces, ne prenne la parole, le visage rougeaud, sur un ton énervé:

"Monsieur Rocard, si c'est la guerre que vous voulez, vous allez l'avoir."

Réponse de Rocard, d'un ton posé et ferme: "Monsieur McCreevy, des guerres, dans ma carrière, j'en ai déjà arrêté deux. Mais ce n'est pas parce que je suis un homme de paix que je céderai à l'intimidation. Je maintiens donc mes positions."

This is the key point to argue against in the context of people, privacy and mass surveillance.

It is the touchstone of privacy, anonymity and crowd protection.

Regarding noise suppression: yes, the more queries (available data whether raw or extracted) the more you can filter (ask a Kalman student) to reduce your error bars and margins. This is a reason why DP is overhyped. Also, if there are no differences between queries, then data is redundant. See deduplication (database) or scaling (measurement).

About the analysis pipeline: this is why the mantra "know your detector". Coincidentally, this is why releasing only recorded datasets is next to useless for people outside the given research group. You would need to capture detailed knowledge of your data taking operations and instruments, which happens rarely, if ever. Please cite a thing such as "the NASA pipeline", perhaps you mean a given mission/experiment? In any case, detector recalibration is a usual, almost daily activity...

But as you say: your "aggregate analysis" NEEDS "many different samples from different stars". Commonality is the result of your analysis based on different samples. But since they are common, you can go and sample and have the result without doing mass surveillance on every star.

ps: I am fully aware of photo stacking, but also note, that stars are not humans, see context of privacy. Please look at argus or sdcMicroGUI from CRAN to get a feeling for data utility vs. reidentification risk.

Adding noise and fuzzing has a long history in statistics since the '70s [1], and while it does work on large numbers, it almost always messes up the details ie. the error bars.

C.D. DP is essentially a cheap ripoff of the ideas implemented in ARGUS[2].

[1] 1977 Dalenius, see Do Not Fold, Spindle or Mutilate movement and earlier:

http://tpscongress.indiana.edu/impact-of-congress/gallery/fi...

[2] http://neon.vb.cbs.nl/casc/

We begin therefore where they are determined not to end, with the question whether any form of democratic self-government, anywhere, is consistent with the kind of massive, pervasive, surveillance into which the Unites States government has led not only us but the world.

This should not actually be a complicated inquiry.

https://archive.org/details/EbenMoglen-WhyFreedomOfThoughtRe...

Surveillance is not an end toward totalitarianism, it is totalitarianism itself.

https://www.washingtonpost.com/world/national-security/nsa-i...

For most of my career I worked on contracts that had already been awarded, so the inner workings of the program office were completely opaque to me (and still are to this day). By the time I got involved in a project the contract had already been awarded according to a proposal that had been generated by some mysterious process that I never fully understood, and which I never actually saw. All I knew was that my line management gave me a set of account numbers, and I wrote those account numbers down on my time card, and I got paid every other week. And this was true of most of the rank-and-file engineers that I worked with.

The result of this opacity was that the incentives and reward structure for individual employees was often in direct conflict with the goals of the Lab and NASA. For example, one of the factors that went into my performance review every year was how many papers I had published. In fact, this was one of the major considerations because it was one of the few things that management could get a quantitative handle on. So naturally I put a lot of effort into getting published. The problem is that the things you have to do in order to get published are often very different from the things you have to do in order to actually be productive on a NASA project. Getting published requires getting approval from your academic peers, who work for different institutions, often competing for the same contracts that your institution is trying to win. The result is a lot of politics and mutual back-scratching (and back-stabbing), because those are often more effective strategies to get papers published than actually doing worthwhile research.

[...]

At the peak of my JPL career I attained the rank of Principal, which is the highest rung on the technical career ladder whose existence is publicly known. (It turns out there are "secret" promotions you can get after that.) It's essentially the equivalent of getting tenure at a university, only with no teaching responsibilities. The decision to promote someone to Principal is made by a committee. I never found out who was on that committee, or what criteria they used to make the decision. But whoever they were, they had the power to render me more or less un-fireable, despite the fact that by then I was not really contributing anything to the Lab's mission.

http://blog.rongarret.info/2008/09/failure-must-always-be-op...

Those who are at the receiving end of the job delegation process report to several managers, none of whom need to take responsibility. Therefore only the one who reports can take hits, as in hightail (see win-win analysis of The Office on ribbonfarm). Obviously success is management's success, not least of the DG.

CERN management proper on the other hand is a tightly knit group (not talking about external contributors, “users” in CERN parlance) with the same level of transparency that need-to-know mechanisms allow for. There are even line-managers and the whole lot. Gianotti was earmarked for leadership position two or three decades ago and has been at CERN since her early twenties. Her external institute affiliation is just a mere formality in the sense that Italy has financially contributed to the CERN budget.

Make no mistake: there is a chain of command, but one that is heavily concealed behind a thick layer of administration (see ribbonfarm) protecting management. There are whole departments and groups devoted to implement the five questions you are wondering about.

http://www.hanno.jp/gotom/Cint.html

(Saber-C, the Saber company has become Centerline, and the software itself has been renamed to CodeCenter. saber, xsaber, and sabertool have become codecenter, xcodecenter, and codetool. DEC offered Saber-C on ULTRIX. It never appeared to do very well in the marketplace, which is some kind of tragedy. It was, and is, a terrific piece of software. The fact that a product as useful as Saber-C could fail to do well in the market is an indicator of the impoverishment of software "engineering" practices industry-wide. Anyway, it ended up being ObjectCenter from Integrated Computer Solutions doing C++ and having an IDE with class browsing, with xobjectcenter)

cint (M. G.) was in maintenance-mode for a long time by then.

ph-sft group was more for python (P. M.), and fnal wanted llvm/c++ (P.C.).

fnal then put down the money for an IC contract (A.N.) at ph-sft for the llvm/c++ based implementation and joined the iso body.

cling is almost orthogonal to the whole ROOT mess (graphics, histogramming, partially the analysis etc.)

Are you a passionate engineer who is at ease with powerful high voltage equipment? Are you ready to become a key player in the design, development, production, installation and commissioning of some of the largest power converters in the world? Take part!

http://jobs.web.cern.ch/job/11871

Blaming a bird or a small mammal makes cute propaganda. This wasn't always the case: in 1999 three breakdowns have occurred in 18 kV transformers, causing major power cuts and beam losses totalling 3.5 days. Animals didn't take the blame in 2008 for the failure of a power transformer on one of the surface points of the LHC.

And a warning to non-western members:

"The cost [...] has been evaluated, taking into account realistic labor prices in different countries. The total cost is X (with a western equivalent value of Y) [where Y>X]

source: LHCb calorimeters : Technical Design Report

ISBN: 9290831693 cdsweb.cern.ch/record/494264

On top of the above treatment, the usual package for prospective employees:

Resolution of the CERN Staff Council

- the Management does not propose to align the level of basic CERN salaries with those chosen as the basis for comparison;

- in the new career system a large fraction of the staff will have their advancement prospects, and consequently the level of their pension, reduced with respect to the current MARS system;

- the overall reduction of the advancement budget will have a negative impact on the contributions to the CERN Health Insurance System (CHIS);

http://cds.cern.ch/journal/CERNBulletin/2015/46/Staff%20Asso....

Pensions which will be applicable to new recruits as of 1 January 2012; the Management and CERN Council adopted without any concertation and decided in June 2011 to adopt very unfavourable mesures for new recruits. http://www.gac-epa.org/History/Bulletins/42-2012-04/Bulletin....

La Suisse pourrait contribuer à améliorer les conditions sociales des travailleurs détachés du CERN. Le Conseil fédéral est prêt à évoquer la question avec l'organisation.