skysight-inc/HackerNews huggingface dataset:
Being able to keep your keys in your pocket/purse/etc when entering and driving a car I find to be a pretty big upside. Especially in areas where it can be cold enough to freeze the key mechanism on your car door.
5 Emerging Tech Hubs from Around the World
What was your motivation for handling things this way?
I spent a long time at a boutique consultancy that specialized in rescuing at-risk software projects for fortune 100 firms. Mainly, that meant we got very, very good at building up waterfall adapters for our internal processes.

I won't say we were following agile, exactly, but the concept remains approximately the same. Big company management thrives on the mistaken notion that they can plan out the world years in advance. The key insights that made our adapters work were 1) no one has enough of a memory to hold anyone to those plans even six months down the line and 2) no one expects anything to work anyway, since they're all used to their plans falling over.

Which isn't to say this is going to work. I suspect that, like all things recent IBM, any success they find will be more attributable to inertia than execution excellence.

edit: clarification
Because management doesn't want them to be true.
Congratulations on getting rid of your last AIX box. I wish I could :|
Well for the example timing I gave you only need 1 part per thousand accuracy, and it's easy to get 10ppm or much better. It only needs to run during communication, anyway.
Tagged unions in particular, C's version of variant types. An enum can be considered a degenerate case of such a type, so the naming isn't totally arbitrary.
It's very true that most people wouldn't choose that life, but that's kind of what the author seems to be saying. I personally think that anything that makes you feel alive, even if it doesn't last forever, is the best way to go. Congrats to you, author
Please elaborate as to how the fob or car would detect the MITM:

1. You place device A near car and device B near fob.
2. Device A relays all Rf transmissions in the target frequency range(s) to device B, which rebroadcasts, and vice versa.

Public-key encryption / authentication only ensures that no-one in the middle is reading or editing your connection. It does not prevent someone from relaying your communication. (And a good thing too, else the entire encrypted web wouldn't work.)
Third Patient Receives Artificial Heart
Yep - here's a presentation on these relay/repeater attacks by some researchers who actually build some: http://media.hacking-lab.com/scs3/scs3_pdf/SCS3_2011_Capkun....
Open Source at Facebook
I had the same problem with other projects like that before. We were lucky on finding older builds in some Linux distribution repo. Maybe you can also try looking in Suse's or Debian's repos for them. Another, often used alternative is automatically building an open source project for yourself. Especially if you find that new versions build your system on a regular basis. Building it yourself is the first step to get involved in the release process.
> But do you eat fast food? In the fast food world, Chipotle is pretty high up on the "brand perception" scale.

Chipotle aims for a fast casual ambiance (which can be a reason to prefer it), but to me the food quality seems to be between lower-end fast-food places like Taco Bell and better fast-food places like El Pollo Loco.
Well is your goal to bring your product to market or to get into YC? Doesn't have to be the end all be all.
I'm sure it just comes down to personal preference, but as a node developer myself (perhaps former), i found it so freeing to switch to Go. Mainly for two reasons (which i assume are less common reasons):

1. Synchronous by default
2. Interfaces

Point 1 to me feels silly to admit. But man, i still do a fair bit of JavaScript/Node for work (our frontend, mainly) and it is just so.. tiresome to me, to constantly feel on the edge of bugs because some functions are expected to be synchronous (return values) and others are intended to callback.

I'm not even talking "nested-hell", i'm simply referring to the mental overhead that i apparently use when using any JavaScript function. It's not difficult.. it's just not enjoyable. It's.. tiresome for me.

Point 2 is simply because i really like interfaces. Back from my Python days, a few libraries had invented ways to support interfaces and i really really liked them, but not the overhead they required. Being able to expect the behavior of an object with certainty is the main part of duck-typing to me, and seeing that from a more static language (when compared to python/js) is really enjoyable.

I know you didn't ask for a writeup, i just had to agree with you and felt the need to share my experience from a similar standpoint. :)
Reprogramming Women's Work: Glorious Ladynerds and the Dudes Who Steal Their Jobs
In fairness, "Try on Hipster Desktop" is an awful lot of text to fit onto a button.
Armadillo Aerospace's core team members are on Kickstarter for Sub-Orbital Space
Thanks!

I wish I'd known this a week ago, but I'll keep it in mind for the next time I'm poking at Go :)
Valve are people and people make mistakes. With that said, lets make sure that we pay attention to how FEW mistakes they make.
First proton collisions at Large Hadron Collider should start in early June
It's pretty darn hard to make a derivative work without understanding the source material. I suspect your immediate dismissal of this analogy is more related to your strong personal greed for entertainment, which appears to be a fundamental human feature.

One wonders how that could have evolved. Someone should do experiments where they deny access to three company episodes to chimps, to see if they freak out as badly as the internet generation does when they can't get their favorite things.
Drones and dogs deployed in battle to save the guacamole
Rust's enums aren't like Java enums, they are algebraic datatypes and each variant can hold different data. Check out the example with DrawTriangle and whatnot for what I mean :)
You no longer have to code certain features into your API and can let Kong handle it for you :)

