This is parse but for backbone instead of mobile?
24 karma · joined October 9, 2011
I feel like there's a huge gulf between second and third wave feminists. Modern ones would find the above comment empowering, you only react in this way if you've been brought up in a society and culture that demeans female sexuality and teaches you that low cut dresses implies slutiness and so on.
Obviously music cannot follow this model, meaning sounds themselves (in the context of the essay sounds are not so different from smells) will become un-ownable and the only thing left having any value will be live performances. Artists could still make a good living if they are any good at it. It would be the same as what we had a few hundred years ago before mass media, and the music industry would transform from a creative industry into a service industry.
Of course this is just my impression of what pg means, I don't want to put words into his mouth.
Badges need to enhance the application not interrupt it. I have never seen a badge application pause the application to award you with the badge. The entire concept is pretty nuts. It's a good idea, such a shame about the implementation.
Mozilla can easily provide an interface to delete badges you don't want, or ban applications that spam you from the badge system. The whole threat model idea is just self-sabotage.
The reason we're even presenting the user with a dialog is because we want to prevent badge spamming, whereby third-party issuers spam a user's backpack with badges that they don't want. Consequently, we need the backpack to ask for the user's consent. This will be accomplished via an iframe embedded in the issuer's page.
The only sensitive information that a user needs to enter in this flow is login credentials. Since authentication is done via BrowserID, which opens in a pop-up window, the consequences of spoof attacks are minimal–so long as the user knows to look at domain names in their address bar and BrowserID's UI."
I was really interested until I got to this part. Asking the user for permission each time I want to award a badge? Complete fail. Mozilla doesn't get UI.
I estimate the chance of a legitimate file being deleted by this process at 1% or less.
I'm sorry, but there's only 1 reason why you would remove a link to an infringing file but not the actual file. Aiding piracy.
Here's a HTML5 example:
One of the main practical problems is that websockets take a second or 2 to start up, clearly too slow.
That's the kind of game we need.
Our only regret now is not having moved to node.js sooner.