skysight-inc/HackerNews huggingface dataset:
There is a bunch of ways to distinguish important updates from the others. First, prioritize updates from projects I am or have contributed to. Second, updates from people close to me in the social graph (i.e. the people I watch on GitHub or people who belong to the same organization as I do). The frequency and size of updates should matter too - an usually silent project with a big update should have an advantage over noisy projects. Filtering out typical bugs (or commits/PRs fixing them) from the top priority ones should be fairly easy too - all the information is already there (comments, labels). Finally, you can go insane and start analyzing the actual code or even use NLP for commit messages/pull requests/bugs and make decisions based on that (for instance, prioritize projects that use similar tech as I do, changes that mention me or touch the code I've created or touched recently).

No need to turn off anything, just make it smart.
Yes, but that doesn't always help.

If your opponent is rich, they can hire an army of lawyers, and you'll generally need a correspondingly huge law firm prepared to invest their own time and money in countering that. The kind of law firms we're talking about are both few in number, and generally fully-engaged by well-paying clients -- clients like your rich opponent. The incentive to take on a case like this is pretty limited.
QuickbooksOnline has done an amazing job innovating over the past few years - it's the best product in its class now, easily. Yes, there are certain things it still can't do - and that makes it very frusturating, but I don't see a reason to use any other service.

I think the main flaw with this idea is that everyone wants to make accounting "simple." Unless you are going to focus on a specific niche, I think you're not going to solve the problem.

It sounds like you want to solve the problem of visualizing accounting data better than any other product or service. Why not build an app that works with the quickbooks API (Bill.com is the most notable app out there that sync's with QB). Just an idea..
It's not that different from any other type of selling. If you ask someone out, they'll probably say no if you seem to want to go out with them a little too much. Or at a job interview, you'll probably be told no if they sense that you want the job a little too badly.

The reason being that people tend to wonder why it is that you want it so bad, and they tend to assume that's because you can't get anyone else to acquire/go out with/hire you.
I know, I must have been reading way too quickly. I thought he believed the actual code had to be in CoffeeScript, so I was explaining that it can compile to relatively readable JavaScript. When I came back and reread my comment, I wanted to edit or delete it, but it was already past the two-hour mark. I do agree, it seems rather silly to have the docs for a JavaScript framework written in CoffeeScript.

As sort of an apology, I wrote up a little bookmarklet to translate the page into JavaScript at http://news.ycombinator.com/item?id=3641217
Irrelevant Digression:

The niftiest progress bar I've ever seen wasn't a progress bar.

It was a little morality play.

As the game installed a dinosaur slowly bounced across the installer window and _ate_ a hapless user .. who didn't send in his registration card.

Still remember that, seventeen years later.
The share button is only on the embeds. When you use the API, you won't have to worry about these. (See: http://mapbox.com/hosting/mapbox-streets/)

Tile loading should behave just like you see with Google Maps or MapQuest, or any other tile-based slippy map.
Indeed, I've been working on this type of tool (without the distributed component) for blog authors who want user-submitted corrections: http://edithuddle.com

When you want a central, de-facto version, it makes sense to have a way of aggregating "similar" corrections (both in type and content) from changes.
Yes, the only real difference is that, given sufficient local storage, the song will also get copied to your local device. This seems like an advantage IMO.
Can anyone explain something for me.. I'm interested in subscribing to the print edition. Does subscribing mean I also receive the back-catalog to issue #1 in print also? (This is what I'd like).

Thanks
Looks like it may have been abandoned. Last commit was 5 months ago. https://github.com/anatoliychakkaev/railwayjs.com/commits/ma...
As an aside to answering your question the toughest thing is dealing with someone overseas because you can't sense the nuance in their writing or (if verbal) their voice. The english many times is broken and that messes up all the patterns.

Here's an example that is playing out right now.

Name offered for $6000. No other buyer for this name. If it doesn't sell it will probably never sell for 10 years.

First offer from buyer:

"Thank you for that. I could do $1200, but that is not really in his ballpark. If he changes his mind, please let me know. You are welcome to take that offer to him."

What he did right: Made offer and made it seem like that's pretty much the range he will pay. "If he changes his mind let me know" as if he is going away. So a seller would think he can probably get $2500 out of this type of guy maybe for this name. (Nobody ever makes the first offer the best offer.)

What he did wrong:
No time frame to transaction. No sense on the sellers part that he could loose the deal. No sense that other names are even being considered (even though that's normally bs and can backfire).

Reply from seller:

(A short sales spiel showing why others would want the name) ending in "he might do $4000 but I have to clear that...".

Reply from buyer:

"Please ask him about how low he will go. I will see if I can get there."

What he did wrong: He essentially didn't barf at the $4000 for the name. He gave no kickback. So seller knows he can get that amount most likely. And maybe more.

Seller:

"Ok I will find out" (or something to that effect).

Buyer writes back quickly again:

"I am feeling pretty good about that. I think we can do it or very close to that."

Somewhat good: "I think we can do it or very close to that".
That essentially says he will pay the price but he gave himself a little wiggle room.

Bad: He replied to quickly to the email showing he was very eager. Time and tempo are important.

Then he writes back again a minute later to say he is ok with the escrow company and will write back soon. So he completely telegraphed his intentions. Even though he hasn't really agreed to purchase.

By the way this was a lawyer as a buyer. And this is the same stuff that happens with 6 figure domain sales as well.

So the deal right now is going to happen at $4000. The seller is fine with that price and doesn't want to loose the deal for fear he will get nothing.

In this case the buyer overpaid if he handled it correctly he could have had this name for $1500 about.

And as mentioned multiply by 10 and the same stuff happens.
Oral vitamin D is not taken up by the body all that well. If you do have a D deficiency and you're taking oral supplements, be sure to get your levels checked after 6 months. You may need to up your dose or get some direct sunlight.
I think I understand why this was downvoted - didn't know this wasn't ok. Now I know.

Only reason I mentioned this is that it brought the essence of the article out in one sentence (tl;dr).

Please either delete my comment, let me delete my original comment, or stop downvoting me. What's the point in downvoting someone repeatedly? I'm not sure how the system works on your end (or if you can see how many others have downvoted), but seems pretty harsh to keep doing this when there was an honest mistake. Thanks.
That's pretty cool. I didn't know that worked so seemlessly.

Nonetheless, in order to use a library, you must either read the documentation or the source. The biggest issue is that most CoffeeScript projects document with CoffeeScript. Technically, you could read the compiled source, but that's usually a non-starter unless I truly need your project. Otherwise, I'm more likely to find someone else that's solved the same problem, but has written their docs / source in JavaScript.
Facebook faced this exact problem with its newsfeed. The solution? Do what Facebook did. Allow people to watch projects and then subscribe to various levels of activity.
The power of symbols [video]
After living in the UK for six months with Amazon Prime.. its painful to be back in Australia where you can only get fast shipping from certain specific stores.

Well not painful, but being able to order something at 10PM and having it arrive at lunchtime at work the next day was such a better shopping experience than I normally get here.

I really hope amazon has aspirations of opening an AU store sometime soon.
There's probably a lot of opportunities in news aggregation on multiple level. My RSS feeds list on Google Reader is way longer than I can manage to read. If I had a clone (i.e. somebody who knows exactly what I find interesting) I'd definitely have him do that and tell me just the interesting stuff. Absent that, paying somebody to do a good approximation of it would be reasonable, if it's not too expensive.
Unfortunately, Atari owns a patent on little games loaded for someone to play while a larger bit of data is being loaded.
Who cares?

There is express, geddy, railwayjs, djangode, drty, Locomotive, spludo and probably a few others that I missed. All of them are modeled after rails/django.

The last thing the node-ecosystem needs is yet another half-baked rails-clone.

This may come across harsh but I really don't understand why people keep beating that dead horse instead of tackling the node-vision: Build a framework that spans client/server. Make it good. Start by not pouring your time into yet another rails-clone...
Youtube says your link is adult content and wants me to login. Believe it or not, I never logged in there, and was never asked to.

Damn Youtube, it's How to light a grill in 2 seconds, not a girl.
I agree 100%. This has bugged me for a while. I use the watch button to basically favorite something that I don't want to fork. The way the current timeline operates right now is useless to me. Perhaps a way to show activity without regurgitating the commit log in a timeline form. sort the watched repos by recent activity and then when you click on it show some things that happened via ajax.
It's a dangling participle... heh 'dangling'.
People really care enough to make it an item worth that much skull sweat? Weird.

Unfortunately, yes. The B2C desktop software market is such a cutthroat environment both in terms of what users expect and how much competition there is. It's an entirely different beast and the devil really is in the details. For some reason, bloggers, software review sites, magazines, etc. will really run desktop software through the mill and pick at the nitty-gritties in a way that they don't with webapps. Perhaps because with webapps the user experience is rather ephemeral and can be easily patched or fixed whereas with desktop apps everything has a very "final" feel to it.
Yes. 100 times yes.
For me at least, this is certainly true. Even with significant dietary supplements and spending more time outside, I've only been able to get up to about 25 ng/mL. This is a significant improvement for me, as my initial levels were below the sensitivity of the test, at <0.25 ng/mL, but still not ideal. I hadn't considered visiting a tanning salon; I may try that soon if things aren't notably improved after the next time I get this tested.
I agree ... mostly.

One of the examples was bytes downloaded. The reason I, and I suspect other users, interpret that as % downloaded is that in most interfaces (e.g., iTunes, Firefox, Safari), below the download progress bar, it says "XK of YK". (There is also an estimated time remaining, but it's typically not on the left side.)

In other cases (installs), yes it makes sense that the simplest interpretation is time, because that's what we care about when installing: how long until we can use the new shiny widget.
That, I can believe. I don't watch any repos, though, so I don't know. I care about the ones I contribute to, because I forked them and issued pull requests, so I want to know how they're doing. Apart from that, I don't really care about watching other people's development live.
Suggestion: use a succession of checkpoints (including start and finish) to keep track of overall progress. Then create a database of checkpoints along with timestamps (either from historical runs if this is a process that normally runs often for an individual user or from a few sets of lab runs if this is a one time thing like an installation). Now, calibrate the checkpoints to the expected position on an "ideal" progress bar given the historical data and present that to the user.
There's that, but "users" and "watchers" are different. I care about actual users more.
Read the small print. "Traffic is unlimited. If you exceed 40 TB / month, the connection will be limited to 10 Mbps."

That works out to a bit over 100mbps commit. A fair enough deal but nothing spectacular. Doing 10gbps ports is a neat marketing trick but I can't think of too many situations where you'd balloon that large and yet still sit within 40TB/mo where a gigabit port would be a serious bottleneck.

Just keep in mind the carriers are using at most 40gbit and 100gibt optical lines and trunking them together. If you wire an entire neighborhood with gigabit last mile, or a DC with 10gig to the node, it all coalesces somewhere at the network access points. For home subscribers, I'd much rather prefer a quality product in the 10s of mbit for the next few years, the only point I was originally trying to make. The argument for laying gigabit last mile has more to do with last mile life cycle IMHO than truly giving customers a full gigabit pipe at the moment.
"A classic bizdev trick: schedule meetings at inconvenient times or in inconvenient circumstances; if the other party accepts, they want a deal to happen."

Very true. Of course if a party makes this mistake they can easily put the fear of god in the other party by changing their pattern of response.

If you tend to reply in a quick fashion and appear very eager and then all the sudden there is radio silence the other side will intuitively know something is wrong. (Ever have that happen with dating where the girl all the sudden doesn't respond as quickly and you know something is up..)

The mistake that most sellers make is assuming that someone's eagerness is locked in. That a party doesn't change their mind or doesn't have another circumstance come up that makes a sale unlikely at any price. (Similar to what the OP was saying.)

No deal is done until the fat lady sings.

The domain in the example I gave I recognized would have no other buyers essentially. So I advised to close the deal as quickly as possible even though a little money was left on the table. But many sellers simply won't take that advice they are gamblers.
I have two suggestions:

Activate a 'quiet' mode? In quiet mode nothing is sent to people's feeds.

Daily Digest mode. Daily digest would do just that. Lump all update in a day into 1 news feed.

I'd be happy with either option.
Add Lenovo ThinkPad to the list. I always order mine with no camera.
Thanks SkyMarshal, I use Play all of the time. I've never tried Lift though--I might give that a go soon as well. I'm curious about whether or not there is a framework of Clojure however. From the responses, it seems like Noir is the popular solution these days :-)
I can't buy that. Customers would be more likely to use your project if it were more active, not less.
I have heard it very difficult to get a prescription for Modafinil, even if you have work sleep shift disorder because most doctors aren't used to prescribing this drug.
I worked for Microsoft on Visual Studio extensibility back in the early days of .NET. At the time it was ground breaking and exciting that there was finally one IDE for using all of Microsoft's programming languages with no hidden APIs. The IDE is now long overdue for a rewrite in .NET, but it would be such a massive undertaking. So far the business benefit of that has yet to eclipse the cost.
I Was a Warehouse Wage Slave: Inside the online-shopping shipping machine
CSS Color Palette Extractor
Extract colors from CSS in Javascript
If you think that tower may solve your problem and the only obstacle is that it's written in coffeescript, then learning coffescript is now solving your problem.
Always listen to your customers, but don’t always do what they say
Everything old is new again.

In the late 90's and early 2000s, video game companies that used OpenGL instead of DirectX offered the same thing in a program called GLSetup:

http://web.archive.org/web/19991013110237/http://glsetup.com...
What, seriously?? How the hell can you patent that??
Want a promotion?  Think like an entrepreneur
The facts emerged.

You called my posts "lies", "hate", "garbage" and "antisemitism" and made claims backed with no references.

I provided references to Israeli and Jewish sources that any reader can check. Here are some more:

http://www.icahd.org/

http://www.heraldscotland.com/news/politics/auschwitz-surviv...

http://www.zochrot.org/en

http://mondoweiss.net/
I was skeptical of Hacker Monthly when it was first announced. I haven't been following it, but on seeing this article I was so impressed I subscribed to the print edition right away. A great excuse to spend less time on HN. :-)
Your symptoms sound very similar to mine. I eventually had a large vitamin, neurotransmitter, hormone, and adrenal panel done, including saliva and urine samples throughout the day, and blood of course. I was severely deficient in vitamin D, very low cortisol, and notably low B12. Since starting to address these issues, my life has improved significantly. If you haven't had similar tests done, I encourage you to do so.
+1

I've never disliked the fact that it was built, everyone has fun playing around with little transpiler things but it's turned into some retarded religious warfare. The show-stopper for me is when it gets to the point of pull-requests containing "Add coffeescript support". Once you go that far it's just flat-out wrong
Games are the ultimate art form
>Well, you haven't learned it unless you memorised absolutely every aspect of it

Oh man!

I guess I don't know any programming languages whatsoever.
I Was a Warehouse Wage Slave: Undercover in the online-shipping industry
I would love to see that patent. I have a hard time imagining it would be enforceable.
Additional they should introduce some "version notice", you get all the notices on new versions on your favorites.
Just a simple function for the creator.

This is the thing i always click watch in the first place, but i never get to the dashboard in reality.
Sivers has some good advice on this, though it may not answer your last questions:

http://sivers.org/how2hire

TLDR:

1. Reduce your big idea to “Version 1.0”.

2. Write a simple overview of what it does.

3. Write a detailed walk-through of every click.

4. Break it up into milestones.

5. Make your first milestone a stand-alone project.

6. Post it at elance, guru, odesk, vworker.

7. Hire one from each.

8. Continue with the one you like best.
I think your view may be just a little more cynical than reality. I'm not saying reality isn't bad (it is), but, in the little bit of "free" blue ocean that exists, incredibly vibrant communities are thriving. Whether that is people share truly open photos on Flickr or entire operating systems being built and given away or authors and musicians providing their content to the community, there is still life in non-corporate-controlled culture.

(And, FWIW, I'm truly cynical about our corporate overlords.)
>You can publicly watch one of their projects; this is similar to "liking" something on facebook.

>If you commit "too often", people will get annoyed and unwatch you.

So don't watch projects you're not interested in watching and leave the Facebook mentality at Facebook. Issue closed.

I couldn't imagine not working on my projects out of fear that somebody who's feigning interest might stop feigning interest. Who thinks like this?
As a maps dev, I'm very familiar with those exponential scaling problems, 4^z is a bitch. :-) Thanks for taking on this problem.

What zoom level are you all at in major US metro areas?
Yeah, it was popularized by physical tally counters [1], long before it made it into software UI.

They are still used sometimes at concerts or carnivals to tally up people entering a location for records keeping, and to make sure that you're under fire code.

I have one of these counters too, but I only use it on the range to keep track of how many targets I've hit by sheer chance. ;)

[1] http://9cloud.us/c/general/pictures/album/36357/id/1239690/
>Why on earth is this disturbingly so objectionable?

Ruby dev here with limited JS/CS knowledge. Are there any sections of CS where the semantic mapping to JS is not obvious? It took me about five minutes to figure out what was going on.
Yes, subscribers receive access to all issues, including the back catalogs.
Not necessarily, it's effectively no different than if you were to support the same feature-set in the single library
I had a similar problem with a customer that wanted a smooth progressing progress bar for periodic sync process where I had no idea how many actual entries were being sync'd on any given run (the cost of finding out == cost to sync)... the number was almost always more than the previous time.

So what I did was simply calculate how long the previous run took, add 10%, use that as my new baseline, and show progress based on the percentage between. Often this would mean the progress bar went straight from 93% to complete - but this was preferred (better than stalling at 100% for minutes at a time).

Eventually we automated the sync process, and the customer was happier looking at the occasional exception report instead of a progress bar.
I'm a contractor. Make sure that the contract specifies upper limits, and that it covers some process. For example it should specify the maximum monthly or weekly payment as appropriate payout. It should have a termination clause ("either party may terminate the contract on immediate written notice for any reason or for no reason"). It is also a good idea to cover invoices and payments ("invoices must be submitted with 14 days of month end and payments must be made within 14 days of invoice receipt"). That will remove a lot of stress from the relationship so both can concentrate on the work at hand.

I've always done hourly because the clients were not able to specify upfront exactly what they wanted, and priorities would keep changing. Additionally they would find that I'm good at other things and can help in ways they didn't anticipate. Everyone benefited.

If you can accurately specify exactly what needs to be done, and know you won't change things then ask for fixed price bids. Contractors will know how to respond. There is no perfect way of protecting yourself from below expectations work, but contract limits mean you know the worst that can happen. (eg if you say you won't pay for more than 40 hours a week then they can't suddenly surprise with 120 hours of work after the first week.) Being able to immediately terminate also means you can cut your losses early if you need to.

I always end up spending a lot of time on the intellectual property parts of the contracts since they are usually egregious land grabs written by lawyers. It is really tedious getting that fixed up. Know up front what is happening with the copyright (you can retain it exclusively, or give the contractor their own copyright on a copy) and licensing. I'd certainly give discounts for open source work, especially something that I can freely reuse elsewhere - it helps as a reference and it helps future work.

TLDR: you can't perfectly protect yourself, but be optimistic and plan on good things happening
C++11 threads tutorial