skysight-inc/HackerNews huggingface dataset:
Great questions. Now I'm having to think about implementation more.

Here's the basics of a system:

/domains/
/domains/google.com.space

Let's say the key requirements are:

1.) Domain pattern + ip address
2.) Some expiration timestamp
3.) Some property that tells you who told you that domain matched that IP

The contents of file "google.com.space" then could be something like this:

ip4 123.123.123.123
expiresEvery 3600seconds
lastUpdated 2/2/2013 4:00pm
receivedFrom dns.verizon.com

For subdomains, you could do a "/domains/foobar.google.com.space" file, or maybe a "/domains/*.google.com.space" file, or maybe you just put them in the file above like so:

ip4 123.123.123.123
expiresEvery 3600seconds
lastUpdated 2/2/2013 4:00pm
receivedFrom dns.verizon.com
subdomains
mail.google.com
ip4 123.123.123.123
ttl 3600

Et cetera. The implementation details would be very important. There are plenty of sub decisions to make to come up with a great DSL. But I'm fundamentally confident that at the root level, the decision to create a Space based, object oriented domain system is not only correct, it is inevitable. It just feels right to me. Again, I've had the benefit of working with this structure for a while now, and am amazed at how so many things simplify down to it. Space is object oriented programming in an extremely simple, concise, robust, human readable way. Just as most (if not all) major computer programs nowadays are written in an object oriented way, I am predicting there will come a time when most major message passing systems are written in a Space encoded way.

> That makes it trivial to e.g. modify zones files in shell scripts with tools like "awk" etc.

I look at awk and I think that's something that will at some point be buried, and should be. awk is kind of like a neanderthal or some other species in between ape and human. Served it's purpose, helped the evolutionary chain, is a very honorable tool, but at some point will go extinct.
But wait! Shouldn't file system subroutine check if it actually written what was asked thus marking operation as completed successfully.

Why do we have bloody exceptions if we need to double check every action taken?
My entire Computer Science education summarized. Blind faith. Every test, every question, every function, every call. Blind faith.
Noses and hands also spread infections, I don't want my doctor to have them either.
nice, thanks for sharing.

I was actually contrasting it to ack in my speed claims. I don't expect that it'd be that much faster than GNU grep in most situations.
Good points - thanks.

Although having looked at hopper, I must say I'm not convinced it seems any more native than a Qt app on OS X could look if work was concentrated with this goal in mind. So as I said in my VirtualBox comment, I think that while indeed it is a Qt deficiency that apps don't look native straight from the compiler, more work could be done by the developer to make it more native-like.

I've seen controls acting weirdly but only QPushButtons - that seems to be regarding the hit-test area - we've had to sub-class a lot of them on OS X to fix this by making the hit test area bigger which is annoying. There's also a pretty bad spacing/padding/layout issue as I alluded to in another comment.

I agree with the event stuff as well - definitely one of the biggest things which affects us is that sometimes mouse/keyboard events don't get sent to the app if the app isn't active or the mouse isn't over a particular window. Debugging through Qt, it seems that Qt never gets the event from the OS, so we have to install event filters for all windows and intercept them which is crap. We've also seen weird stuff like key release events being received before key down events - again debugging through Qt, it looks like an OS X issue in that that's the order they come in from the OS, but again, without a native version to compare to, it's difficult to tell or test.

Generally the crashing of our apps is due to graphics drivers or memory allocation issues (we deal with huge amounts of memory), and I'm not aware of Qt itself being the result of any crashes on OS X for our apps any more than other platforms, but I guess without a native version to compare to, it's difficult to say - but Qt is very rarely the cause of crashes in my experience and I generally develop for Linux and OS X.
For all we know, their protons would decay, so they would not be anymore.
Deploy your websites with BitTorrent Sync
This might be a good time to remind folks of Markham's Rule of Technical Debt: The economic cost of making your code better can never exceed the economic value of the code to begin with.

Write a function that saves to disk but never checks if it fails? Who cares? If you never use it again, or it never does anything of value to anybody, it's not worth anything.

Craftsmanship is a great thing, but it always exists inside a larger economic context. The guy laying tile in your kitchen doesn't give the same attention to detail as the artisans completing the Sistine Chapel. And this is a good thing! He might not have much education, he buys pre-assembled pieces, and he's liable to just slop it in there. This is appropriate because your bathroom's economic value is miniscule compared to a great cathedral. Likewise, if you're in a startup writing code, you've only got a 1-in-10 chance or so of your code ever having any value at all beyond just playing around. Completely different picture if you're being funded by BigCorp to write version 8 of the Bells-And-Whistles App. Yet some of us insist on treating all this coding the same.

So I am a bit annoyed at the use of the word "faith" in this context. If "faith" is calling functions and expecting them to either execute or terminate the program, CS is replete with faith-based-coding. This entry describes the situation too much in loaded terms.
Exactly. Often it is not the innovators that end up benefiting from showing everyone the value of a new idea (1). Most innovative work is very long term and there are simply not many channels to fund such work. Innovation is often too far up the pipeline for the originators to reliably extract value. As you point out, the original innovators of the internet and desktop computing are not the ones that ended up with the bulk of the rewards.

Douglas Engelbart and his team innovated, originated and practically invented all of modern computing paradigms and interactions. Engelbert died unable to garner interest in his grander vision of accelerative bootstrapping. I suspect he saw modern incarnations as bizarro implementations, outwardly similar imitations apart in spirit. Those like Bret Victor recognize that spirit. This list shows some of that spirit. I would argue RapGenius qualifies too. Here's hoping this picks up as a trend.

Google and Apple both innovates like crazy

I would dispute that Google and Apple innovate like crazy. They do more polishing and acquiring, with most of the innovative work in service of the product, a benefit but not a new paradigm. Voice recognition, self driving cars, heads up displays, multi-touch,internet blimps. For the dozens of researchers who devoted decades of their lives to this work, the recognition Google and Apple get for things on like that list is bittersweet.

This is not to dispute the tremendous innovative thinking and work it takes to package research to a public ready state, I am merely pointing out that true bellwether innovations (2) often go disproportionately unrewarded.

(1) With a negative income tax and library->hackerspaces, that would very often be perfectly ok. Such people are moved more by vision than by monetary rewards.

(2) Which will themselves be combinations of existing things, the key is they should be the first to inspire with this combination, even if in very rough form. By this definition pagerank and the iphone are the key innovations of Google and Apple.
It goes very deep in meta territory, but hey, it's not as if there were any fact intersting to discuss.

I remember a lot of discussions a year or two ago when marco was very vocal about the reasons he didn't have comments on his blog, and would prefer to have all of these on HN for e.g.

slowdown's comment goes the other way round, on why HN should care about commenting on marco's blog. There is another thread [1] with 138 comments and more quality opinions and speculations than anyone should need,
Marco's speculations are also represented in the top comments. Agree or not with he's stance, it's a valid point IMO.

I think it's fun to see this kind of reaction on why some contents should be commented or not, and the motivations to push a site or another.

[1] https://news.ycombinator.com/item?id=6071233
Concept of Idea Hub is pretty interesting. For me there is an angle that I haven't really seen explored i.e. a place to collaborate on (develop) high level concepts related to CS and CS applications. Very much alike to what you'have done in some points in your list. E.g. how to apply patterns/concepts from game design to other more traditional fields (your GP examples). I would love to see a place for collaboration centered around this approach--an idea incubator. I see it married to a platform leveraging experimentation around some of those ideas in lean startup style:)
The tools are publicly developed: https://android.googlesource.com/platform/tools/build (there are also two adt repos, one for eclipse, one for idea; gerrit is also public)

Google may develop a lot of things behind closed doors but let's give them credit where credit's due.
Thanks for the list. Not implying anything is cut and dry. Pointing out that in nearly a century, 8 of 11 cases are sourced in this decade. That's the kind of thing that gets historians and political/critical theorists paying attention.
They take it down during WWDC keynotes and other major announcements, yes.

