skysight-inc/HackerNews huggingface dataset:
instant in the sense that sending it doesn't take 3-5 business days. they're not necessarily meant to be tweets, although there's nothing wrong with using email for a system like that. they're not slowing anything down, in my opinion. they're to be used when necessary, just like most things. besides, after the initial email in a chain it seems that the trend is to drop that greeting anyways.

there are issues larger than writing "Greetings" in your email that you can solve. :P
I'm curious - but feel free to not dive into it if uncomfortable - about your current job. What job could you possibly have that means you don't get to create anything from the ground up?

I applaud your will to pivot to something else, and your desire to learn something new at a deep level. Best of luck!
new purpose for RSS and cause for last weekend's project:

http://www.pclapper.com/GetRandomRssSummary/
Replace shoddy with limited and I could agree with that. BeOS died very young.

Pretty much all those points could be made at the inception of any OS. OS X had a nice jump on that because it was NextStep and had been developed for well over a decade.
It could work with my boxee setup.

It could work on my iPad while I'm on the way to, or in the mountains.

It could work when my connectivity sucks / is saturated.

It could have the things I want when I'm ready for them.
Interesting; kinda threaded live chat. Hard to know where to look for new messages, with them appearing arbitrarily in middle locations.

Perhaps all new messages could appear at top or bottom, with really long background thread-lines tracing them back to their antecedents?

And some sort of quick expand/collapse, or focus/defocus, for narrowing in on just one thread?

Or maybe even: the thread you're 'watching' if left-justified in a generously-sized font, and everything else is right-justified in a very compact font – making it possible to focus on one thread, but maintaining peripheral awareness of (and one-click-focusability) on all others?

Added: I see that there is some sort of click-to-focus, but thus far the logic of its effect eludes me.
interesting point - I think people who "donate" do it out of gratitude rather than creation of entitlement. By virtue of that, the complainers are less likely to come from the actual donor list.

My empirical evidence comes from the Cyanogenmod Android project - where "when can I haz gingerbread" or "this sucks - why arent you spending enough time fixing <bug>" is always from non donors.

NOTE: it is easy to see this trend on the CM forums, because your forum handle displays whether you are a donor or not. That I think is an easy way to lower the credibility of flamers (something that isnt possible on Clojure Google Groups). But then again, maybe that in itself give rises to the expectation that "if I donate, I can flame". I havent seen it happen on the CM forums though.
No, these are for a one domain to another, not a domain to a subdomain of itself
The cost of writing 'Hello' in an email is very minimal, the cost of reading one of these greeting is also very minimal.

The cost of being perceived as unfriendly, too-business-like, and demanding is just so high. It's not worth the risk.

PS: I don't care either way, but I have heard multiple people comment on how they don't like doing business with person xyz because their emails are extremely cold and unfriendly. Because of this I have alway add a nice greeting and a friendly closing. The middle is all business/meat, but padding it with some friendly talk can really help.
Lead, mercury, and Tobaco where known to be unsafe before I was born. That's a fairly long time from my perspective. Also, in the short term they are reasonably safe. It's only because we can look at long term exposure that we understand how harmful these things are.
It's also run on Alpha in the past, but both the Itanium and Alpha ports are pretty thoroughly marginalized at this point.
Memex 1.1 » Blog Archive » Facebook: the craze du jour
I actually know one that is true. The Air Force back in the 60's brought some old piston engine transports back into service. The mechanics could not get the engines to deliver the power to spec, they read the manuals, and did everything they could think of, no dice.

Finally, the AF hired some old mechanics out of retirement who used to work on them, and they promptly had them running to spec. Turns out there's a lot on how to tune them that was never written down.
I picked up an 80GB disk for my system a few years ago, when the X25-M2 model came out from Intel with a price drop. It was great. Firefox launches in 2 seconds, GRUB to login in < 10s, login to desktop in < 5 seconds.

What really hit me hard was gaming. I like to play a few video games from time to time, but they are getting HUGE! For example, World of Warcraft take up about 13GB, and to upgrade to the 4.0 patch it required an additional 20GB (it didn't say this, but that's how much space I had to free before it was able to complete). That's about 35GB for one game, and that's half the space on my SSD. I installed StarCraft II recently and that required 6GB for the download and 14GB for installation.

Of course, when I moved the games to an older disk I suddenly had over 50GB free.

It's my observation that disk will tend to fill up. First it was with programs, then it was with audio, now it is with video and video games.

As soon as we get more space, we will increase the resolution/fidelity until the average person can't tell the difference from a live event.
I recently got rejected by Google. Most interview questions were straight out of an algorithms book. Like write an interval tree, a hashtable, some dynamic programming question, etc. I probably failed because I misunderstood a trivial question as something far more complicated. As for the interviewers, half were quite nice but the others seemed bored and distracted. I won't try again.
Business Model Building Blocks: Join The Conversation & Win Business Coaching
It may run on Itanium, but it doesn't support more than a fraction of the x86 server functionality.

