hyperplane

Or they're simply under investor pressure to put on those big boy pants over achieving feature parity.

Forgive my ignorance, but who is doing the blocking? Is it American sites willingly censoring for legal reasons, or is the Cuban government blocking them for the country's own ISP?

For as much as AMD shows promise in their graphics line, if one thing is clear it is that the Bulldozer architecture has been a humiliating failure on the CPU side: extremely high TDPs and terrible performance vs. equivalent Intel *y Bridge/Haswell cores. It's been universally panned for most workloads since its release date made worse by AMD's marketing efforts leading up to its launch.

I wonder what has happened to the Bulldozer design team at AMD at this point and whether or not they even still work there at all.

Nope. Unless it's something I need to keep around (taxes, insurance, usual "business of life" things,) I don't keep any of my email, messages, etc. for more than a few months at best. Nostalgia can prove to be an enemy of progress, and not having a lot of things to look back on keeps me focused on the future.

The original essay on Stross's blog that led to that FP article is linked in Schneier's post.

If this is going to become a pattern, it probably makes more sense to allow the browser chrome to be manipulated in a way so progress bars aren't redundant (i.e. 'pjax' style loading uses the same bar as if you did a real page load, just like pushState allows for history manipulation.)

It would be cooler to see some guys get together and make a de facto standard, and then implement this type of control into extensions for FF/Chrome.

> Maybe there are better ways of monetising than forcing multiple pages of ads down your users throats? :)

Kill the CPM model and your wish will come true. Unfortunately, advertisers often first ask "Well how many pageviews does your <site/app/whatever> have?" Most advertising metrics are still stuck 10 years behind where we are and where we're going.

> The cost of healthcare alone makes subsistence living impossible.

No. Subsistence living is entirely possible - there are millions of people doing just that somewhere in backwoods wherever, across a multitude of political systems and states, all over the world.

What you want as "subsistence living" is not its definition. What you're talking about is "how much labor cost it requires to maintain your current lifestyle in this current political system".

EDIT: I was late on this reply I guess.

You don't see it in Singapore because Singapore is a heavily-controlled state where tons of things are capital offenses and you are subjected to physical violence (caning) for things as minor as vandalism.

Nice opinions, but the primary feeling I get from this is "Designers are closed-minded prima donnas, and the only way to work with them is to talk their language and care about the same things they do."

As far as I am concerned, the primary job of a designer is communicating a message. If anything, designers should probably be given less slack over time for their personality flaws, because their whole job revolves around communication and empathy toward a user.

Why not reflect that same empathy inward toward the company? If your design team is the center of your empathy toward your users, your design team should equally be trying to lead positive communication efforts with engineers and PMs to find a common ground, build a common vocabulary, and understand everyone's stake in the game from the onset in a diplomatic and friendly fashion, especially so as the designer becomes senior. After all, what problem is more abstract than the meta-problem of intergroup communication?

I don't think posts like this help construct meaningful dialogue between departments and only serve to reinforce existing clique-oriented behavior. Interdepartmental/inter-role communication is "us vs. them" only if these types of attitudes are allowed to foster in the corporate culture.

Brilliant advice, but I would (optimistically) assume that Coinbase is doing some or most of these things? Fraud is a pretty well-solved problem for most payment processors.

It's a "user-friendly" feature that sacrifices some of Coinbase's own bottom line (and security) for the sake of those that want convenience over security. I wouldn't be scared unless this is enabled on your account. (In fact, from the usability end, it should require some serious hurdles to be enabled in the first place for that reason, to protect against unauthorized enabling.)

The sacrifice for Coinbase seems to be that the people that would enable this feature are accustomed to calling up Visa/MC, reporting a fraudulent transaction, and getting their money back + an affidavit in the mail, so Coinbase will have to be able to cover a fraudulent bottom line either out of their own finances or a good insurance policy.

It would be nice to have a better explanation of the types of problems being solved here, because the security space is so massive.

Is this websec? appsec? Reverse engineering?