Hacker Newsnew | past | comments | ask | show | jobs | submit | hengli's commentslogin

This is parse but for backbone instead of mobile?


I have a backbone todo list running locally and hosting the data on parse. Setting it up took about a minute (good docs yay!).

I don't think you can provide this as a service though as I have my parse credentials in my js file.


Github and Twitter is where it's at.


I can't imagine trying to learn art and literature without formal higher education. Programming... maybe, but literature? no. But yeah, just because it's mandatory for literature doesn't mean it's mandatory for programming. However there's a distinction between programming and CS.


I need to do some web crawling, how does this compare to jsdom on node.js? I'm using node.js of course.


In my experience, using jsdom (and other similar node.js DOM libraries) is fine for scraping static content, but tends to fall down when you're dealing with anything that requires executing client-side JS. That's a big deal if you're scraping sites that load in content via XHR, or manipulate CSRF tokens in JS specifically to throw off static scrapers. Both of these are use cases that PhantomJS has handled beautifully for me in the past.


Those are just scraping tools. phantom is a browser, what your scripts see are exactly what the user would see. Makes it great for test automation. Casperjs is a fork focusing on testing.


I built a scraper that was nodejs and nowjs that sent instructions to a javascript bot I injected into the page rendered by phantomjs, the bot then scraped and sent snippets back to the server again via nowjs. The real win for me was it was a comet + ajax target which is usually hard to scrape efficiently but I just synced the bot with the comet updates and away we go. Also being headless I could just spin up 20 instances without any performance problems on a cheap rack server.


For example, if you need to scrape the DOM content for content loaded dynamically by JavaScript, PhantomJS will allow you to do the job. Or take snapshots of Web sites as they appear to users.


While subtle discrimination is really bad, how does she get from low cut dress to slut? That's surely something she came up with herself and nothing like that the guy intended. The guy certainly doesn't want her to wrap herself up in sweaters, why does she feel like that's how she should respond?

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.


My interpretation is that she felt the low cut dress comment was derogatory (like the term slut), and that the man, by sitting across from her in order to sexualize her, thought he was doing what she (the slut) wanted ("why else do women dress nice?"). If she weren't a slut, then her dress would be a dress, and there would be no reason to call attention to it, especially not in that way.

The guy doesn't want her to wrap herself in sweaters only because he wants to continue to objectify her, not because he sees her as a person that has the right to dress comfortably (as long as it's still appropriate).

What's empowering about being a sexual object if you want to be a programmer?


Korea has this already, I believe?



Interesting how lacking that article is compared to it's Wikipedia Brethren.


Probably some kind of super DRM. Think OnLive or the new Diablo 3 where you need to be on the internet to play.

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.


But if we're doing that will that really be that different from current client-server implementations?


"Threat Model

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.


Allowing providers to spam me with badges - complete fail.

I may well be interested in having you award me _a_ badge, but that doesn't mean I want you cluttering things up whenever you feel like it.

Mozilla's policy is that the user has control over their data, and I fully support that.


This is going to be more of a pain in the ass than Vista's Security popup or whatever it's called. It'll be the #1 way to make users hate using your application, I assure you.

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.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: