skysight-inc/HackerNews huggingface dataset:
To this day I still do not understand how this inane argument happened to be the single thing that killed OpenID. How is ‘cody.my-open-id-provider.com’ more confusing as a login than ‘cody@my-email-provider.com’? Hint: it’s not. I’m not one for conspiracy theories, but the whole URL-versus-email argument against OpenID seemed like the excuse various people used to put a nail in OpenID’s coffin when they didn’t like it for other less defensible reasons.
Oooh, sorry, I messed this one up. To clarify, I live in a 2br with a friend and it's $4k a month for the both of us. $2k a person.
A minor bug: One of your tabs is labelled IFrame, and seems to link to the contents of your iFrame.
They give you a token, you do a GET request to browserid.org with it and get the user's email, that's all. The user has to register their email with browserid.org first.
exactly. and even more worrisome, on-start shenanigans is tied to all kinds of sensors on your car. and it has a data connection. 24/7.
"On June 17, 2010, Sergey Ulasen was in his office in Belarus sifting through e-mail when a report caught his eye. A computer belonging to a customer in Iran was caught in a reboot loop — shutting down and restarting repeatedly despite efforts by operators to take control of it. It appeared the machine was infected with a virus."

I am curious as to what in Stuxnet code and/or the client computer caused this. From the rest of the article, Stuxnet went to great lengths to stay undetected. Anyone has clues ?
I have a very noob question. For most databases, suffix search is always super slow. However, can't someone just build an index based on the string reversed, then treat suffix search exactly the same way as prefix search? This doubles your index storage requirement. But index storage is generally not a problem. Finally this could be perhaps extended to cover any wildcard searches (hell*world)
10 Principles for Improving Government Transparency
I don't think the "launched the wrong app" is really that uncommon a use case. And after launching the wrong app and already being annoyed, the last thing I want is my phone to say "screw you" and make it harder for me to get to the app I intended.

There's also the use case where you have a related apps on the same screen or in the same folder. If you open a Facebook app, how likely is it that you'll want to check out Twitter next? If you get done checking the NYT headlines, might you want to open CNN or Flipboard next? Sick of Angry Birds so you open up Words With Friends? These scenarios don't seem that unlikely to me, but the "go to screen 1" behavior breaks them.
I think they're interconnected. Once people feel like they're "time-invested" in a game, they're much more willing to be financially invested in the game. The time investment warms them up and turns them into prospects much more willing to spend real money on the game they're already heavily invested in with their time.
>Ex: Many apps go to the browser, but the user might not remember which app sent them to the browser. They might have thought it was Twitter, when it was in fact the home screen.

This is exactly what I like about the back button. Frequently I'll finish an article I was reading in the browser but not remember immediately what brought me there. (This might happen if I had to interrupt reading it for a moment to pocket my phone and use two hands.) I'll have a sense I'm supposed to do something with it, but what? Did someone text it to me? Was it in a Gchat? Email?

"Well, that was a good article... why am I here, again?" I hit back, and find myself in an email with a link to the article. "Ah, yes, that's it! Joe emailed it to me." Now I can reply to Joe about it.

Maybe this wouldn't be as helpful to others, but I like it because I'm quite forgetful.
> Facebook got this right from the beginning.

