Of course the usual way has just been to use Flash, Java, Silverlight or some other NPAPI plug-in to provide the DRM. That API is 20 years old from Netscape Navigator 2.0 and honestly nobody likes it much. Microsoft has always pushed ActiveX for IE, Chrome prefers their PPAPI they launched 6 years ago and Firefox calls plug-ins a legacy technology. Many mobile browsers don't support traditional plug-ins of any kind. But it's not going to go away as long as it's the only way to play DRM'd content under Firefox.

So it's a compromise, you get the EME which is going to be a far more limited API isolated in a security sandbox to decrypt DRM'd video and audio streams and with that Firefox hopes to deprecate NPAPI and proprietary plugins for everything else. No flash, no java, no silverlight or anything like that just HTML/CSS/Javascript (open source) + EME (sandbox + closed source). It's just that it has never been in Mozilla's nature to compromise when there's overwhelming evidence they can't win, they'd rather stick by their guns and lose.

According to StatCounter, they had 32% marketshare in November 2009, now they're down to 17%. If you add in mobile where they have nearly no presence they're now fourth after Safari and IE. They're not going to achieve much of anything by pushing their remaining users away from them, it's the curse of populism. To actually be in a position to change anything, you must have the support of enough people to enact change. And in this particular case, I don't think they'll get many to join them in a boycott of Netflix and other DRM-using services.

Oh, there will be plans. Realistic plans? Well.... I've worked in a supporting role to some fairly big projects and there's a few things that strike me:

1) Huge projects generally have the biggest uncertainties. It'd be easy to think the opposite, the bigger the stakes the more sure you want to be that you're right but that's not really the case. While small to medium projects have some rather tangible goals under current conditions, the huge ones generally involve more conjecture on where the company, market and technology is going and is heavily mixed up with the corporate strategy. In addition they're a lot more one of the kind, unlike smaller projects where you have a lot more guidance and experience on how similar projects have been.

2) Huge projects typically involve a lot of major decisions that may be a boon to some parts of your organization while negatively affecting others, obviously this a major factor in political decisions but also internally you get a lot of actors who act in their own interest rather than the business as a whole, for example because it plans to eliminate or centralize some functions or focus on some technologies, products, services and locations in favor of others. Don't expect your SQL Server guru to be happy for a move to Oracle or vice versa.

3) As a consequence of points 1) and 2) above, you often get a lot of bad data as input. In particular, you tend to get a lot of overly optimistic estimates of costs, schedules and quality or that casually neglects to mention related costs that it is likely to incur and that are hard to fact-check while sales and savings are wildly exaggerated. Naturally the other side is equally biased in the other direction, so real neutral assessments are hard to come by. It doesn't help that the time scale is such that by the time failure is obvious many of the ones who made the decisions have left for other jobs or retired.

What's even worse is that in many cases the people who grossly oversold their position are the ones rewarded because it's incredibly hard to back out of a high visibility project, it's expensive and it makes the executives who agreed to it incompetent. Lesser projects and their owners/managers have the chance to be chewed out by their superiors, but when it goes all the way to the top you're way more likely to throw good money after bad to keep the project going rather than wave the white flag and declare it a miserable failure. That's how you get overruns of hundreds of millions of dollars and up.

NoCrack seems extremely vulnerable to a crack since they create decoys on the fly. It should be fairly trivial to pick it apart and tell when you're getting a real password from the vault. As for the stateless password managers, they operate without any kind of wallet which is their problem. Also you can't change password for any reason, that's a problem too. If you have a wallet most the problems go away. I'm thinking as follows:

The wallet stores a PRNG value to avoid various rainbow attacks. For each site/login the wallet stores a 128-bit PRNG and how to extract the the password from the hash.

Upon entering a password, the software shows you:
a) The fingerprint of SHA1(unique key+password) in some user friendly way so you might realize a mistyped password
b) For each site/login SHA1(unique key + password + site/login key).toBase64().substring(startPos, length)

For example,
When I generate the wallet, there's a random seed. Lets say it's
1234567890abcdef.
I add a site/login called "Slashdot" and it generates a site key:
1122334455667788

My password is "go fish"
When I type it in, it generates SHA1(1234567890abcdef + "go fish") = "PFr7t9qfAP9PFVG0+Vvbez82rW8=" and I know that if I type the password right it should start with PFr... something.

My hash for slashdot is SHA1(1234567890abcdef + 1122334455667788 + "go fish") = "8ktw2l8XVdI81/6TvEcg5EbxJ90="

I pick some part of that which satisifies this site's requirements like "ktw2l8XV" and the wallet stores (openly) that it'll take startPos = 2, length = 8. If nothing works because the site is weird, I can always generate a new site key and I'll get a new string to choose from.

If you type something other than "go fish", you'll get a different set of passwords but no indication whether it's right or wrong. Some of those passwords might fail the site's passwords requirements, but that's a very weak elimination.

Isn't that what this really boils down, not some bullshit about masculinity? Women watch soap operas because it's more exciting than their boring life, men play video games so we can be greater than the insignificant little peons that we are. And in porn the most beautiful women will perform for you even if you're fatter than the marshmallow man and uglier than a troll. We have immersive enough solutions that the body is fooled to play out almost all its chemical registry with endorphin, adrenaline, dopamine and so on letting you fake all the excitement and rewards as you slay imaginary dragons.