http://technet.microsoft.com/en-us/library/cc772344(WS.10).a...

I don't see how Microsoft will ever shed the x86 legacy in Windows. Intel would have an interest in killing off arm-based laptops with aggressive pricing, and there really isn't any history of Windows developers rebuilding apps to support other chip architectures.
1. Invoking google (the outlier of outliers) at anyone trying to make an otherwise valid point is like a special Godwin's Law for startups.

2. Google is also a monopoly. If you are blessed to be in such a position, almost nothing you read applies.
Aim for a Lifestyle, Not a Jackpot
How a Chicago Firm Innovated Wikipedia Donations
Somewhat relevant (and more amusing) is the story of Scigen[1], a tool that three MIT CS PhD students put together to generate fake but legitimate-looking papers in order to troll conferences with low/no acceptance standards.

Their site also tells the story of submitting and attempting to present a paper to shame one of these spammy, fake conferences.

[1] http://pdos.csail.mit.edu/scigen/
The Future of Media: Kindle or iPads?
>On the other hand, if you can afford to develop a loyal user base first, then that is your best path to success.

Assuming you don't define success as "stable and profitable company", I suppose it is.
I did, but you didn't read my 30-page legalese fine print.

/sarcasm
This is just a prediction, but notice how Congress will suddenly be able to work together when it comes to passing this bill. I hope the cynic in me is proven wrong.
This piece is clearly talking about an enterprise sales model, and because of that I think his point about taking extremely low amounts of money for first customers requires a word of caution.