What a weird double-standard. A feature of email (that you can have several, and you can change which one you use) is a failure, and a failure of Facebook (that it's one site, forever) is a feature?

We're all familiar with ways to migrate from one email address to another. If/when you leave Facebook/it disappears, how will you migrate your identity then?
This has been updated to say 1.3% in the article
I would agree with this. Google is up over $100 since G+ came out, so I think there will be some people eager to sell tomorrow to cash in on the strong uptick.
Hi, are you associated with the Plus Buddy site? There are two typos on the frontpage: "... and provides recommmendations of who to follow..." and "We'll recommned Google+ users ...".
The problem with "known" facts is they often extreamly context specific. There are actually a wide range of interview questions where I would much rather have someone say "I don't know" than say a correct answer without aproprate qualifications. Because even something as basic as how large is an int is can quickly lead to a bug when someone assumes the usual rules still apply.
Your definition of a design pattern is more precise than mine for sure. In FP its not "an abstracted, re-usable piece of functionality" unless it can be made into a library, as far as I know.

But it seems to me that FP forces you to look at programming in terms of what you are doing to transform data. In that case I can't see why having enough libraries won't do the job.
That's an interesting language stack you've displayed. You have Obj-C but not C/C++... From your selection, I'd guess you're either a web or mobile app dev?
I actually agree with a lot of stuff here. One should contribute to things that are useful for your job or your future, not spend time polishing your github resume.
My first ever programming project (I was 11) was basically this (edit: from a UI perspective, not under the hood), in PHP. I had no idea what I was doing, the architecture was questionable and at this point decentralization and OpenID were new and hot. It flopped horribly; it would have been a nightmare had it taken off, but it was fun.

My flow was basically this: website links to http://my-site/login?to=http://site.com/authenticate. User logs in against my MySQL database with an email I verified and a password. If successful, I generate a "ticket" number, my site makes an HTTP post to http://site.com/recevive with md5(ticket number + secret key) and the user's details, and then the user is redirected to http://site.com/authenticate?ticket=12345. Site.com verified the ticket using its API key and stuck it in its database. When the user hits site.com/authenticate, it looks it up by ticket number and has that person's details.

Obviously a terrible idea for a number of reasons (MD5, the race condition between the user and the ticket, and the reliance on my shared server being up) but my 11-year-old self thought it was pretty cool. Just thought I'd share.
I was living in Virginia for most of the period from 2000 to 2008. I had salary jobs and I had contractor jobs. I preferred contractor jobs, since they pay better (and I thought I could get by without health insurance -- always a dicey gamble). I slowly got better as a programmer during the years I was there. During the first few gigs I got, in 2000, I was a true novice, and trying to prove myself. I would charge a low, flat rate for projects, and I doubt my hourly rate was better than $20 an hour. I slowly raised that rate to $25 an hour and then $30 an hour. These seemed like huge steps forward at the time. The country was still deep in recession, and the tech sector had been hit very hard, so it wasn't a great time to get into tech with no resume. Somewhere around 2005 it became easy to raise rates, so I raised mine to $40 an hour and then $50 an hour. (Most of the work I did at this time involved websites and used the language PHP. There were a few exceptions, like a big Rails project in 2006, but PHP was the norm.) For whatever reason, I never seemed able to get more than $50 an hour while I was in Virginia. I did start picking up some freelance gigs in New York City, for which I could work for higher rates. I worked remotely. Then, in early 2009, I moved to New York City. I was working for a startup as a freelance contractor. I charged $100 an hour. For awhile New York City seemed somewhat safe from the recession. But the recession caught up with it. The startup I was with burned out, and then I had trouble finding work. Being unemployed, I tried to work on projects of my own. This is when I started wpquestions.com. I went to a lot of job interviews, but apparently the rate I wanted was too high for recession-era New York. I cut my rate to $75, and then to $70 and then to $65 and then to $60 and then to $55. Finally, I just really wanted a gig, so I cut my rate to $50 an hour. I ended up working a contract at winespectator.com. This involved diverse technologies; I was porting a Java/Oracle app to PHP/MySql, and then later I was porting a FileMaker database to PHP/MySql. I started looking for other gigs. Things had improved economically in New York City. I found I could raise my rates again. Everything I've been offered lately has been between $60 and $70 an hour. Again, all of this is contract work, with no health insurance.
Maybe StackOverflow should ask how the military does it.

You're not allowed to quit. It simplifies things a great deal.
Old TechCrunch + really fast, clean, customizable layouts
Spotify API (libspotify, metadata API)
Ah, but you were waaay ahead of your time! Now someone else (me) stole your thunder ;)
I don't know what to tell you. What's the difference between this and cheering at a sporting event? People draw tribal boundaries where they want to. (I'm reminded of The Onion t-shirt that says "the sports team from my area is superior to the sports team from your area").
How are they getting us to "share more", as the title says?
Now that Spotify is available in the US, this might be worth reposting.

Also stuff at: https://github.com/spotify
Have you ever clicked a trending topic on Twitter? Yes, people really are that vacuous. Lots of them.
used efCYNacLAS9NqMDz
Git is fundamentally pretty easy, but its terminology is confusing. Maybe this glossary helps:

commit: a snapshot of your files

tag: a reference to a commit

branch: a moving tag

HEAD: the current branch

index: the next unfinished commit

git-add: copy file(s) to index

git-commit: create a commit from the index

git-checkout: copy file(s) from a commit and redirect HEAD

git-reset: redirect current branch to another commit

git-revert: create new commit, which is the inverse of another commit

An interesting thing is that "the next commit" is an object you can work with in git. This concept is new for svn users. With git you can puzzle together a snapshot before it becomes a "real" commit. So mistakes like "Oops, i should not have commited that file" or "Oops, i forgot a little fix in another file" can be handled with git.
Is there some sort of account ID other than an email address? It looks like the email is all that gets sent to the website (although I didn't read deeply enough to be sure). If you change (add new, remove old) your email address at browserid.org then revisit a site you authenticated to before, what happens?
Key difference: Facebook has 750 million active users. Google+ has 10 million users.
One more general question to pile onto this -- what is a 'normal' junior developer salary, for someone fresh out with a bachelor's degree? I'm thinking $60k plus options(for a startup).
You can also filter posts by authors.
that's a really cool project at 11 years old, both in terms of your idea and what you can actually accomplish! off topic, but when i was 11 i had a c64 and basic and couldn't dream of talking to another computer unless i saved my program to the tape drive and had my mom drive me to my friend's house to load it on his c64.
I find this interesting because TPM's solutions reminds me of the classic UNIX "pipes and filters" strategy - a series of small components with well-defined inputs and outputs that can be strung together to produce a sophisticated result. (Of course, "small", "well-defined", and "sophisticated" could be relative terms.) The pipes and filters "API" was plain text transmitted through stdout.

It also strikes me as an example of software development becoming more deeply embedded in media companies. It's not an accident or a coincidence that most content management systems work on the framework-with-plugins model. Dedicated software developers build the framework, and it's expected that organizations who use it only have the technical chops to deal with plugins. TPM's architectural change is also a change in the amount of development work they plan to do - they're saying that they can afford to rewrite/develop/debug/etc. 10% or 20% (percentages are arbitrary) of a CMS-size framework and string those components together, rather than work with the 2% of a plugin and sprinkle it on top of the main 98%. They've moved up the food chain in the size of their internal development.
Submit the source article and I will vote for it.
Mozilla Launches BrowserID, a Decentralized Alternative to Facebook Connect
I had an app with over 2 million monthly users. One day I got an email saying that one of the ad networks I was using had violated their ToS and I needed to replace them. The email said I had 3 days to do this. The cautious person I am, I turned off the ad network within 10 minutes of the email being sent.

Five minutes after I turned off the ad network, Facebook shut down my app. Users trying to visit my app saw a Facebook 404. Facebook refused to give an ETA for bringing my app back up. When it finally came back up 4 days later, its traffic was utterly crippled. Facebook never apologized or admitted any wrongdoing. They have NO respect for developers on their platform. Their platform is unstable, and if their comments at Velocity Conf 2011 are to be believed, they are proud of this fact ("we move fast and aren't afraid to break things").
Ooops that wasn't suppose to show. Thanks.
Laff! The golden age of the engineer is only beginning.

One word - graphene.
The article and the comments here make some good points but my question is whether rote memorization of facts is beneficial in other ways, e.g. it may strengthen critical thinking unrelated to the memorized facts. It's intuitive to think that remembering a list of countries, their GDPs and mortality rates would help you understand the correlation functions between those variables but it may also help your brain to form similar but not identical groupings and associations.

I seem to remember reading that some educators are reemphasizing rote memorization because they found other beneficial side effects. Unfortunately, I didn't memorize it enough to make my point here, hmmm, time to Google...
do from YC till fund raising under visa waiver program. Don't get a B-1 because you'll probably get rejected and this raises lots of suspicion whenever you enter USA in the future as you have to declare it.

If more than 2 co-founders and you all have degrees, get H1Bs.

If less than 3 co-founders or no degrees, crush it some more and get O-1.

If you have not raised significant (eg: $1M+) capital by demo day you will not be able to get a visa, go back home, iterate, come back under VWP when you can raise capital, then get visa. It is a tremendous stress.
Alas, email address has become the online analog to the venerable SSN.
SortPrice Adds Flash Sales to Facebook Stores
"Drupal, Wordpress and Joomla use PHP. — the plugin model aches at scale: popular plugins become abandoned plugins, energies move elsewhere. Plugin A works great, plugin B too. However, they weren’t designed to know about each other, thus leading you down a rabbit hole of forking and mending. A few years of use later, you are left with an unmaintainable tangle of ad hoc code written by an all-but-unknown cast of programmers."

This is true of Joomla, and to some extent Wordpress, but as someone who makes his living using Drupal, this statement is patently false and indicates that the author isn't truly familiar with the systems he's criticizing.

The cast of characters behind most Drupal plugins (modules, in Drupal parlance) is well known and most have been iterating their plugins for four to six years (or more). Drupal.org serves as the sole repository for plugins, providing usages statistics, notifying users of upgrades and patches to modules, serving issue queues, and generally keeping the Drupalverse running quite smoothly.

Drupal plugin A and Drupal plugin B are designed to know about each other, at least indirectly, because they use the same fundamental elements (the menu system, the hook system, common APIs) to manage data.

I'm not going to claim that Drupal is "Wordpress easy" to install, or that you'll just sit down in a day and master the system as it's as much a RAD framework as it is a CMS. It's big, powerful, and flexible, and these traits are the natural enemies of "easy."

FWIW, I'm not a core contributor or anything like that, I'm just a guy who's made a hell of a nice living using Drupal.
Blog engines are a subset of CMSs. They're supposed to be restrictive - that simplicity is part of their value. If they wanted a CMS that would allow them to add their own types of content, they should have gone with a CMS that was more "framework" than "application"
Rails 3.1 HackFest
Wasn't one of the benefits that you don't need to rely on a third party service?
"Sure, every website can implement this flow, and users could could go to every website they've ever logged into and update their email address... assuming it all works properly even though they might not have access to the old email address anymore."

And how is this different than the current situation? Nearly all web sites require an email address. With BrowserID, you at some point confirmed ownership of that email address, so you could continue to use it to login, then change when you're ready.

"At the very best this technology offers considerably less value to websites and more hassle to users than Facebook or Google. And it's about 5 years too late."

Tell that to users who a) don't have Facebook accounts or b) don't want to use Google or Facebook with their identity. Far more people have email addresses than Facebook or Google accounts.
Thanks for catching this. We're on it. How do you find the tool working?
And then you get phished for your one password.
The last three examples, Zynga, Groupon and Facebook all have instances where users are rewarded or incentivized to share more.
Ignifero described what happens when your browser or email provider don't support BrowserID.

When your browser and email provider both support BrowserID:

1. You log into e.g. gmail.

2. Your browser generates a keypair and sends the public key to gmail.

3. Gmail signs your public key and sends your browser a certificate saying "this key is owned by whoever@gmail.com".

4. You click "sign in" on some site (e.g. Hacker News) that uses BrowserID.

5. Your browser sends Hacker News an message saying "my user is whoever@gmail.com", that is signed with the private key generated in step 2.

6. Hacker News looks at the "gmail.com", grabs gmail's public key (the one that signed your public key in step 3) and verifies the signatures.

Hacker News now knows that you control whoever@gmail.com.

The process is described fairly well (diagrams and everything) at http://lloyd.io/how-browserid-works
my posts were public
Some interesting new papers in cybernetic theory
By exercising, I meant exercising regularly. In my understanding, you don't make new glycogen unless your glycogen stores are down. And the body can only store about 3 pounds of glycogen from what I've read.

So what I'm saying is if you're mostly sedentary, eating a high-carb diet, your blood sugar levels will rise to the point that insulin is secreted. And then some of that blood sugar will be converted to fat, and its energy will be 'lost' - it won't be used unless blood sugar levels go down again and glucagon is released. But many people eat way too much and too often for this to happen, and they just keep on packing on the pounds. Thus, carbs causing weight gain while fat gets the blame.

I mean, think about it. All the sugar that comes into your bloodstream from, say, two bowls of cereal in the morning. You have about 3 cups of milk, 3 cups of grains. This is a pretty big amount of carbs that gets digested very quickly. Then you drive to work and sit on your bum for 4 hours. Don't you think some of that carbohydrate energy could be converted to fat before your next meal?
Your point number 5 is interesting because it's been backed up with that link. It shows that Spotify is at the bottom of the list but really you're comparing apples and oranges. iTunes sales are a one off amount but Spotify is a revenue stream.

I imagine that I would listen to some of my favourite tracks 1000 times over the next 10 years. That adds up to pretty much the same amount of money going to the Artist. That seems reasonable.

Anyhoo here are some invite codes:
e32yEp9pMNkVxUhy
cnYq9kG9uPmhwHEM
dBFVbcKeDcm9qw25
bdJTRS492mXnyzSY
a94W7mdcVTnGNugk
bGrMgcbLVL8LtZdM
e7RXhPe3yVWGHHDd
e7DUsN99VJP94YKT
bACewd924c2KLA4X
I saw this video back when it was first uploaded, very interesting video and well done
OTOH, facebook id != identity, neither is twitter username. There will always be some id that you won't be able to change. But you are right that email is a bad choice, and i was surprised they give away the email address to developers. They should provide the browserid.org ID only.
I'm guessing this was a case of big company doesn't really want to sue a 16-year-old entrepreneur, they just want him to cease all operations. Sure, he could have changed his company name and sold another product, but that product couldn't have been the USB drive given the rather prominent branding on them.
Funnily enough, all users on G+ could be considered 30 day actives and probably most of them 7 day actives by virtue of the fact that the service is so young :)
As opposed to the alternative (data stored locally on servers at the clinic)? I think the amount of buck-passing in that situation is actually a bigger problem. It's easy for the blame to be passed around from the vendor to the local IT staff, to the users, etc.
Its hard to say. There are quite a few ways in which this could play out.