Saving you time and money!

Some features: http://getkong.org/plugins/
Looks interesting. There is definitely a need for something secure to manage secrets easily & efficiently.

I'm not super familiar with Shamir's secret sharing. The post says that the master key is split up across a number of people. One thing that I am confused about is if Vault goes down (possibly in the middle of the night), does it require a quorum of humans to boot it back up?
It's actually just an issue with Docker.

Container technology (and the Linux namespaces behind it) support the ability to run containers as non-root by translating the user with a namespace.
The timer could be in the car. Protocol looks like fob pings car, car challenges fob, fob responds.
Interesting, thanks. Im going to give it a try.
I think a big point in each of the articles is that design is being devalued by lots of conspiring factors. These sorts of tools are positioned as suitable replacements for a real designer. Square space did issue and update stating they don't think that's the case, but still, it's a sleek presentation and people could be forgiven for thinking otherwise.
Blendle: A radical experiment with micropayments in journalism, 365 days later
Wouldn't say they are in denial about the issue. Wish I had some better sources, but if I recall the automotive industry has always had issues with security regarding keys and ignitions. My 99 Prizm key would work for most all other Chevy Prizm cars. I know that this "cross keying" would work on quite a few different brands and models as well. Some ignitions can be "popped" and screwdrivers used to start the ignition. My point being that security of starting an automobile or accessing one has been plagues with problems. Break the window etc. Some manufacturers do require the key fob to be present while the motor is running in some cases the feul pump will shut off if the key is not present. It is highly likely that the Tesla demo is for opening the CAN exploitability issue to the convention. Attacks on the CAN remotely are much more serious.
A lot of things will reflect RF in weird ways, and that is precisely what I was counting on. Surely an amplifier that changes the detection range from 1 feet to 100 feet will be emitting much much higher energy than what is usually experienced under normal operation. I guess, the antenna does not have to be omnidirectional as long as the attacker can search around the direction the key is likely to be.
So, they just want low-quality software? The market happily addresses this desire :-\
Work in Estonia – Your guide to living and working in Estonia
SanDisk's new PCIe application accelerators arrive
i think the main advantage that reddit has over HN is the combination of breadth and specificity. there aren't any categories or labels in HN and, as has already been discussed, people generally only see the front page. this leads to the "social echo chamber" effect that people have discussed elsewhere, meaning a lot of people read/respond to the same ideas over and over leading to an incestuous breeding ground for thought/commentary.

i prefer to create my own multireddits for content technical content i'm interested in discussing. one for languages, open source, web, mobile, or computer science theory. these would be impossible to find on HN but on reddit they often attract more serious comments (not perfect).

also, did you ask this same question on reddit? i'm wary of the implicit selection bias in asking for a comparison from HN users and not reddit. the users on HN who take the time to read and respond to something like this are more than likely to prefer HN to reddit.
Oh. I see this today nice. I always liked HashiCorp folks.