In our experience at our last company, which was an enterprise software company selling a powerful data analytics platform, almost ALL of the customer negotiations at all stages of the business involved "Most Favored Nation Pricing" clauses - as in, the customer wants to know that no other customer has gotten a better deal. This can be subject to fixed volume discounting, etc. - i.e. someone buying 50 licenses prior to the currently contemplated sale of 20 licenses could have paid less. However, try telling a potential customer that someone previously paid less for the product they're thinking of buying and at a minimum you'll have a hold-up of months of red tape as they get an exception to their purchasing checklist authorized. These corporate purchasing processes are highly inflexible and often imposed by Sarbanes Oxley "internal controls" measures (meaning they're dictated by outside auditors, and not up for discussion) - they are real and need to be factored into pricing strategy.

A good workaround we found is this: make your early licenses have some type of specific restriction or obligation that you will relax in the different class of licenses you will sell later in the company. You might restrict early licenses to dealing with a certain type of data, or you might even add the obligation of participating in a "marketing case study". Do something along those lines (and get it actually written into the contract) so that in the future, you can with good conscience sell less restricted licenses at a higher price point under the inevitable MFN clauses you'll get with Enterpise software sales.
Equity is worth $80 million (and dropping). A buyer would also have to deal with about $500 million in debt, probably repay it.
ASP.NET MVC Preview: Using The MVC UI Helpers
The Database Programmer: Theorems Regarding Business Logic
IceT Owes Me One Million Dollars.
It really depends on what kind of software development job you are looking for. I believe writing a web server will teach you a lot. You'll learn more about the HTTP protocol and you'll learn/master socket programming.
Your two examples differ in a way you fail to recognize.
The illegality of the beer example comes in the act of giving to the underage person.
The illegality of the documents example is the first exposure of the documents to someone without clearance.

Both examples involve two steps; the beer example is illegal in the final step, the document example is illegal in the first step.
Some ideas / thoughts:

On viewing your site, my first thought was why am I being prompted to log in? I've just landed, the first thing I want to do is find my feet.

I suggest maybe put a recently submitted playlist to the right of the main page. Then have a dialogue with a button with something like 'create playlist' to left.

Allow people to create playlists anonymously if they want - then give them the ability to share it. That might encourage some people to stay on your site and generate content who otherwise may have left. I know you're aiming for social, but how about the ability for people (logged in) to vote up / down playlists being the more social aspect?

Having names / titles for playlists as well, that way someone is likely to create more than one and give them proper labels that people can use in rating them.

I'll be honest, I don't think I can picture myself using this app as is. If I want to share a song with people I know I'll likely send a link in an IM or put it in facebook.

As you're probably aware of, there are plenty of places which do the whole music + social aspect already, so why should I use your service? How is it different and more worthwhile than simply sharing links on facebook / twitter? These are the kinds of important questions I'd ask myself.

I think your application does have potential though. I'd say worry less about number of users or level feedback you have and more about the product you're creating at this early stage. The important thing is to keep doing stuff - keep adding features and refining it.
"Almost anything a user does with your app is helping you"

Like a rancher is helped by docile livestock. But the relationship between the rancher and the livestock is very different from that between the rancher and the actual customer.
Tanks in the cloud - measuring web infrastructure
Could Kinect be Microsoft's iPod?
Google's customers are the advertisers.

The end users are Google's product.
Definitely concur on this. A C300 in the standard drive bay and a seagate momentus xt in the optibay is a wonderful combination (or a second ssd if you are really trying to pimp your ride...)
Abolish the senate - don't just reform it
Things move too fast for me. I'm trying to understand what I'm looking at exactly.
When a bank lends you money, they're really just signing a piece of paper that says, "we've given this person X dollars", thus it counts as a liability, in that somebody could come calling for that money.

Sorry, does not parse. When the bank lends you money, it's an asset for them. Like you mentioned elsewhere in your comment, deposit accounts are liabilities for the bank, because somebody (the depositor) could come calling for the money.
Oh, yes, any results we came up with running the experiment here should be properly doubted from the start. Not only would participants know too much about the experiment, but over the Internet participants wouldn't be directly observable which certainly throws out any real legitimacy. I was only thinking in terms of possibly recreating enough of the test to experience some of the same results, regardless of how those results might be perceived, but I think too much information about the test is now known.
+1 on the auto complete. I don't know Grooveshark all that well. I'm still unsure how to create my playlist... so I type the title of the song? How does it work?
There appears to a habit here at HN to downvote a comment simply because one disagrees with said comment.

You have a valid point. I disagree, however.

One has to weight the situation. A government operating in the darkness of secrecy will not lead to anything good.

It started with simply stopping lawsuits against "renditions" by citing national security concerns (i.e. the government can basically do what it wants and then just draw the "national security" card) and goes on with knee-jerk, infantile reaction against WikiLeaks.
IIRC BeOS had no security model; basically everything ran as root all the time. You might say that it had no concept of non-root. Remember that Be viewed Mac OS 8.0 and Windows 95 as their competition, not Unix.
> Haha, condescending ever.

Not sure what you are saying here. Please use grown up sentences.

> The connotations are different, that's the slant someone is trying to put on whether their discrimination is good or bad. We change how we act towards one person such that they benefit relative to another's detriment. Whether it be preferential treatment by omission of detriment or preferential treatment by application of benefit if the treatment alters according to the characteristics of the subject then we have discriminated.

You are a one trick pony -- once again you try to deflect. The guy declared he was not giving someone preferential treatment. It does not matter whether this is by lack of advantage or by taking away disadvantage, non-preferential treatment by definition is not preferential -- therefore no one is getting advantage to another's relative detriment.

> The question doesn't bother me. I don't think your assumption stands to much inspection - I'm sure you can imagine many scenarios that would leave someone in an "entry level" position against their will. Why does it matter how old the person is, can they do the job, will they do the job? One can change one's age no more easily than one can change one's sex.

Hrm.... deflection again! The fact that a reasonable assumption can be made does not eliminate other possibilities. Yes, a person's age is strictly a product of forces outside his control, however getting an entry level position at that age is certainly within his control. Why choose that route? There are other options. Why not choose them. In these cases of choice, it is worthwhile to examine the candidate. See by examining one's choices, you can maybe learn about their ability and willingness to do the job. (remember, these are the things you claim to care about, and now we can learn about them!)

> I love these sorts of closing statements, they must be the thinking man's ad hominem "anything that disagrees with my stated position would be idiocy", that's almost the definition of tiny-minded simpleton. </sarc>

Ohh, man out of nowhere-- deflection! I never saw it coming-- honest. It's not really ad hominem. Not even kind of. Im not even declaring you to be idiotic, in fact, since disingenuous is pretending to know less, I sort of did the opposite. I have no problem even with you disagreeing with my position. I was merely preempting a disingenuous position of moral absolutes being attached to a word that has vague boundaries on its applicability (rendering absolutes impossible). You have clearly demonstrated your understanding of the vague edges of the word discrimination by using it in two different senses already, so any claims of not knowing at this point would be false. Looking up the definition of disingenuous will get you the rest of the way to my statement.
Starting with the Torch BlackBerry's have a webkit browser and can render on the canvas. (disclaimer I work for RIM on webkit)
I think you could better apply this logic to TSA.

But with TSA, something more important than money is being "handed over"
Yeah, didn't mean to imply that -- just poor wording on my part.
I have implemented two clients, a generalized libpurple transport, and spent significant time on a server in a professional environment for sale to real customers. IRC isn't a replacement for what it does, and yeah, the problems come from the problem domain, not the protocol. I'd know the difference. None of the "professional" protocols seem to be significantly simpler, because they can't be... the domain complexity forbids it. I spent much more time working on semantic issues than I ever did working on the raw XML, orders of magnitude difference. The XML was always the easy part, even if JSON would have been even easier. The trappings are irrelevant. I could transform the entire XMPP protocol stack into JSON in a week, with implementation in ejabberd and one of my clients. XML is a sideshow.

The problem is getting the standardized semantics. If XMPP taught me anything, it is that it doesn't matter how many specs you throw at a programmer, they're just going to bash on the program until it sort of works most of the time and release it. That's where your roster problems come from, it's where a not insignificant number of your transport problems come from too. (Though the transport protocol is one of the spottier bits of the protocol.) The core bits of XMPP are generally reasonably well specified and in my experience actually held up surprisingly well as I bent and spindled it a little bit. (Corporate customers don't "get" rosters, don't get that you can start with a blank roster and work your way up, so I added a module to build rosters based on grouping criteria specified by the user and driven by outside input. Well beyond the stock ejabberd shared rosters, but pretty custom to our environment. XMPP actually dealt with these semi-magical roster entries just fine, to my surprise.) Those specifications really matter and just sort of bashing some stuff out that's 90% correct most of the time isn't good enough when you're trying to communicate with so many different systems. XMPP actually managed to avoid a lot of problems that even the "professional" systems had, having learned from their experiences; AIM last I knew still had some encoding corner cases you wouldn't expect in a modern program, all of the protocols had major encoding growing pains, surprising versioning issues, all these little quirks inside them that you never noticed because you can paper over a lot when you control both the clients and the servers. Again, I know it's not perfect but in the space of "deployed IM protocols" it does not make a bad showing.

IRC clients are actually just as quirky, IRC just doesn't hang on to anywhere near as much state or you'd see it mangled, spindled, and mutilated too. (Also part of the reason it's not a replacement, real users want that state.) This is fine, too, I don't have a problem with IRC for what it is, but you can't just drop it in everywhere you see an XMPP server.

If you try to work IRC up to be a real, true XMPP replacement, you'll be complaining about how hard it sucks in no time. Too much suckage is in the problem space.
Game Preview: Voxatron - voxel-based, destructible environment, 8bit soundtrack
that's interesting that you come from finance, I'm coming from a similar field in terms of hours and job satisfaction. These four books are exactly what I'm looking for.
Defamatory speech isn't protected. But I still don't think "low-value" is a helpful description.

For example take comments on Slashdot or wherever saying "first post" (or "first comment" or whatever). Do they have value? Most would say no. Does that mean they shouldn't be protected?
I really like it! I think it has some potential.
I'm sure it worked on his machine... :P
Whamcloud Staffs up for Brighter Lustre | insideHPC.com
More barely concealed anti-wikileaks pro-facebook propaganda from the establishment.
The login thing is also what made me immediately close the tab last time I checked this website out. (He submitted it sometime earlier this week or last.) I just wanted to take a stroll around the site, see what's up, get carded at the door.
This reminds me of a DHH talk at startup school where he says it's not just about being "the next ... INSERT BILLION DOLLAR COMPANY HERE".

The funny thing is until I started reading HN I had no idea the extent to which people are out here building apps frantically for the "big exit".

When I read about how much 37signals get pissed off at being referred to as "a lifestyle business" I had no idea that this subculture chasing VC and Angel investing even existed.

I had a vague notion that people got investment but I feel a little uneasy about the way that young kids coming straight out of high school are being influenced by this culture.

Everyone just wants to "be an entrepreneur" and no-one really seems to know what that means. In most cases, business is about raising invoices, not capital.
I would go where Grooveshark users are. Find who they are and reach to them. Use twitter search and other social monitoring tools to find them. http://lithium.com has got a good social monitoring tool you can use free for 14 days. Should be plenty of time for you to find enough of them.

Once you found them, ask them if they would part take into grapev.in mavens. Tell them you are looking for feedback from heavy grooveshark users and in return they will be the only ones with early access to some grapev.in features.

Create them a special account, give them a place where they can connect to each other. Make them super fans by iterating and get to market fit with them.

They will evangelize your product for you - sounds like a good starting point.
If you do end up having to reinstall, use http://ninite.com/ to do a bulk install of some common apps.
BeOS was amazing. It simply smoked the competition. It was sleek, functional, good-looking, fun to program for, and had blistering speed (remember it playing 6 different videos each on a side of a rotating cube?).

It was not free software, but with features like that, who cared, right?

Well, its community cared when BeOS was mutated into an "appliance OS" and then later sold off and closed down.

I'm not optimistic about Haiku. As soon as it becomes popular (and I don't see why it wouldn't -- it's aimed squarely at knocking the socks off of end-users), I bet all the core devs get scooped up by some company which will then add proprietary lock-in features and sell it to users.