Firstly, there are two important points to consider. Currently, BigCouch is more or less a superset of Apache CouchDB. The only patches we have to CouchDB sources can and should be back-ported but require that we solve a couple possibilities for bugs in non-clustered deployments. Secondly, Erlang is a language which allows for an easy mish-mashing of code so that once we have back-ported these patches there's no real requirement for a merge at all.

There are also a few things that we're discussing in the CouchDB community that could very well contribute to not needing to merge the projects. Specifically rearranging our source tree to be more prototypically Erlang as well as some tools like a couch-config script that could allow plugin-type extensions to CouchDB.

In the end, its hard to tell how things will shape up. It could be a full on back-port, or it could just be a general improvement to CouchDB's source tree and build system so that BigCouch is strictly "CouchDB + Other Erlang Apps" if that makes sense. And with my CouchDB committer hat on, it really depends on what the community wants. Its easy to fall into think of the trap of "it's obvious" but we also have to consider that others are taking CouchDB and porting it to mobile phones. What we end up with in "core" CouchDB has to consider a lot of use cases.
I believe you will definately rely on one (of many possible) 3rd parties.
This is roughly what Ars Technica was doing before I left, I think moreso now. The Movable Type "post" interface was relegated to "the box people write text in", which was then pushed into the app that handled rendering a site.
I think hangout use statistics would be really interesting. anybody got any idea/estimate about those ?
Various forums already verify you own a certain email account when you sign up. Basically everyone does to send your account information or their marketing stuff. This isn't new.