skysight-inc/HackerNews huggingface dataset:
Cats aren't very good at catching sticks an dogs aren't very good at catching mice. Therefore you can't have the dogs trying to do what a cat can do....

Except design is different. As a developer, once you have worked with some PSD efforts a few times and then worked with real dynamic content then worked with a real client to get the thing to actually convert sales, then worked with the client stats you have got a good grasp of when something is right on the design front. Plus you can open the css and do something about it. Or you can open up some stuff on the server side or put in some hack with javascript to get the usability to what it should be.

Designers are completely out of the loop after go live, they have done their 'lorem ipsum' stuff. Proficiency at UX comes from delivering the deliverables, testing, testing and testing. Listening to the client and the customers. It does not come from a few static designs.

I have never heard of a designer wanting access to the css to make that 3px change. They are welcome to it. They would make my day if they wanted to do that stuff. They do design for the web and the css is really over to them if they want to do it. The problem is that they would have to learn what a border is, what a margin is and what padding is. It is not difficult stuff.

The whole point of CSS is that the presentation is a separate thing to the content. Any developer would be happy to churn out the content blocks and sensible markup and hand it over to one of these PSD experts for them to get exactly to their 3px requirements. But in the real world it does not happen. Developers can dive in and fix something at silly o clock on a Sunday, but would anyone ever call a designer at such times even if it was a UX issue that was the problem?

Obviously there are some fantastic designers out there - allegedly - but, in general, designers don't do the hard stuff or even bother to work with live content. Far too many of them produce static nonsense in PSD format - a trade that should have been pronounced dead the nanosecond the iphone came out. They also perpetuate this myth that all developers are totally retarded when it comes to anything to do with aesthetics. Yet it is the developers that implement design, learning along the way. Rarely if ever is it the other way around, and, should a designer dare to do that they will get clumped in as a 'front end developer' and have some retarded PSDs foisted on them by some manager that thinks only designers can have any input whatsoever regarding UX/UI design.

How often do you think a developer tests something? A given page can be tested 100's of times. Along the way 'this checkbox might not be needed' or 'this dialogue box makes no sense' or 'this process is tedious' gets discovered. The guys with their PSDs just do not have that insight.
I feel pretty confident in saying that at least some poorly-written web apps will end up sending new status codes to user agents that are not expecting them.

I also feel pretty confident in saying that it will be the browsers that will be perceived to be "in the wrong" when they reject or ignore such responses, even though it's solely the fault of bad web apps. (See how browsers today need to accept and try to correctly handle totally broken and incorrect markup, for instance.)
One million Forbes accounts reportedly stolen in Syrian Electronic Army hack
You tell by looking. This will utilize people's very well-developed pattern matching and spatial memory abilities. That said, it's not too hard to imagine a quick "show me where I am now" overlay, or a breadcrumb type header/footer/sidebar that shows what regions of the desktop your view is zoomed into. This is the opposite of modality: everything relevant is right in front of your face.

If an argument from authority means anything, Jef Raskin, one of the creators of the Archy system mentioned, is a large part of the reason modal UIs are Considered Harmful. If he thought ZUIs were an answer, well, you might have something mixed up.
He made that assumption under the (incorrect) belief that you didn't fully understand that it was only a single game of pokemon being played.

He had this incorrect belief because he inferred from your statement, "it would be cool to see which starting Pokemon got used most", that you thought multiple games were being played.