But there are other instances where the store will go down outside of those periods. Sometimes it's for maintenance, but more often than not a new or updated product appears (e.g. a product line gets a speed bump across the board).
I don't quite understand this (or rather why this is a wikipedia page). This is literally "blind faith" as defined by the normal wikipedia page; there is not "Blind Faith (electrical engineering) or "Blind faith (civil engineering)".

Also the recommended alternative does not have to be TDD, that is just one engineering practice. One can develop with tests without it being TDD.
Agreed--it's just a utility.
You need to know m and n, or a number of lines, beforehand for a one pass version, don't you?
*Verizon did not specify why its SIMs were not vulnerable*

I was under the impression that Verizon phones don't use SIM cards because their network is CDMA instead of GSM.
I think most of us have probably deployed fixes without knowing 100% whether it helps, but based on a good hunch from looking at data and code. The reason I keep doing so is because so long as the hunch is good and based on facts, it keeps working.

Tests are good, but there are always those issues those 0.001% issues that will never occur when you are trying to make them happen, but will happen to somebody once code is deployed. I am reminded of an incident a few years back where I could reproduce it with tests occasionally, but it would literally take me weeks of re-running the test 24/7 before I would hit it again. As you can imagine, I applied some "blind faith" (as in article) fixes while waiting for that stuff to run.

PS: By the rules of wikipedia, this article probably shouldn't exist. Nonstandard terms, not notable, original research, blah blah blah.
Request: http://mock.isssues.com/{RESPONSE}/{MESSAGE}
Verizon's LTE phones have a SIM.
I would hope a multi-billion dollar developer portal has a backup somewhere. It'd be insane if they didn't.
If by epic you mean a great way for a twenty-something to travel for free in the guise of raisin money and get some publicity for himself (and G+ to boot), then yes, it is epic.

I'm sure he'll then use the documentary and sure-to-follow book to claim that everyone should do why he did. He's the next Tim Ferris, I'm sure of it.
Their 4G LTE network uses sim cards.
I don't think anyone was, least of all me. In any case, I'll bite:

Different UI toolkits make doing certain things hard, certain things easy, and some things damn near impossible without large effort on the part of the developer.

So when the parent commenter says "Nobody on OS X wants a Qt app", I'd argue that yes, although you can make a "well designed QT app", it's much harder to make a "well designed OS X app" with QT.

Why will it be less likely to be a well designed OS X app? Because it will be different to a Cocoa app made with interface builder, in subtle and sometimes not so subtle ways. Sure you can code around these and make adjustments, but the level of effort and investment to get to the stage of if you'd just built it with a more suited tool for the job (Cocoa / Interface Builder on OS X) is quite high.

This is why there is some truth the the admittedly generalised statement made above that "Nobody on OS X wants a Qt app".
I pass.
Ah, the old "if even <some low number> of people pay for it, we're golden!" thing.

I'm going to go sell rocks at a concert for $1m a pop. The concert is 100,000 people, if even 0.01% pays for them, I'm rich!
Ubuntu Forums hacked, 1.8 million passwords and emails stolen
Sorry, I'm not a crypto guy. It seems that he sends an "Over The Air" SMS that has an incorrect signature and then always recieves a response that he already knows.

EDIT: Ok, I just read your other comment and must say that you probably understand a million times more about this than me, so disregard this comment.
I think PG puts the definition of a "hacker" in the best way I have ever read

To the popular press, "hacker" means someone who breaks
into computers. Among programmers it means a good
programmer. But the two meanings are connected. To
programmers, "hacker" connotes mastery in the most
literal sense: someone who can make a computer do what
he wants—whether the computer wants to or not.

http://www.paulgraham.com/gba.html
Google+ getting beat by LinkedIn for social sharing
Sorry, I might not be old, but I do like my professionals to be professionally dressed, I consider professional to involve being smart and smart generally involves wearing a shirt. You might think I am wrong, but in equal measure I too think you are wrong.
The Dance
That wouldn't help. Without wanting to go too deep into OT-territory:

Even if the DPI could be known (and afaik normally it isn't, it is just set to a value) and it would be possible to convert in into real inches (btw, I have no idea how big that is in real units) to be displayed on a monitor, how would a designer know how big any element, even text, should be? It depends on the available space, which depends on the size of the monitor/the size of the window.

To think about how absurd that would be, try to find a situation where someone would say "this heading should be 2 cm tall".

px as size lead to the same problem with the available space, but they at least correspond to the resolution.
I really hope no one is going to try to force me to carry a phone around all the time (I only have one with me when I'm expecting a call or planning to call someone myself). Those yubi keys look interesting, but it's still an extra piece of hardware that has to be bought and carried around (and not lost).
i was complimenting you.. ahh nevermind
Hurray for Java applets.

But seriously, there is a sunny side to this story: a user could load her own programs onto her SIM. She could gretaly extend the functionality of her phone... with programs that she trusts. Maybe even ones she wrote herself.

Imagine... an open platform. Oh gosh, that would be terrible, wouldn't it?

Otherwise this story highlights the concept of "minimum viable product" not in the startup world, but as it exists among major industry manufacturers. For example, if SIM manufacturers can get away with using DES, then why invest their time and money in using stronger crypto? There are so many examples of this type of thinking... it's certainly not limited to imlementations of cryptography or SIM cards. No doubt, some would say this is simply Business 101... ask any used car salesman. But it's particularly acute in hardware and software.

Do hardware and software worlds makers need higher standards and more serious "quality control"? Beyond the cosmetic appearance of their work, no. Because users are generally indifferent to all else. What they don't know won't hurt them.

Did you know you can type encrypted messages directly with a text editor called ed(1)? How cool is that? It's so easy. Who needs PGP?

It uses DES, but hey, DES is good enough for SIM cards, so...
Oh, sorry, I wasn't sniping at your comment!
I started to agree with you, but only because my brain initially parsed your statement as, "you no longer have the right to write an article about what a hacker is". I would take anything ESR writes about hackers or "hacker culture" (whatever that is) with a grain of salt the size of my clearly-unreliable head.

There's a lot of interesting tidbits and trivia and observations in ESR's hacker dictionary and other writings, but it became really clear to me about 10 years ago that ESR has this reductive wish-fulfillment streak that pretty much invalidates his entire worldview. ESR really, really wants to believe that a hacker is something more than a really talented programmer. He really really wants to believe that hackers have a shared, unified culture that goes back to the dawn of computing, and that this culture agrees on pretty much everything that really matters to him, and that this culture is ultimately the only group that matters where philosophical issues surrounding computing are concerned.

If it wasn't obvious enough, he uses terms like "our tribe" to refer to the culture, and "the elders of our tribe" to refer to the supposed universally-agreed-upon elite of this imaginary meritocracy. Most importantly (and this is where the wish fulfillment part comes in), he really wants to believe that he is one of those elders. For all of his strengths (and he has many- he clearly has a really active intellect), he comes across to me as a really insecure yet conceited and arrogant guy (insecurity and arrogance frequently go together in my experience). He ultimately just wants to believe that there is some vast and old meritocratic subculture of intellectual elites, and that he is at or near the top of that meritocracy.

All you have to do is read through his version of the hacker's dictionary for any entries that attempt to define what a hacker is or what a hacker believes, as opposed to the entries that just document trivia, history, and slang. It's like reading Heinlein- every time he tries to define what an ideal hacker is like, he's obviously describing himself. This goes all the way down to political beliefs. At one time, there was a controversial entry that stated that most or all hackers were libertarians. Guess what ESR was? At some point in the 2000s, he changed it to read that most or all hackers were neoconservatives. This coincided with his own self-identification as a neoconservative. I don't know what it says now, I can't bring myself to look at it.

The "surprised by wealth" essay was what initially soured me on the guy. He was (briefly) very wealthy after VA Linux's IPO in 1999, and he felt compelled to write a big long essay about how rich he was and how it validated everything he'd been saying (http://news.slashdot.org/story/99/12/10/0821224/esr-writes-o...). This was followed by all sorts of lovely things, like his Bill Gates-as-Hitler artwork that I think is still on his site somewhere, and many many many blowhard outbursts and incidents over the years.

EDIT: typos and a clarification
So, vitamins are actually bad for you and there's really no such thing as a 'crack baby'.

It's a bad week for things I learned growing up in the 80s/90s ...
I remember. I was there :)

tangent: should downvotes be based on "how dare you?" sentiments?
Sadly the http codes were never designed for API calls in the first place, but are the recommended, and accepted way of expressing errors in APIs. The choice is to use woefully vague codes, or move out into other standards such as Webdav. Or of course custom codes.
Actually, I was not even raising money. I just had coffee with one of them without knowing they were investors.
I haven't talked to any investors other than that. Just been focusing on building the startup. I will take on your offer for later though. My email is jerry-at-contentdj-dot-com. What's a good way to reach you?
You're right.

I managed to mess up some entries of the database, thats why you see some ungodly stuff like 11b email validation. I'll patch it up.
I don't understand the article's description of the sandbox vulnerability. On the iPhone app sandboxing is done by iOS, not in the SIM. Does the reporter just not understand, or is there another layer I'm not aware of?
I thought this is what trampolines are:

http://en.wikipedia.org/wiki/Trampoline_(computing)

http://gcc.gnu.org/onlinedocs/gcc/Nested-Functions.html

FFcall can be used to do simillar things:
http://www.gnu.org/software/libffcall/

It has four subprojects:

* avcall - build a C argument list incrementally and call a C function on it.

* vacall - C functions called with variable arguments

* trampoline - closures as first-class C functions

* callback - closures with variable arguments as first-class C functions

[update] used outdated link to http://www.haible.de/bruno/packages-ffcall.html
Especially when it translates to greater food availability.

The poor in the US do not suffer from a lack of food availability.

5.1% of poor children don't get enough to eat. For comparison, 5.7% of children above 4 x poverty line don't get enough to eat.

http://mchb.hrsa.gov/chusa11/hstat/hsa/pages/221oo.html

Food availability is a solved problem in the United States. Portraying it as a problem takes resources away from real problems which need to be solved.
Might I ask what vulnerabilities exist for SSI, and why you describe SSI as a "poor way to setup a static large-file caching endpoint"?

I haven't used SSI before, but after researching various technologies, it looks like a solution for my own caching use-case, and I am planning on implementing it. I realize that it's a rather old technology, but as long as there's nothing wrong with it, I think it could work for me.

Is there something wrong with it? The only thing that I have seen is that the "exec" command is dangerous, but NGINX doesn't seem to implement it.
> Remind me where in the Constitution it says ...

There's a lot that the Amendments, including the First, don't say. They are not literal descriptions of what specifically is and what specifically is not allowed. They set the tone for the kind of things that should and should not be allowed.

When you judge a practice, or a law, against the First Amendment, you don't look for that specific practice in the text, you judge how much that practice supports or opposes the amendment.

The amendment does specifically mention the press, in a general way. The press does need information to function, and discouraging access to that information would tend to weaken the amendment. Which is why we're seeing credible discussion today that the NSA's dragnet metadata collection violates not only the Fourth Amendment, but the First, because the collected metadata is data mined for associations, which could tend to discourage and punish (room for discussion) "the right of the people peaceably to assemble."
Honestly, the idea of a facebook subscription is not a new idea, nor is it a feasible idea.
It is something people have discussed on HN about for years now.
Not to mention $10 a month is unrealistic in every developing country where roughly 40% of facebooks users are based (brazil, india, indonesia ...)
Paper planes and maple seeds the basis for life-saving, disposable UAVs