1,134 karma · joined August 22, 2011
Having worked directly under the SVP of Business Intelligence & Analytics at one of the larger US-based social networks I can say from experience that it's really, really hard to get people to consider the things that are hard to measure or hard to interpret. Even in a company that's heavily analytics-driven there's a lot of magical thinking, a lot of anecdata, and a strong bias towards short term effects. Think of it as the marketing equivalent of laying off 20% of your workforce, telling everyone else to work 25% harder, and convincing Wall Street this means profits will go up and stay up.
It's easy to spot the bump in your balance sheet from lower costs and it's hard to quantify the long term costs of decreased morale, lower total productivity, most likely lower individual productivity, attrition, and inability to take advantage of opportunities.
"Google long maintained that the engineer was solely responsible for this aspect of the project, which resulted in official investigations, some still unresolved, in more than a dozen countries. But a complete version of the F.C.C.’s report, released by Google on Saturday, has cast doubt on that explanation, saying that the engineer informed at least one superior and that seven engineers who worked on the code were all in a position to know what was going on." - http://www.nytimes.com/2012/05/01/technology/engineer-in-goo...
* Killer drones. Ubiquitous surveillance by both government & business.
* Bad data that destroys one's ability to travel, get credit, find work, or avoid being thrown into jail out of nowhere.
* More and more armed citizens shooting each other over minor things.
* Flash mobs for every purpose under the sun.
* Samizdata.
* Manipulating the cops into raiding innocent targets while using software to conceal your identity. Absolute and complete lack of airships.
* Corporate domination of the political process with unlimited donations.
* Massive and growing wealth inequality.
* Political campaigns severally wounded by software failures.
* "You're not the customer, you're the product."
* DDOS for commercial advantage.
* Arresting people as "terrorists" to seize embarrassing stolen information.
* International treaties negotiated at the behest of corporations as backdoors to subverting the legislative process.
* No-recruit agreements for the rank & file combined with vicious competition for the top talent. People carrying half their life in portable computer devices.
* Ransomware in a myriad of forms.
* Vast government computer intrusion programs.
* Criminalization of access and dissemination of public information. Criminalization of downloading too much from something you've got access rights to. Criminalization of downloading from open directories with no warnings on them.
* New diseases, rising seas, freakish weather.
* A resurgent, militaristic Russia invading various countries.
* A resurgent, militaristic USA invading various countries.
Admittedly the cyberware is a bit slow in coming, AI is still the same 10 years off as always, self-driving cars are barely at the testing stage, sub-orbital planes are a pipe dream, and nobod thinks the Net looks like brightly colored blocks, but it's still unsettlingly close.Against DNSSEC + certificate records:
1) There's a centralized PKI administration issue, but less so than the current CA morass 2) Administrative/rubber hose/legal/monetary compromise of the DNS root administrators (currently US NTIA) would allow substitution of the TLD keys, but this would be blatantly obvious to every organization or individual paying attention 3) DNSSEC has some annoying properties with regard to name enumeration and such 4) Need to either use a primary resolver that supports DNSSEC (Google Public DNS and Comcast, among others) or do a separate query to one who does
For:
5) Minimal extra infrastructure, already supported in some libraries 6) Extremely cacheable with low resource requirements (root & TLD keys, MRU/MFU certs) 7) No need to add a new dependency on a previously untrusted source of code and crypto data 8) As long as the parent TLD has deployed DNSSEC the organization only needs to get their key set up, add a theoretical cert record, and sign records as needed.
I think issues 1 & 2 are at least as big a problem with DNSChain because in practice the hand-waving of how you pick a trusted DNSChain chain is ignoring a huge class of vulnerabilities. Issue 4 is still a win over implementing a large chunk of infrastructure or trusting okTurtles'. The "just use Javascript" bit seems to apply equally to either, though I guess the _query_ portion of DNSChain is relatively simple.
There's a maintained and actively developed fork at https://github.com/salamiwst/Panopticon-Forked
[Edit] Pano can also hibernate tabs or groups, so if that's the last thing you're using Bartab for it can replace that as well.
I think the house system was a mixed bag there, it kept some people closer to each other than was healthy but it also provided some level of support for a lot of us. I suspect things have gotten much worse since I was there, though. The only honor code I've ever seen work was the largely self-policed "No member of the Caltech community shall take unfair advantage of any other member of the Caltech community" and the administration was clearly communicating that they no longer expected students to be capable of following it. My impression is that the morale effects of that really cut into the effectiveness of a system that had helped keep pranks from escalating to the really dangerous or outright damaging, cheating low, and aggression of any form very rare. It was mostly worked because it was too simple to have real loopholes, the community fetishized it, we got a lot of benefits from keeping it working (take home finals, lab keys, etc.), and fundamentally it kept the peace. The administration still has a page describing it, but my impression is that as a social construct it's a hollow shell of what it was.
TL;DR? The house system was less damaging than most frats due to self-selection for house membership, but that also concentrated some really unhealthy behavior and the rest of us were already pretty broken without the houses helping.
[1] Short institutional memories confusing the issue further. [2] Fleming house members, basically stereotyped as Caltech's jocks at the time. I can't throw stones, I was a Mole and there were plenty of jokes about us, plus I almost dated a Flem.
Less flippantly I think that there may be a pretty strong correlation between these behaviors and personality disorders, but bullying and animal threat display behaviors are still relevant models. It's potentially a big mistake to confuse one of these people who is panicking and trying to use intimidation as a response with someone who has slipped into a state of irrational anger & obsession. The former can be dissuaded or possibly negotiated with, the latter is more likely to just keep escalating. In particular I'd presume that the latter are more likely to actually file the frivolous lawsuits and it's a higher priority to get everything locked down on the legal front. Generally a good idea anyway.
As for plugins, that's a bit more difficult - I wouldn't mind an option to ask if I wanted to let a site enumerate plugins, but you start getting into header games & pointless reloads there if you're not careful.
[1] I force my own fonts for everything, so no UX issues for me. No idea how much of an issue it is for other folks.
https://github.com/kazu-yamamoto/Mew http://www.mew.org/en/info/release/
Putting something into your clipboard is kind of annoying and could be a small security risk, but pulling the contents out is much worse. If it's a site you don't visit often it would be limited exposure, but if someone manages to hack Soundcloud/Pandora or inject JS into them you're talking about a lot of illicitly acquired information. Most of it may be useless, but it's a sucker-bet to assume no-one will get hurt by it.
It also occurs to me for the first time that the rise of pulseaudio was not that many years after laptops largely switched to integrated codec chips instead of discrete sound and I had all sorts of problems with those above and beyond the "Damn it, give me hardware volume controls" frustrations. It could have inherited some of the problems around quirky/flaky hardware that I remember ALSA facing in that period. At this point I just want something that can reliably play music or take audio input and for whatever reason pulseaudio isn't it for me. Hopefully that'll change before most distros switch to whatever the new hotness in sound setups is...
I guess my core complaint is that ALSA could be a pain to get working properly on a new system, but once it was working it didn't usually spontaneously break on me. PulseAudio was only slightly more likely to work out of the box, but was much more likely to break without my making any changes. I guess it's partially a sysadmin mindset, but I usually come down on the side of preferring up-front pain to long term unreliability. Perhaps I didn't use as wide a set of audio programs as you did, I didn't tend to run as many of them at once, or my hardware just had better drivers. For streaming sound (I didn't care about video) I usually stuck to network servers that could shove audio down a Shoutcast or http stream and listening with something like Amarok or MPD, I'm sure PA was nicer if you were trying to relay what your HTPC was playing back.
[ETA: I use linux consoles very heavily when I'm coding on a linux machine, I know this isn't exactly the most common behavior among more recent unix users.]
On the flip side this should have set off warning bells for them - it can be a little bit of a code smell to pick 1 for a configurable value in your encryption. Not always a bad choice, but 1 has a lot of properties that can simplify various mathematical operations and Basically setting a crypto value to the smallest positive integer (and a non-prime at that!) is like deciding that a set of numbers in your code should always be represented by two-byte signed ints. Sometimes that's _exactly_ what you want (say, various fast math libraries), but if you're doing general purpose code you should really stop and think about whether you might end up with a value outside that.
(1) The South China Morning Post out of Hong Kong broke the PacNet story: http://www.scmp.com/news/hong-kong/article/1266875/exclusive...
(1) Beyond her general profile in CS and administration a quick google check shows 136,000 hits for her name and 13,000 for "David Dyche", almost all of which appear to be someone else.