He made this inferral because in the Pokemon games that he has played(recall he hasn't played yellow), you cannot get all of the starting Pokemon in a single game.

His own anecdotal experience resulted in a differing interpretation of your statement than was intended, and I would be remiss to not mention that fact that I 'mis'-interpreted your original comment in exactly the same manner as he did.

What a retarded and unfortunate happenstance this has been.

Not to mention the 50000 people watching the stream, an extremely active chat, and 20+seconds of latency; how exactly do you think that any qualitative findings in a post-mortem of this social experiment would be in any way indicative of the communities preferred starting Pokemon.

Furthermore, are they really "starting Pokemon" in yellow if you only really 'start' with Pikachu?
Why is this an argument between you and the engineers? Get latest, make the change, test it as best you can, commit it with a descriptive comment, and it'll go to QA for the next deployment.

What, you want somebody to do it for you?
True, but not on my area of work. That is seldom the case.
This is the only decent routine I was able to find:

http://www.youtube.com/watch?v=8JG7yzkGOYE

Short and sweet. Rest of videos is just a bunch of torsos.
When it's not clear that someone who can do something about it is even present, it's usually just an "in" to post a low-value comment. Zap all the thousands of aggregator comments complaining about fonts/background-colours and nothing of value would be lost.
As a child I was more than happy to spend ~10 minutes waiting for my ancient computer to boot up and load a game, and even now all the League of Legends players cope with absurd startup time. In contrast, it'll take less than a minute to put on some VR goggles.

The comparison with 3D TVs isn't so valid. In contrast to gaming, TVs are both casual and multi-user. Making sure everyone has the right glasses to watch 20 minutes of the Olympics (while conversing or eating or whatever) is much different than sitting down by yourself to do some proper gaming.
Cheaper prices would be one.

As a merchant when a customer chooses to pay with bitcoin I pass on the savings (that would instead go to middlemen like paypal and credit card companies) onto the customers, and they love it judging by feedback received.

Credit card companies and paypal etc are parasites who siphon billions from global commerce, their business models are based on old money transmission methods.

There used to be a time when people would ask as to why they would use credit card over cash, yet people moved on and accepted new concepts and technology
That's correct, you can set in in Wallet settings:

https://support.google.com/googleplay/android-developer/answ...

Checking your tax rates

Sign into the Google Wallet Merchant Center.
Next, click Merchant Settings.
After that, click Sales Tax.
Then, click Edit next to the country or region whose tax rates you'd like to set.
(Optional) Select the state/country/province and set the tax rate
Finally, click Save

Also:

If you are a developer selling apps in one of these countries, please note that we have applied the tax rate set in your merchant center to your existing tax exclusive prices.

Keep in mind that Google will continue to pass on the entire tax amount collected to the developer, and calculate the 30% transaction fee off the net price of the product. For example, if your tax inclusive price is 10GBP and your VAT is 20% (as set by the developer in the Google Merchant Center), then Google will first calculate your net price (8 GBP) and then apply a 30% transaction fee to that amount (2.4GBP fee). The developer would then receive 7.6GBP (includes tax collected).
Well you do have to wonder as to who pays their bills
What's going on in Venezuela in a nutshell
> Does the designer know how to use git and commit properly? Do they know on what branch? Understand the deployment schedule? Perform browser testing? Are they part of code reviews? Do they understand whether that rule is used by just that component, or just that page, or if it will affect code elsewhere?

If he doesn't, find one who does. A web-designer who doesn't understand code is like a fashion designer who can't sew.
When I was holidaying overseas my credit card was left in a taxi. The taxi driver then proceeded to spend over $5000 in 3 days. I spoke to my bank and within a week the money was refunded to me. Those merchants should have had better processes to handle locals using foreign credit cards. And likewise they have the ability to work with local authorities to recoup the lost money.

These processes work every day to protect consumers. People using Bitcoin may use it once but the first time they are burned they will never use it again.
> Most people don't even talk to their neighbors, so even if you lived in a neighborhood that had a high enough density of nodes for this to work, why would you want to share a little ad-hoc network with your neighbors?

I've been thinking about this recently. The idea is that it's transparent. Imagine, for example, if Apple started shipping this on all iOS devices, or it became a common android feature. Here is a blog post I wrote on the topic last month: http://stevenjewel.com/2014/01/android-mesh/
The timing of this submission is impeccable. My 36th birthday was yesterday. Thanks for the inspiration!
Typically when you're compromised, you don't bother trying to fix the problem. You wipe the device and start over from a believed-good backup.
> The choice between "big government" and "big business" is a false dichotomy, if that's what you're getting at.

What is the third choice? Anarchy? What if I prefer not to be dragged out of my house and beaten to death by a mob?
Before launching my first product, I wrote ten articles on related subjects and put up an email sign-up form. The article were static html pages, not blog posts. They were howto's and other reference pieces that had lasting traffic value.
KUKA Robot vs. Timo Boll: The Duel
near zero transaction costs

Ignoring the sizable 3% or greater costs incurred in acquiring the currency, plus the transaction costs associated with prioritizing a transaction for processing.

irreversibility

For merchants. It's a definite killjoy for customers, and customer uptake is far more important than merchant uptake for a new currency.

anyone who sells online and had to deal with Paypal and Credit cards would tell you plenty of nightmares about frozen accounts, chargebacks and chargeback fees and rampant fraud.

Nope. The only nightmares I've heard are from people who did things wrong. Paypal and merchant services make their rules pretty clear, and they even offer assistance to merchants to figure out what they need to do. If you're having problems with Paypal or your merchant service provider, it's because you messed up.
mPesa has been around for longer, and has a bigger momentum. I don't think there's anything to get out of this besides that. Also, how many people there have at least smartphones, if not PCs, to make their Bitcoin payments? With mPesa you can do it through SMS if I'm not mistaken. So again, of course the market for mPesa is bigger right now.

I also don't think it's fair to look at Bitcoin's growth "over the past 5 years", and just conclude Bitcoin "has been flat", when it's just starting to take off now in some countries, and the fact that those regions don't have a ton of smartphones doesn't help.
Google hits space bar for Bay Area startups
James Iry’s history of programming languages (with pictures and large fonts)
Perhaps you don't want the purchase to be connected to your credit card, or perhaps the purchase is small enough for it not to matter. I've bought a few indie games with Bitcoin, admittedly mostly for the novelty, but it also turned out it was actually easier than typing in my credit card information. It also requires me to place less trust in the website; sure credit cards have much more protection, but it's still a pain if your credit card number winds up stolen.

However, when it comes to physical goods costing more than a trivial amount of money, I'd certainly want to use a credit card.
According to Satoshi, he worked on the implementation before the whitepaper. iirc he released both at the same time.
This would be pretty easy to do in games since you have all the z-buffer info already. I'm thinking of a HUD that has multiple horizontal "monitors" that show you the action. Then when things get close, they pop out of the monitors for the 3D effect. That would be awesome!
None of that explains the changes to redirect codes, which are the main point of the article. Those are what sound truly brain dead.
I guess I should out myself as a Chromium HTTP stack maintainer (since 2009, so this behavior predates me). One might consider me a domain expert here. I participate in IETF HTTPbis for the HTTP/2 work as the primary Chromium representative. I am not involved with the RFC 2616 revision work as that's tough, thankless work, that thank god we have Julian Reschke and Roy Fielding working on. As far as I'm concerned, I owe them a drink everytime I see them. They do an awful lot of legwork talking to various implementations and trying to build consensus on actually conforming with the standard and all its edge cases. It's really quite unfortunate to see this blog post author treat them so unfairly, although I can see how one might easily jump to his conclusion.

Now, as far as "SHOULD NOT", that's a reasonable thought for people not aware of what popular user agents currently do. The thing is, the majority of major browsers rewrite POST to GET on a 301. Here's my browser's code for it: https://code.google.com/p/chromium/codesearch#chromium/src/n.... Here's Firefox's code for it: http://mxr.mozilla.org/mozilla-central/source/netwerk/protoc.... To my knowledge, all browsers implement this behavior. We basically copied IE's behavior, because, IE did it and websites expected all user agents to do what IE did. Story of the web, sound familiar? :P

So, as you can see, Julian was merely acknowledging the pragmatic reality of the situation when he updated the httpbis specs to reflect this behavior: http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1428. And this reasoning behind it is covered in the introduction to the relevant section in the httpbis docs: http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-2....

"SHOULD NOT" implies that our implementations are behaving badly. Now, it's true, our implementations may not be behaving ideally from a spec cleanliness point of view, but interop trumps spec cleanliness, at least from the perspective of anyone who actually deploys real software on the internet. So it's probably best for the spec to acknowledge this and officially allow this. Specs that don't mirror reality are...probably not just useless, but actively harmful.

I hope that explains things, cheers.
MIT materialsproject.org
Fraud and theft is much more rampant in the BTC universe. By now there have been dozens of large-scale thefts when services were compromised. And unlike with established payment solutions it is next to impossible to get your money back if it happens.

As a consumer it is also impossible to pay with BTC ad hoc unless you already own some and thus expose yourself to its volatility. Of course I could see something that I want to buy, then log onto a BTC exchange (which requires me to already have an account) and buy enough BTC to then pay with those BTC. But why would I subject myself to that additional effort for no practical benefits for myself?
Analysis of the CoinThief/A malware
Yes, that's why I mentioned Tumblr in particular. Tumblr is an example of a website where people write HTML, yet don't control the HTML that displays to others.

On sites where you control the HTML, like Wordpress, you can do whatever you like. Use <video> tags if you know them. Likewise, on sites where you don't write HTML (e.g. Facebook, as another poster mentioned), <video> tags are fine--because people don't have to know about them, so it's all just handled in the background when you drop a video on the page.

But there are these in-between web services where HTML is used, usually as one method of several, to get rich text from people, and then presented in an aggregate view (think of any traditional threaded forum.)

Because people can do some pretty nasty things when you inject their HTML directly into your pages, you have to filter that HTML to remove bad behavior. And usually <video> is one of the first to go--not because it's particularly bad (though getting people to autoload huge videos can be used as a DDoS attack in some instances) but because these filters are usually whitelist-based, and haven't been updated since <video> became a thing.
That's an excellent point. Adverse selection is a real problem because some people can have a very good idea of what their bills will be. If it's cheaper to pay out of pocket they'll do so, but if they could save money by buying insurance they would do so.

Another part of that problem is that the price is all wrong. People who have very little risk of dying regularly buy health insurance in part because the premiums are so reasonable. $200 a year (or whatever it costs) is such a small amount of money for so, so many people that you're a fool not to buy it if you have dependents.

If you could pay the actual market rate at the doctor's office -- the rate the insurance companies get -- you could afford most medical problems out of pocket. I mean it's demonstrably true, the insurance companies don't pay out more than everyone pays in so by default we can all afford to pay for healthcare. What we can't all afford to do is pay $50k for big procedure X or $200k for cancer treatment Y. But those are major medical type issues which we can insure for not horrific amounts of money.

The adverse selection problem can be solved in large part by having affordable major medical that makes you an idiot not to take it. I can totally understand why single people in their 20s aren't keen on shelling out $450 a month for insurance. But $20-$50 a month? That's less than car insurance or a cell phone or cable. Save $400 a month on insurance and you could afford to get ACL surgery every couple of years!

But here's the thing: if you want to buy your own insurance you can't 1) because of the adverse selection issue and 2) because an already high price would get about 30% higher as you get taxed on that money.
> BSD is a de-facto more permissive license.

