navitronic

A modern alternative to the pizza delivery message would be to use uber to book a car near the location and upon the allocation of the driver, contact them and ask them to deliver the message.

and then drive around the block a few times for their trouble.

edit: My mistake, forgot that it wasn't as wide.

I would love to be able to hook one of these panels up to a Mac and use it as a retina display (1024x768) for testing desktop retina usage.

The 5's size was to maintain the 326ppi of the display and ensure a smooth transition for developers. A 3.5 and a 5 inch screen would have made app developers have to create 2 separate layouts, whereas this approach means that developers 2 similar layouts for 4-class phones (3:2) and 5-class phones (16:9), which should ideally mean less work for the developers

It's the combination of the three factors causing the issue.

Not a huge fan of their blog's redesign.

The combination of the serif font, text-indent on paragraphs and lack of separation between them makes reading it a chore. One of the first times I have needed to use Safari's reader mode out of necessity.

Seeing as an aside/light hearted post like this makes it onto the HN front page, I'd say its a reasonable deal for the advertiser in terms of eyeballs/brand awareness, even if the HN audience is not their intended audience.

I was always under the impression that the main point of salting a password before hashing (unique or not, stored in cleartext or otherwise) was to prevent the hash from being referenced against a rainbow table of precomputed hashes. Obviously this is in the case of using md5/sha1 for your hashing.

As an example, find the md5 of a dictionary word and google it, its original value is bound to be in the first or second result. Now find the md5 of that word and a random string (aka a salt)... google and there shouldn't be any results. and even if there was due to a collision, that password wouldn't work, because it would be resalted prior to the comparison happening.

I should clarify, I mean terribly formatted.

Also works great for displaying JSON in a consistent way, useful for visualising and understanding object hierarchies.

I think, and I might be going out on a limb here... that it was a joke.

Would be interesting to see what percentage of users have updated to version 3.0. Eg, 100,000 clients have hit the server in the last two weeks and 65,000 had 3.0

Love the product though and enjoy these kinds of tidbits of info.