skysight-inc/HackerNews huggingface dataset:
Can you expand on what information is required to use this feature? I assume you can create a new account with little to no information (or fake information) and use it.
In front of the kids, I will support anything my wife says over the kids. Period. That is necessary to avoid having kids try to play one parent against the other. (Any attempt to actually play us against each other ends badly for the kids.)

When my kids are teenagers, perhaps my feelings will shift.

But right now my kids come first in my emotional life. I would die for them. I have compromised work for them. It wasn't even a question. I support my wife, but not as unconditionally as I support my children.

This does not mean that I do everything they want. This does not mean that I try to be their lives. I want them happy and healthy, and I do everything that I think is good for them. This is not the same as being their friends. Nor should it be.
As hgimenez said, the best way is to not store your secrets in your source tree at all (12factor.net style). Keep them in the environment. Here's a great example:

https://github.com/democrats/voter-registration/commit/2fa87...
Only a fool would have loyalty to an institution (business) that has no loyalty to him.
Went looking for it and found a copy on the Internet Archive: http://archive.org/details/BooksOfArslanhowToWinFriendsAndIn...
3 Reasons to Choose Angularjs
that would couple session to db. Play Framework, for example, is able to provide support for sessions using encrypted cookies, without having to provide adapters to all sorts of potential databases.
Rumor: Windows Blue to Maintain Metro User Interface
I have several domains with them and have never had a problem. I had to contact their customer support about a .IO domain and they were really helpful.
In case anyone wants to see the rather unremarkable photo that this whole thing is over, see:

http://jezebel.com/5971234/randi-zuckerberg-accidentally-sha...
How did she get it wrong? The photo wasn't posted publicly. Somebody she shared it with took it and posted it publicly on a different social network.
http://www.zdnet.com/blog/facebook/epic-facebook-timeline-ch...