Just saying something like this seems slightly dishonest. It's more permissive for the first receiver of the code, but that therefore means that they are permitted to reduce the persmissions of subsequent receivers of the code.

So 'more permissive' in a sense yes, but not in the sense that the FSF care about - the freedoms that the end user is guaranteed. It's quite possible that the end user is ultimately granted fewer permissions because code was licensed BSD rather than GPL.
There's this: http://www.cs.uiuc.edu/homes/dhoiem/projects/popup/index.htm...
Creatables
Interactive Map of the Universe [Flash]
This is the equivalent of implementing the design in Flash :)
Ask HN: Good examples of screenshot style product tours
I'm diligently working away on the sales page for my SaaS startup. Just reading thought the comments for ding.io the first comment was this https://news.ycombinator.com/item?id=7246312

Its a good idea and something id like to do for sure. I'd like to see some exemplary examples of successfully showing off your product using screenshots.

Who can suggest some?
The system already ignores most of the commands due to how the game works. Essentially, it picks a move at random every frames or so. And if you look at the live stats of the voting, you can see that the people tend to vote in a single direction at a time already: https://sheltered-reef-4687.herokuapp.com/

I think that the long stream delay is a bigger problem then the randomness. People tend to vote according to what the stream is currently showing but the votes will actually be counted 20 to 40 seconds in the future.
The article actually makes pretty good suggestions despite coming off as a little arrogant (our design tweaks will make a world of difference, if only the developers could understand!). I think the key is to realize that the visual design work comes last. Moving things by a few pixels here or there is not going to make or break your product, because the purpose of your product is to provide some sort of useful functionality and not just to look pretty (presumably). And a lot of times it's completely subjective anyway. Get the approximate layout and user interactions nailed down first, ignoring any superficial flaws. Then, at the very end, I don't think the developer will mind if you ask him or her to make one pass of tweaking a bunch of colors and alignments.
I wish your taxi driver good luck spending stolen Bitcoins without the owner's private key. The fact that your credit card worked for 3 days for $5000 in unauthorized transactions is a bug, not a feature.
4-5% transaction cost (http://blockchain.info/charts/cost-per-transaction-percent) is certainly not "near zero", and in many cases is higher than credit card transaction costs.

just because the current transaction costs are paid with freshly printed money does not mean they dont exist, and as the rate of minting goes down as we near 2080, those transaction costs are going to start coming more and more from the users instead of the mines.
Agreed -- this is what I signed in to post. I have been waiting for a long time, with growing frustration, for Bitcoin's transaction rate to start taking off[1]. For several years, the transaction rate was near flat. But look at it now! Clearly, people are using Bitcoin for to buy and sell.

In fact, my thesis is that increased use of Bitcoin as a currency is partly what is driving down the price. Most of the highest-volume Bitcoin-accepting vendors (Overstock, Gyft, Tiger Direct, etc.) change their Bitcoins immediately to USD, which creates significant selling pressure.

1. If anyone is wondering why the most popular addresses are excluded, it's because those addresses are almost invariably the exchanges, and so they skew the data upward.
ChefAPI – A dependency-minimal Ruby HTTP client for a Chef Server
Totally agree. The best part of working with my wife is knowing that she's always looking out for my best interests (and vice versa). The absolute trust is a huge relief.
Thanks for the kind words! And yes, the article was meant to address picking key hires, whether your spouse (main focus of article) or any other person who would play a major role in your business.
Truly wonderful post. Curious though, could something like this be replicated with HTML5 and JS?
There's a pretty cool Vidsauce video on this. The most popular version of the map that causes this misperception also causes Greenland to look much, much larger than it really is.
Drawing outside the panel is a standard method in comics when you want to add extra impact or a 3d effect to a panel.

For example: http://siguealconejoblanco.es/comics/wp-content/uploads/2013...
Interesting…

Note that they also add sha256 specific instructions. Which is good, because sha1 should no longer be used for new application and existing application should definitely start looking into an update path. See [1] for a rough estimate how fast the existing (publicly known) attacks become feasible.

I hope they are also working on implementing the sha3 permutation. That would allow for some really cool features to be super fast and simple like authenticated encryption or reseedable pseudo random number generation[2].

[1] https://www.schneier.com/blog/archives/2012/10/when_will_we_...
[2] For details see section 5 and 6 of https://eprint.iacr.org/2011/499.pdf