The problem is that it's addictive and desensitizing, if you're on a constant rush of awards and achievements and level-ups and whatnot then real life is a real downer. Not entirely unlike how I hear people on drugs describe coming off their high or how fat people act when they come off a sugar rush. So through a combination of actual reality check, batting outside your league because of failed self-perception and being poor at handling disinterest or rejection the result is often a painful face-plant. Once bitten, twice shy so you rather watch porn and play video games than try again.

I don't see how two of them should be meaningfully counted under any circumstances. They could just have it drive itself out of the parking lot and let a human do the rest, the autonomous system would never be at fault. If the car's not driving, it's just a plain old ordinary human-operated car. You don't count the miles, you don't count the accidents.

Actually only about 90% of accidents are attributed to driver error, the rest is mechanical failure like a tire blowing out or environmental like a tree falling across the road. And there's solo accidents and chain collisions, so it's not given that there's two parties involved. I don't know what the percentage is, but it's probably not 50%.

In theory or as in a representative sample of the driving population? I'm guessing it's pretty hard to get a good answer to what we would do. At any rate, my prediction is that we'd do better with one less fleshy driver instead of one more.

But this is exactly why a zombie site doesn't do any good. You need somebody to be your heir, which goes beyond simply the funds to keep the lights on. If you don't have any line of succession set up, make arrangements in your will to add a message to the site saying I've passed, here's a zip of the entire site, if you want to carry the torch feel free for your own name under your own domain. You can't just offer free money and a domain name, somebody will just take the money and use the domain for squatting for ad revenue. Or you could go the formal route and establish a trust, but I imagine that's overkill and the trust manager will take a fair chunk of cash for that.

It's already the default, at least in the US any "work prepared by an employee within the scope of his or her employment" belong to the company. That generally means anything done as part of your work duties or using company resources including but not limited to your working hours, computers or intellectual property. The courts will generally side against you if you come up with a solution for something that's naturally related to your job duties too, you can't research the problem at work then go home and write down the solution claiming it was independently developed.

He might be good friends with his boss, but his boss is probably going to send this to legal and from there it can go spectacularly bad. For example they might start to think he's disloyal and holding back things or stealing ideas to put in his own work for his would-be contractor life. I wouldn't try pulling off a stunt like this unless I'm prepared to be fired and anything you do make on your own gone over with a fine tooth comb. It might also go over a lot nicer than that, but I'd rather build a nest egg and take my chances as a contractor. What he's doing now seems high risk compared to that.

Probably something to do with average winnings/hand, playing more hands with the total winnings not increasing much makes the significance weaker.

Ah, I thought RAID1 would warn you somehow of bit flips which I assume would be the way heat-deteriorated storage would show up. Guess it won't, you'll need ZFS or something like that.

Bring laptop with SSD to Death Valley, leave it in the car stuck in the sun and go hiking. How long until your data is in trouble? However, I just looked at the specs for the Samsung 840 EVO, since it was the first to pop up:

Temperature
Operating: 0C to 70C
Non-Operating: -55C to 95C

I would assume the 95C is with data? It would be a rather small caveat if the drive survived but your data was fried.

Uhh... doesn't that mean that the RAID controller has to wait for the HDD on every read/write to verify it's the same as on the SSD, so effectively you get HDD performance?

Actually it's more traditional mass production at work, I do have a friend that works in the construction industry and modular housing is the big thing. Like for example bathrooms are fairly expensive with membranes, heat cables, tiles, plumbing and whatnot, the smaller ones just come on a trailer from a low cost country. Just hook up electricity, water and sewage and you're done. In apartment blocks they sometimes do whole apartments this way, for more custom buildings there's wall modules and such. Less and less is actually built on site, at best it's assembled.

And at least according to my friend though he might be somewhat biased but he's done both, the modular builds have fewer faults. Instead of unique builds depending on the job performance that day the modules have strong consistency and a pretty decent QA system. Even though the deliveries are more standardized the buyers are usually okay with that, just like there's a limited number of car models usually you're fine with getting one that suits your needs. What you need carpenters/plumbers/electricians for is now often aftermarket repairs/changes, not construction.

Huh, what? Project managers are typically generic drop-in process experts with PMP/Prince2 certification, there's usually a business analyst or reference group that are the subject matter experts. You might say project managers would do better with domain knowledge too, but that's ofte not the case unless it's just a side job to being the one designing/implementing it.

That's not really how it works, I don't know anyone who outsources one position. You make an assessment of your onshore team, you make an assessment of the offshore offering and you either do it or you don't. It doesn't matter if you're the star of the team or the glue that keeps them all together, if you're kicked to the curb it's all of you or none of you. Even if you're kept on you're just there to smoothen ruffled feathers until the offshore team are the ones running it, your new job is to be their coach until you've made yourself redundant.

For example, thought it's not outsourcing as such my government recently decided to move certain public offices out of the capital. This is a political move far, far above the individual employee and they do expect some competency will be lost but it's still going to happen. Individual skills will not protect against this, only practical or legal reasons why outsourcing is unfeasible. Any sensitive data for example is usually a giant PITA to move out of your jurisdiction to workers who aren't bound by your national laws. More practical reasons can be because you're working too close with the clients, they need on-site availability, it integrates too closely with hardware or anything else that makes on-site presence necessary.

Sadly this is a kick in the nuts to remote workers, as much as I'd really like a job I could do from anywhere I know then I'd also be in intense competition with the whole world. Because the value of my work doesn't come down to any of the above really, it comes down to supply and demand. Of course you can't expect massive demand but a stable niche you know they'll need for a long time where only a few can meet the requirements is usually a very safe spot. Like my current job I can't do shit from home, it's quite inconvenient but hell will freeze over before it's outsourced to India.