https://hashicorp.com/blog/vault.html
you would use both.

Django REST Framework (or any other framework) to build your business logic and API services.

Kong is useful to scale and manage acceess to the API for API consumers (as oppose to end users) as well as a plugin system that abstracts HTTP tooling away from your API application, so you can scale them independently.
The nice thing about Go is that you rarely have to think about memory management. Can you access the object? Then it exists! (even across threads)

You should use locks for thread safety though.

That being said from a Rust background I like to be able to know what's going on at the lower level and Go makes that harder, but that's not a major issue whilst programming.
In general what would you support and (very important why): Someone who focusses on a clean architecture even if it means slower development and less features, or someone who will integrate nearly everything even if it means the code base, build process etc are a mess?

My feeling always says the first, but all my successes (which I define as "someone was getting his job done using my open source tool") came from the latter. So I wonder if my sample size is simply too small, or if I was too naive in the first place, thinking clean architecture is good and important.
I hope so, but no one except systemd is using it yet. Last time I checked the sd-bus.h header isn't installed with systemd yet due to the systemd folks concern that that API for sd-bus wasn't finalized yet.

It would be very interesting to benchmark it against the glib implementation (which most people, even if they aren't using glib directly, are using these days).
Fixed link:

http://www.agner.org/optimize/instruction_tables.pdf
I want a bracelet to replace my phone and pebble.
The article points out that the Windows 10 icons really suck. They don't even look like they belong to the same family. They suck so badly that Iconfactory, which designed some previous Windows icons, issued a public denial that they had anything to do with the Windows 10 icons.

Maybe the next trend will be to get rid of icons and go back to words. Expecting people to learn a new pictographic language for each new product is not working. See the article linked here, and look at the icons in row 1, column 3, row 2, column 1, and row 2, column 3. Any idea what those mean? On touch devices, mousing over an icon to get a popup that tells you what it means no longer works. The user has to know.

There's an SF book by William Gibson, "Idoru", where one of the lead characters carries an icon dictionary around with her.
Play Typed Actions
The T-shirt to wear on code review days.

http://www.redbubble.com/people/ramiro/works/13306366-im-a-v...
The drawback is if you left your keys on the bench in the garage next to your car. You get in, push the button to start, then drive off. Now you can't get back home. At least with the physical key you are guaranteed to have it with you.

The other thing -- do the key fobs have an on/off switch? If not, you wouldn't be able to have a spare "hidden" under your car somewhere (yes this is insecure anyway, but it works for most people).
Jenkins Environment Variable Templating
Why Push Notifications Used Correctly Dominate Email Marketing
11 Tips for Solo Female Travellers
Except with the iPhone, which couldn't run native apps when it was launched.
One thing that might highlight the value here is to use a reduced set of effects. Here's (in Haskell, sorry) the "teletype monad"

-- set of commands
data Teletype = Write String x | Read (String -> x) deriving Functor

-- monadic data structure
data TeletypeM a = Pure a | Effect (Teletype (TeletypeM a))

-- monad instance
instance Monad TeletypeM where
return = Pure
m >>= k = case m of
Pure a -> k a
Effect tt -> Effect (fmap (>>= k) tt)

-- API
write :: String -> TeletypeM ()
write s = Effect (Write s ())

read :: TeletypeM String
read = Effect (Read (\s -> s))

Now using this we can write "effectful" teletype programs. For instance, the "echo doubler"

echoTwice :: TeletypeM ()
echoTwice = forever $ do
line <- read
write line
write line

Finally, we can "interpret this into IO", which is to say give it a side-effecting semantics

runTeletypeMIO :: TeletypeM a -> IO a
runTeletypeMIO m = case m of
Pure a -> return a
Effect e -> case e of
Write s next -> do
putStrLn s
runTeletypeMIO next

Read cont -> do
line <- readLine
let next = cont line
runTeletypeMIO next

This is nice and feels a lot like "pushing the toothpaste around", but we can take advantage of its pure structure for other purposes. For instance, here's a delimited interpreter which only allows it to take a certain number of "steps"

runTTDelimited :: Int -> TeletypeM () -> IO ()
runTTDelimited n m
| n <= 0 = return ()
| otherwise = case m of
Pure a -> return a
Effect e -> case e of
Write s next -> do
putStrLn s
runTTDelimited (n-1) next

Read cont -> do
line <- readLine
let next = cont line
runTTDelimited (n-1) next

And here's a completely pure interpreter version of the above which also takes its input from a pre-arranged "script"

runTTPure :: Int -> TeletypeM () -> ([String] -> [String])
runTTPure n m input = reverse (go n m input []) where
go n m input acc
| n <= 0 = acc
| otherwise = case m of
Pure a -> acc
Effect e -> case e of
Write s next -> go (n-1) next input (s : acc)
Read cont -> case input of
[] -> error "ran out of input"
(s : ss) -> go (n-1) (cont s) ss acc

All of these can work off of the same TeletypeM values.
3 machines in 2U looks like the way to go. I don't need that kind of compute capacity but it's good to know someone is spearheading that initiative.
What happens when I drive more than 100m away? Does the car rely on the key being "close enough" to keep the engine powered?
Wikidata Meets the Google Knowledge Graph
Also, it was Microsoft that targeted Android with patents on things such as FAT32. If you sue me, all gentlemanly agreements are off the table.

Essential patent is a loaded term. I argue all non-trivial patents are essential. If a software patent isn't standard-essential (I'd argue standard is yet another loaded term because FAT32 is a de facto standard for interoperability) it should not be a patent at all. I think you'll agree.
Yes. Like that's gonna happen.
In fact it does.