http://us.gizmodo.com/5921085/facebook-just-changed-your-ema...
Very strange and arbitrary selection of cities for Europe, it seems. How were the 29 selected? What often happens for these kind of lists is people assume those reviewed are somehow better than those left out. Hope this will clarified once the report gets published, that many top location were just left out.
Right. She should have seen an icon that showed "friends" rather than public. I think the "share" button remains and (if I'm not mistaken) only people within the original permission will be shown your "share" in their feed. This could, however, give the impression that you could just pop the photo into Twitter, however. There is "download" right in that "options" menu.

There's also the ol' right-click/save.
O Maior Edifício Modular do Mundo
It was showing up for Callie, who was not friends with Randi. I think most people would assume that means it's public, when it fact it's just an example of the fact that privacy on Facebook is really confusing.
i have some questions.
how do i contact you?
When I first saw the story I was sure it was going to be about how easy it is to save and broadcast a photo from the Poke App.
Yes, building your approach around chaos monkeys (https://github.com/Netflix/SimianArmy) has some real advantages.
It's cool to hate MongoDB

When a product is pushed as essentially a silver-bullet -- often by people who have never and will never actually build anything with it -- it is naturally going to get a lot of backlash by people who see through the problems, and moreso by those who buy the hype and then smash into the reality halfway through their projects.

I speak from personal experience on the first point, while the second has come from countless real-world case studies. A couple of years back I had several widely distributed pieces declared "trolls" because I essentially called for a sobering reset on the NoSQL hype train. Every single thing I said has been well proven out since, so there's that.
How about not paying Nick Denton for it?

http://i.imgur.com/en5PP.jpg
It's not "just a fact." It's an (as of yet) unsupported assertion. Liberal is an inclination, not a party. There is no platform. Unless you're talking about a party that calls itself Liberal, which would mean you need to be clearer when making sweeping generalizations.

I am a liberal-minded person. I don't want taxes any more than I want gas in my car's tank, but neither can be avoided under the present system. I would consider supporting a way to maintain civilization in a fair and equitable way (rough definition of liberal) that doesn't need taxes, should someone propose such a thing.
If you want to argue base purpose, the base evolutionary purpose of pair bonding (which leads to marriage) is to ensure good child care for ones kids. Evolutionarily, men who participate in serial marriage, having kids with each, are very successful. Even though their relationships are not.

Evolution does not care whether your children are happy and healthy. It cares that you have a bunch of them, and they have children in turn.

I am not very successful evolutionarily. Nor do I strive to be.
It seems that every GutHub downtime I can recall was caused by automated failover.
I dunno. I notice Mark is slumming in the corner. I mean, if you want a remark.
What's wrong with it? It's a bug by design that allows a useless feature (access to private members ... why not make everything public then?) and allows the destruction of a key concept of OOP: encapsulation.

Which is perfectly fine if you don't need encapsulation.
"there is a difference between latency and bandwidth the chart is simply inconsistent".

Both transmission delay and propagation delay are measured in units of time -- I don't understand how it's inconsistent. If you'd like to change the payload size, I've made it very easy to do so -- simply change the html at the bottom of the page and it will be reflected immediately up top.
But why wait, when you can use Postgres now?
What do you mean, "three factor"? The factors are something you have (telephone), something you know (secret or password), and something you are (biometric). Google isn't allowing you to use biometrics like your fingerprint to log into your account; thus, you aren't using three-factor authentication.
No, this is not true. Until C++ can reason carefully about aliasing, it can't be memory-safe. Iterator invalidation and reference invalidation are the key problems here.

Rather than repeat the code examples in detail, I'll link to some earlier examples I've shown:

http://news.ycombinator.com/item?id=4724781

http://news.ycombinator.com/item?id=4724421

Basically, they come down to references and iterators not knowing about aliasing, thus being unable to determine when the referent is destroyed.
Right. For brands it encourages them to see those numbers. If it doesn't, it encourages them to sponsor stories. For users it's more likely to have them taking a look at their privacy settings and locking stuff down.
There is an icon attached to every post that indicates its privacy setting. That icon is in fact in the same row of actions as the "share" link.
Facebook ruins Zuckerberg Xmas
I understand where you're coming from but no user should have to move country to get improved internet services. The internet is global and the services on it should be also. Did you think about staying in the UK and trying to address problems like this yourself (you would actually be better positioned to do so there)? [serious question]
Yes, they are insecure. One of my pet hates is when they go on about how I'm a "genius" or a "miracle worker" when mostly I do basic stuff they could do themselves. It's both an excuse for them not to do it, and a way to flatter me into doing it for them. Except I don't flatter that well, and I'm not really tech support in the first place.

I keep reminding myself that these are otherwise highly intelligent people who have insecurities about technology. Part of the "pushing back" is about encouraging them to do it themselves.

A trick I learned from a one-time co-worker was to listen attentively and repeat the words "I understand" and "yes, I understand" until they calm down and I can say something more meaningful. Keep reassuring them you're listening and their problem is valid. Works like a charm.
I'm not sure what you're getting at with rvalue references and move semantics. They are quite unsafe. The language does nothing to prevent you from using a moved value after you've moved it.

Also, circular references are not a problem in managed languages the same way they are in C++. Managed languages automatically clean up cycles. C++ requires careful use of weak pointers to deal with cycles.
I have this same sentiment, but I use C++ just because templates, classes, smart pointers, lambdas, and namespaces are such huge productivity gains.
True, but why bake it into the language if it's not enforced? Most OOP requires encapsulation which requires private members and the ability to enforce this privacy. It should not be up to the user to enforce it, as that will never happen.
Human decency also includes not making it easy to publicize private photos.
You seem to be confusing title with competence?

If I hire a dozen of my high school friends to run a multi-million dollar company, it doesn't mean anybody knows what they're doing.
You could try that with tourists asking for directions, too.
It's termed as free because most people only care about the financial side of payment. If people can get a service like this for no charge I bet most couldn't care what information they are giving Google.
It interesting to see a completely different background to mine. If I have one criticism of this list it's that it is very mono-cultural -- all OOP, nothing FP here, for example.

My background is K&R, Code Complete, SICP and related books in the Scheme canon (HtDP, PLAI), and lots and lots of papers and blog posts. Having absorbed the fundamentals I find online material both more accessible and up to date.
Most of those applications were written decades ago.
Yeah she was not friends with Randi but apparently friends with one of Randi's friends. Agreed -- it is very confusing. G+ gives you a nice big warning before resharing something within G+. But of course we know that this was shared in a completely different social network (twitter), Callie obviously saved the pic and then reuploaded to twitpic (automatically or manually). Which imho isn't very classy no matter the original privacy settings.
N.Y. Website Posts Map Of People With Gun Permits
Common geek UI philosophy: "There's a cryptic symbol! What could be clearer?"

(Not to imply the parent thinks this way. Just that this seems to be yet another example of important information obscured by too-clever UI.)
The client is always wrong
Interesting -- good to know!
If you're designing a system that will be displaying things in a monospace font, making it automatically add additional spacing may be reasonable but that is itself an application of the rule! If you're using an existing system (or, say, laying out a poster in a monospace font), then the notion that "you should ignore the rule because to do otherwise would be confusing content with presentation" is a confusion of another kind.

One place I'm a bit torn is comments in code, but I think I come down on the side that says "my editor shouldn't be trying to guess which comments are simply paragraphs of text and which may have things I'm trying to line up - monospace should work like monospace" and in this case you should be adding two spaces for clarity.
This may sound selfish, but github does such a great job of writing up post mortems, that I almost look forward to their outages just because I know I'm going to learn a lot when they write their follow up.
How can you prove that you aren't selling this information? It certainly would be the most profitable thing to do, so from the customer's perspective, you certainly have an incentive to betray my trust.
I polled my 500Startups network to see which countries they were interested in and had contacts in, then narrowed down the list to a manageable size.

Which cities did you think I missed?
How about the content of the phone calls?
Then that's obviously a problem with the people touting MongoDB. It's not an inherent fault in the actual software itself...
Email sent to you. Narf!
CUDA implementation of HyperLogLog's for cardinality estimation
I wonder how much downtime they've avoided through automated failover.
Sure, the first stage is easy from an energy perspective, so SpaceshipOne is a good model for that. From what I understand they intend to try to use the same idea for reentry from orbit, though, and I think they'll end up with something expensive and dangerous as a result.

The space shuttle was a disaster from a cost perspective. I don't know how many lessons we can draw from the program beyond "don't do it this way".
It's about time we heard from them. I understand the timing of this was unfortunate (right before a holiday), but the trust alluded to in the conclusion of that post would be bolstered by faster post-mortems on major outages like this one.
I've made a transcription of the famous 'MongoDB is web scale' video, a humorous conversation between a NoSQL fanboy and a more cautious, conventional database developer:

"'And in conclusion, we have found MySQL to be an excellent database for our website. Any questions?'

Yes, I have a question. Why didn't you use MongoDB? MongoDB is a web scale database, and doesn't use SQL or JOINs, so it's high-performance.
...."

Read the entire conversation at http://www.mongodb-is-web-scale.com/
however there's no reason to believe 'qualia' aren't explainable. for example, if "consciousness" is a thing, it may be some kind of system or structural artifact induced by the underlying neurology

qualia then would be properly described by their manifestation in that induced system

that doesn't mean that the descriptions of these sorts of things would resemble anything we refer to as "mathematics" or "engineering" or even "science" today. for example, there's no reason to expect that these things are "computable" or decomposable in any sense
There's an old saying, "If all you have is a hammer, everything else looks like a nail." People hate MongoDB because its makers (and, to a lesser extent, userbase) actively market it as the hammer.
I wonder if the ease of use of MongoDB might be part of why this "hating on mongo" trend exists -- it's very easy to setup and use without having to think through exactly what the best way to use it is. Which means it's very easy to do something dumb without realizing you're doing something dumb. The problem is, most of these database anti-patterns aren't visible at a small-scale, they only become obvious once the datasets get large and then it's really hard to change things.

Pretty much any database is going to leak abstractions at some point, there's absolutely no way of getting around understanding how your DB works. I think the problem with Mongo is that it's so developer friendly initially, that it makes it easy to avoid a lot of hard decisions that will eventually have to be made, and when those decisions do come to the forefront, it's often at a much less convenient juncture in the application's lifecycle to change things.
I bet most people don't have a full understanding of what information they end up giving google by using google services like gmail, voice, even "just" search. I bet google likes it that way.
Yes. But your marketing people should know how your software performs from a user perspective. I mean... I don't know how incompetent your marketing people are, but mine actually take the time to learn what they're promoting and get yelled at if we find out they lied.

Maybe you need better marketing people?
There's more discussion and a few links on previous HN submissions:

http://news.ycombinator.com/item?id=4016421

http://news.ycombinator.com/item?id=159213
When engaged in war a country does not need explicit martial law as it is under no law at all.
Quality is always compromised when you set your sights on appealing to everyone. Most websites do that because they would rather make a lot of money than have the integrity that comes from higher standards and focus.

The irony is they cheat themselves out of their own success because they're too busy trying to pander.
It's part of our terms of service now that we can't sell the information, I'm not sure what else we can do to prove that other than continue not doing it.
All inline comments should come with a space after the #.
All dictionary literals should have no spaces immediately within { and }.
All multi-line dictionaries should be aligned one character after the opening parenthesis.
There exists a line with "for key, value in dict.items.():", which is invalid.
Use of one-liner "for" statements is discouraged.
"if not a in b" is a more easily translatable statement than "if a not in b".
Not to mention a level of success that enables them to ascribe it to hard work.
I can only imagine the outcry that will occur when Facebook blocks right click, save image.
Yes, this is the by far the most common answer. However, one would need to remember to bring said special cable, which at that point why don't you just remember to bring the wall wort USB adapter instead of carrying around a charge only cable?

Side benefit: wall wort USB adapters can push more amps to your device (e.g.. faster charge) than USB hosts.
If I want to prevent you from accessing your account for at least 24 hours, couldn't I just try to log in as you and intentionally enter an incorrect PIN thrice?

Am I misunderstanding something?
I'm not saying that I would not use Postgres now.
Actually, I've been running a website on MongoDB for over a year now. I don't remember the reason behind it but it haven't caused any problems so far. The web server handles more than a million page views per day and all data is stored on MongoDB. I'm not perfectly happy with it but it does what it's supposed to. With some gimmicks here and there.
If I started from scratch today, I'd probably go with PostgreSQL. Not because MongoDB is "bad" but because it's data model itself causes some problems. For example, if you query some range on an index with upper and lower bounds (like age > 18 && age < 50) it can not use both bounds on the index. That's been driving me crazy on some queries and I had to use hacky indexes. It's not a bug though, it's the query syntax and data model causing these kind of behaviour. There have been similar examples during this last year but not something that would cause "hate" agains it.
On the plus side, it makes prototyping stuff so pleasantly easy that you can not have that on PostgreSQL.
I am not trying to be hash. But again? How many more github downtime posts do I have to read on HN every month?
I don't think it's a question of better or more exclusive learning opportunities. I think the op is arguing that you can gain the same skills and experience you would get starting a company at 20 by trial-and-error, but without the lost income, time, and career progress.
Design Tips Every Developer Should Know
Absolutely and unequivocally true! And the truth is that the actual makers have always been quite reasonable in their claims. But from an industry perspective it is hard to separate the two, much like Visual Basic got most of its bad rap from the people who used Visual Basic than from the platform itself.
It would be nice if we could expect people to always do the right thing (even in the face of confusion over what that is due to poor UX), but ultimately you have to deal with the reality that humans are flawed and the more humans you add to the mix, the more likely one bad (or confused) apple will do the wrong thing.

If your platform exists to form links between these (billions of) people, you have to either be extremely proactive with user's privacy (which Facebook clearly isn't), or you have to educate them to accept that anything they post should be treated as if it were public to the world, because basically it is (via 6 degrees of separation combined with Facebook sharing rules).
I think it's more that they felt obligated to register it to protect their trademark than them actually wanting to use it.
To be fair, most people already do this anyways by using passwords multiple times.

At least they have no illusion of security. The scheme you showed provides lots of illusion, and zero security.

This matters because, for the same effort, users can get much stronger security, even a cryptographic guarantee of password independence. (Leaked site passwords yield zero information about other site passwords, even if they're derived from the same root). But they will not seek out these solutions if they are mislead into using broken schemes instead.

There are also two memory banks in a yubikey so you can set two different keys and alternate them using the schema I put forth above.

That's still terrible.
No, she (understandably) didn't know Callie was friends with her sister.
Great library, great people. Highly recommend it. ogrisel helped me a lot while I was just messing around and I'm forever indebted to him for the amount of 1-on-1 help he decided to dish out.
Pretty spiffy. Good luck with your product!
I will bet cold hard cash that they don't portray themselves to outsiders as ignorant as you say they are. That is, their reputation depends on what you say not being apparent.
Yuh, I have the same question too :-). Hard to do cost/benefit analysis when you only see the costs.
GitHub will already generate a .gitignore file when you create a repository on its website. It would be nice if the .gitignore file was based on the type of project being created.

Right, but how does it know that? There is no "Create Ruby on Rails project" command in git. How will it know what to include? Will it have to scan and somehow detect that it's an RoR project? And check the version of it?

Much simpler to leave this stuff to a RoR-specific tool. Maybe the .gitignore should be a default file when creating an RoR project.
I have seen posts where the "share" button was not available. Is there a separate setting for that?
The sad fact of this is that while Randi managed to figure out how the mishap happened, there are a billion other users who might not.

Yes, posting anything online should be assumed to be in the public domain. But that doesn't mean we should have to put up with the poor UX of unclear expectations and no visibility of what is going on.
MySQL cluster is another option beyond MySQL Galera (and Cluster actually has a NoSQL layer on top of it.. FYI)... but I have to say if we want to talk about scaling issues for MongoDB, you might not be happy with some of the limitations of NDB.
Still, someone will eventually call this a feature, because it might force you to dry your hands before turning the knob - keeping it cleaner/dry.

Designers will always find a way to justify their crap.
Actually, I think that would be a business opportunity for a startup, only I can't figure out the tech you'd need to do it. There are shops (like, for wedding dresses) that disallow you from taking pictures of their stuff because you might share it online; they'd make good customers.
This also makes it sound like whoever intervened to rewrite said feature in sharded mysql had an easy time. Usually this would not be an obvious port. However we don't know the technical nature of the feature or specifically why it failed.