http://stackoverflow.com/questions/19499618/gcc-printf-optim...
How many optical pulse oximeters don't work on people with tattoos on their wrists.

The watch works fine.
> That said I wonder why they named it enum.

Because it's a type-safe enumeration? ADTs are pretty much a superset of C-style enums, an ADT with all-dataless constructors is equivalent to a C enum:

enum Foo { Bar, Baz, Qux, Quux }

And members can converted to integrals:

> println!("{}", Foo::Qux as u8);
2

With explicit integrals very much like C:

> enum Foo { Bar = 5, Baz, Qux, Quux }
> println!("{}", Foo::Qux as u8);
7

Calling it "enum" makes it familiar to C developers[0], "union" would have been confusing for the same (as you can't just write one representation and read the other) and "type" is a tad too generic (and used for type aliases à la typedef).

[0] even more so C++ developers as they have `enum class` which is also type-safe and not implicitly converted to integrals
It's interesting reading this about a car maker, when I work for a home device maker and fight tooth and nail to open up API control of home security/thermostats.

People find a way in either way, whether you want them to or not.
I doubt this will really work for really big acts. But, I think it might for the local/indie/whatever-you-call it scene. I don't think taste is an issue if there's enough variety. You don't have to go to shows you don't like.

The real power of stuff like this is in dynamic effects. Can a band get Jukely-famous? Can you find shows you wouldn't have seen but are glad you did?

It might be worth looking into again in 6 months.
I don't think it's that funny anymore. It's funny until you realize lots of readers believe him.

If you want to roll the discussion up to the original claim on this thread:

* Yes, closed-source vendors, Google included, do not as a rule announce severe flaws they find (or contract to find) in their own code. On the other hand, when we're talking about Google, Microsoft, and Apple: they are actually finding sophisticated flaws in their own product, which is something very few open source projects can credibly claim.

* Open source projects are not as a rule particularly awesome about handling disclosures either. See, for instance, AFNetworking.

* Nobody made logos for HTTP.sys (that I know of). On the other hand, HTTP.sys was a bigger deal in the industry than POODLE or pretty much any other vuln with a name besides Heartbleed, which, because it implicated a library used by lots of products, was particularly prevalent among Internet SAAS sites, and was easier to quietly exploit than an RCE, was a legitimately more important flaw. The idea that Microsoft gets a free pass for vulns is something you can only believe if your only contact with them is HN.

* There's no evidence Microsoft hid those vulnerabilities. They were there for 10+ years because nobody found them. In Microsoft's case, you can't reasonably claim that's because they weren't looking. Minesweeper gets more pentesting effort at Microsoft than most open source crypto projects.

I strongly prefer open source software to closed-source software, but I'm not unrealistic about how open source security works. See security tire fires such as: OpenSSL, Rails, PHP, Cryptocat, BIND --- each distinctive not just for having vulns but for the manner in which they've historically handled them.
Thanks for the comment. Our goal is to succeed in the Linkedin/Facebook sense of the word (excuse our enthusiasm, but if not this, we would self fund and be content with organic growth). But I don't want to dismiss their wisdom, as we could be spending our next year building something that will eventually amount to a semi-success/failure, and face a much more difficult pivot.
What's New in SSL Labs 1.16.x
Why?

I mean, Blinky is the "Hello World" of embedded software. When was the last time a hello world aroused you? The point of this is not the blinky, it's the "omg erlang vm on raspberry pi".
What certainly helps:

* Having small, self-contained, loosely-coupled modules.

* Having an extensive test suite for each module.

* Having small (or zero) amount of technical debt.

* Talking to your customers constantly, preferably before you commit a lot of resources into a new development.

Easier said than done, but definitely not impossible.
As Riots Follow Freddie Gray's Death in Baltimore, Calls for Calm Ring Hollow
This is a great series of articles, although I may be biased because I agree with almost everything I've read so far.

On the flip side though, I think one could argue that this is the rise of the designer/developer, rare as they might be. The flatness trend has created a world in which truly outstanding design can shine against a back drop of blandness. Designer/developers have way more of an edge than ever before.
I also find it interesting, that as far as I can tell, the only pricing info on their main product is that it is more expensive than $500 (the high point to which they were advised to drop the price for CPPCAT).

I suppose it's fine to only cater to a high market from a business perspective, but I'd much rather just have them list the price at some high-point they usually charge (eg: 3000$/developer/year ?) with an added caveat of "contact us to negotiate a better price".

Why would I spend hours evaluating a tool I have no idea what costs? I also really can't stand the pricing model of pay-as-much-as-you-can -- then again, I don't use Oracle either.

Not that it really matters -- currently I'm not their target demographic anyway.
Many charitable organizations are rated (by % of dollar donated that makes it to the actual cause) by independent organizations.

At least for bigger outfits, it's easy to find out how your money is spent.
Why TPP on IP law is better than you think
Sounds like in your case, they want customers locked in to their products
In light of the recent hostile takeover of nagiosplugins by nagios from the monitoringplugins folks, it puts the Nagios guy's statements that amount to "they just didn't want to work with us" in a very different light.
Sorry! Thanks for letting me know. I've updated the blog. Right now it's Mac only because Kitematic runs on Mac right now, but we are working hard on delivering a Windows version soon :)
Yes, otherwise - when keys travel with secrets - there would be absolutely no security.

This is akin to disk encryption where you have to type password on boot, but then data is accessible later.
Git Large File Storage
Fixing a slow Rails development server
Haven't tried it yet, but most likely yes. But if you actually need vault and do spread the key to more than 2 people, you likely have more than one vault server running at a time.
The unused imports thing seems to be a common complaint, however I just use go-imports, and imports are added/removed automatically when I save the file.

I never ever have to even touch imports, except sometimes when two different packages have the same name.
You're also missing that Android Wear gained wifi support in the last update - without the phone, you just have to connect to a wifi network (not the same network as the phone necessarily) and you have full functionality again.
Ultimate ultralight travel packing list