skysight-inc/HackerNews huggingface dataset:
Did they also sign a paying contract with you? That's the best of all :).

I agree with you that you can't just break things when you're working with financial firms. That doesn't mean you have to artificially constrain growth. It's probably a matter of degree, and I don't have a good enough sense of where you sit to have a more informed opinion.

How are you actually constraining yourself? Are you keeping out users who want in? Are you limiting the number of companies to whom you are trying to sell?
This is neat! Threw together an Ansible role for it:

https://github.com/duggan/ansible-slack-notify-ssh
A charitable interpretation of the sentence you quoted is your ending sentence.
WW3+TURKS+KILLING+CIVIES+WITH+TANKS,VIEWER+DESRCETION+ADVISED+-+YouTube
That's a hazmat suit. And given the nature of the jet fuel, the paints, and metals involved in aircraft components, you'd probably want to wear something similar when wading through the crash site until it was cleared.
We’re building the first in its kind ads/promotion barter platform: http://appstore.com/postforpostforinstagram
it allows you to find peers in social networks and exchange shoutouts, e.g. promote each other on Instagram, so that both participants of the deal get additional followers for free, and grow together.

It is known as #sfs #s4s #shareforshare, over 150m associated hashtags accross major apps. It is especially popular among professional and millenial influencers in the low/mid segments (e.g. 1K-100K IG followers). Due to sfs’ viral nature, our influencer base turned out to grow a lot faster than traditional influencer/brand marketplaces – this could make us a lot bigger and better place to buy/sell influencer ads than all these 120+ identical marketplaces in the list: https://angel.co/influencer-marketing-2

The influencer ads are like the hottest advertising trend of the upcoming years :) We see we’re up to something great here and start thinking how we get the biggest piece of the pie in the long term. In order to sustain this product strategy competition-wise we’ve even submitted Patent App for the concept 'Advertising Barter in Social Networks'.

…though what’d be a lot more interesting, I just realized an hour ago:
rather than compete with all of them, try to create interface layer – build API for them, etc. I would like to discuss this – would be great to hear your recommendations/roadmap thoughts mb, other than ‘getting big enough first’
I think Bryan Cantrill and Joyent are doing a number of interesting things, but this reads more like an ad than a genuine critique of Unikernels.

The primary reason to implement functionality in the
operating system kernel is for performance: by avoiding
a context switch across the user-kernel boundary,
operations that rely upon transit across that boundary
can be made faster.

I haven't heard this argument made once. There are performance benefits (smaller footprint, compiler optimization across system call boundaries, etc...). However, the primary benefit is not performance from eliminating the user/kernel boundary.

Should you have apps that can be unikernel-borne, you
arrive at the most profound reason that unikernels are
unfit for production — and the reason that (to me,
anyway) strikes unikernels through the heart when it
comes to deploying anything real in production:
Unikernels are entirely undebuggable.

If this were true, and an issue, FPGAs would also be completely unusable in production.
Well since we started with the pilots I’ll go there first. They progressed very quickly at first. One meeting turned into three which turned into 5 more and then we actually got wireframes and mockups made. And then everything seems to go into super slow-mo.

When that happened with one bank we used the first relationship to leverage into a second one with another large bank, after going through a near identical process we realized that big banks all move much slower than we can (even the ones that claim they can move very quickly).

At that point we started pursuing relationships with smaller banks and those seem to be significantly faster albeit still very slow in comparison to a startup.

The most recent revelation with the bill pay stuff has literally been over the course of the last 7-10 days because we threw out what we thought was a hairbrain idea to buy a small bank to an investor we knew well.

He got excited and offered to fund the entire deal if we could find one that we thought could work well.

That kind of kicked ideas into hyperdrive about what we could build to attract users now instead of waiting, and the tool to identify bills within emails was thought up and began progress on just so us and some of our friends can try it.

It’s not a launched product yet, but its close to something we could stick in the chrome store as an extension and see the feedback we get.
From the page:

"This technique is an alternative to weak linking,..."
Open source project with 2 PMs? That sounds very weird to me. In my mind that open source projects should be driven by community.
You got a user here, definitely need something like this.
No, we're talking about running things under unikernels.

I mean yes, you could have some of your app implemented in OCaml and then it talks over TCP to some Fortran running on Linux to do linear algebra, but that approach has its own problems.
I wouldn't call that "C-style code". Namespaces are a C++-specific feature, and inline namespaces were introduced in C++-11. C has never had either feature.
Some additional images of gun owners at home:

http://img.foodnetwork.com/FOOD/2011/12/29/HE_family-meal_s4...

http://cdn.sheknows.com/articles/2012/12/family-eating-a-chr...

http://www.blackmensdossier.com/sites/default/files/styles/l...

http://footage.framepool.com/shotimg/qf/884079511-planting-i...

Disturbing, to be sure. But humanizing as well.
This cheatsheet is wrong about ES2015 modules. They don't define how module loading works, that's still being worked on [0]. ES2015 just defined the syntax.

[0] https://github.com/whatwg/loader
No. It is memory dangerous. Please use appropriate personal protective equipment when using this, or you may find you have lost all memory of your family.

More seriously: no, it makes no guarantees, but it tends to a much safer style by default: Bounds are checked, raw pointer arithmetic is ugly, clunky, and rarely used (although useful within, eg, the memory allocator), implicit conversions are gone, and null pointers aren't present in either the language or the library. You can define your own, even in a generic manner, but nothing uses this ability. Uninitialized variables are generally a compile time error (barring some bugs in the data flow analsyis), and so on. You can poke holes in the type system, but these holes are explicit.

As a result, most code written is going to be far safer than, say, C.
>IMO the entire goal of encryption tech should be to make the government incur significant costs for every invasion of privacy

The entire goal of encryption is to preserve the consent of whomever is using it. Two people wish to speak privately and don't consent to eavesdropping. Unfortunately, due to engineering realities, only the next best thing is for eavesdroppers to incur linearized costs to violate that consent. In effect this is theft of communication / information.
Superconductors exhibit superconductivity in temperature of 30K and less.

High-temperature superconductors exhibit that effect in temperature 90-130K.

Having all that, 200K is really close to room temperature.

https://en.wikipedia.org/wiki/High-temperature_superconducti...
Cool. Is your transaction volume growing at the same rate?
Some of the original "unikernel in a shared environment" research and development was done on IBM's VM system in the 70's. Their motivation was that there were many customers who used a dedicated application on what was then a mainframe to process their data (this would be analogous to their unikernel) and they wanted to consolidate their hardware, so they got a bigger mainframe (like an IBM 370 at the time) and they would run all of these dedicated applications in their own logical partition (LPAR). It brought three huge benefits to the table (error containment, hardware consolidation, and backward compatibility). Because IBM had experienced the same effect that we're seeing today, their new mainframes in the 70's were so much more powerful than the ones from the 50's and 60's, and for them what was worse the ones from the 50's and 60's running their dedicated apps were still fine. So they developed a way to make computing more cost effective for their customer and at the same time opened the market further for their mainframes.

Today, a typical dual core 8GB x86 machine can, as a dedicated machine run a lot of things. At the same time the evolution of open systems have brought "continuous configuration integration" into the mainstream, all major OSs from OS X to Windows to Linux have weekly, sometimes daily, reconfiguration events.

And while the number of the changes in aggregate are high, the number of changes on particular subsystems are low. Unikernels answer the need of creating a stable enough snapshot of the world to allow for better configuration management. Look at the example of the FreeBSD system taken down after 20 years. Some services can just run and run and run.

Image isolation is a thing, and you can only be as good as your underlying software and hardware can make you, but it can also be a big boost to operational efficiency if that can simplify your security auditing and maintenance.

So my take on Bryan's article was that he came at the argument from one direction, which is fine, but to be more through it would help to look at it from several directions. What was worse was that he made some assertions (like never being in production) before defining precisely what he means by a Unikernel which leaves him wide open to examples like NetApp and IBM's VM system to counter his assertion.

The nice thing about computers these days is that many of the problems we experience have been experienced in different ways and solved in different ways already, and we can learn from those. The Unikernel discussion is not complete with looking through the history of machines which are dedicated appliances (from Routers, to Filers, to Switches, to Security camera archivers)

Like most things, I don't think unikernels are a panacea but they also aren't the end of the world and have been applied in the past with great success.
Referrer spamming is significantly else effort than this, and the validation of the target link in the source does provide a higher barrier. Parsing for microformats from the source also gives more structure to validate heuristically. Eventually a whitelist model will make more sense; the 'vouch' extension gives a way to construct one which puts more burden on the spammer than the receiver.
The court ruling can be found at http://www.canlii.org/en/on/oncj/doc/2016/2016oncj35/2016onc... -- I submitted the news story because it's rather more readable than the source judgment.

I find this case interesting because it shows some of the challenges courts run into when dealing with digital and online evidence; for example:

At one point during the testimony of Ms. Reilly, Crown counsel
tried to open the link to one of the tweets on the disk and could
not because Ms. Reilly had locked her account and made it private
the day before she testified. Therefore the Crown, the police, the
Court and the defendant could only see a screen that said, “Sorry:
you’re not authorized to see the status.” Ms. Reilly unlocked her
account and the trial continued.
The lowest natural temperature ever directly recorded at ground level on Earth is −89.2 °C. (Google, copy-paste). So we're now talking about superconductors that could exist in certain conditions on the earth without human intervention. That's pretty amazing.

Now we just need to figure out how to make it work somewhere a bit warmer.
Might want to start writing the book on the 2016 unicorn dehornification, since it seems the powers that be are pretty determined to make it happen (or at least getting all the media outlets to make people think it's about to happen).
I wish the creator would maintain a blog about the project. It is cool to follow him on twitter and watch him work out the technical details of new features (e.g. marching cubes based mesh extraction). There is some definite interesting technical meat in implementing these tools in the context of a voxel engine.
Go would show channels. Rust would show the prevention of a memory ownership bug. Elm would show reactivity. Haskell would show that a monad is just a monoid in the category of endofunctors. what's the problem?

If you haven't got something interesting and at least unusual to show off very early in your docs, it's something to think about in your language design.

Now, you may have to build up a bit, and I'd certainly say you shouldn't bend your entire language around the "one cool demo", but I do think your early docs should make a hard burn towards whatever it is that sets your language apart. It's just basic sales.

(Elsewhere in this thread ori_b says this was not an intentional release, so I mean this as general advice, not targeted at this case. I don't know how to prevent too-early linking on social media sites short of not releasing anything public, which has its own problems!)
Exactly (except I use nc rather than ncat (which I think is a Debian vs Red Hat thing, but I'm not sure), so the ProxyCommand is "nc -X 5 -x 127.0.0.1:9050 %h %p" for me).
Check out my new single Nostalgia distributed by tunecore and live on iTunes
https://youtu.be/o5w71lHw2Mw?t=4

O P
E N B
R A

Hmmm, open bra?! Not sure if that is intended to be some sort of "lolwut" marketing effort but with the overlapping ribbons in the game perhaps they can sell advertising to a bra company!

It would be a shame to ruin the lovely symmetry of the logo, not serious enough to alter (beyond maybe the typography). Looks like a lovely game though.
They didn't have to buy all those leases. That was their choice, they're decision for how to run the project. And that was their downfall.
You did clear it up, except relatively rare does not mean that.

You can't make up new definitions for things and expect people to understand you.

Relatively rare has the same meaning as rare, except that it's rare only in comparison with the compared event, but might not be rare on an absolute scale.

So, no, 49% is not relatively rare.

1% is relatively rare, yet 1% of car trips is still an enormous number so is not actually rare. That is the only change in the meaning when you add the word relatively.

Getting back to your actual point, which was derailed by an incorrect word.

Multi car trips are less common, but not enough to make single passenger vehicles economically worth it. The majority of the expense on a vehicle is not the cabin. Once you paid to make a car, adding a bit more space for additional people costs only a little bit more, but greatly increases the flexibility.

So I don't expect the basic size of a car to change much.
I found this very interesting, check it out.
Personalized Nutrition: Healthy foods are unique to individuals http://bit.ly/1ItKTrV
Great reference and overview of ES6.

One minor quibble. I was bothered by the misuse of the words "lexical" and "interpolate". The lexical value of the keyword "this " is the string "this". Then, you might translate between two technologies such as CommonJS and ES6 but interpolating between them implies filling in missing data by averaging known values. Granted this word is commonly abused. Sorry this is a bit pedantic but these corrections would improve the document, IMO.
OK we took out the "C/" bit above.
Omega-3’s and the Eskimo Fish Tale
In that case, I have no idea why it exploded. :)
Yea that's essentially the path that we're trying to take. We are logging all the search queries for which we don't have product listings and aggregating that to show to suppliers.

We actually switched from the idea of charging users to charging suppliers because a bunch of suppliers told us directly that they'd pay us a 10-15% provision for every sale we bring them. I've asked the suppliers I've directly spoken with what they'd wish for if they could wave a magic wand and all of them basically said more sales.

I guess I'm maybe answering my own question, but to fake the marketplace, should we concentrate for a while on just being resellers for a couple of suppliers to earn the trust? We've tried to avoid that to convince users that we're neutral in the marketplace.
Why You Should Believe Your Friends' Claims About Food Allergies
Nice. There seems to be a resurgence of jQuery alternatives, see also Lea Verou's Bliss: http://blissfuljs.com/
Is there a way to track uptime across kexec[1] restarts? That way you could differentiate between a hard reboot and "soft" one (ex: automated kernel upgrade). Having a system like that working for a 18 years would be insane!

[1]: https://en.wikipedia.org/wiki/Kexec
If there's one thing I have learned, it's that Bryan Cantrill's words don't mean much.
I'm not in US but Canada.(twitter @enitalp) I'm at around 110k Can without Bonuses. Working in video game industry as a Technical Architect with 20 years relevant in video game and add more than 10 elsewhere. I have the best job in the world. not ready to exchange for an IT bank job even for 300k.
This was very useful, thanks! We will try to improve our message, figure out how to provide more value for our users and recruiters, and in the long run explore how to build a valuable brand.

Many thanks, Aaron!
Armchair physicist here... just relying on an undergraduate physics degree, so please correct any naïve misconceptions, but:

Isn't resolving quantum theory with gravity the only remaining hurdle to a theory of everything? Other than unifying the standard model with general relativity, what else is left?
+Erlang, +Pony, +Clojure (also STM waves hello), +Haskell

I also found that reference highly dubious.

I mean the reasons Rust abandoned it were quite legitimate. As a systems language with originally segmented stacks that performed poorly and were thus removed, which mitigated anything resembling the "lightweight" promise of lightweight-tasks, and then combined with the overhead of having to maintain two distinctly different IO interaction interfaces due to a lack of unification between the standard runtime and the libuv based M:N scheduler... I mean of course Rust needed to punt that semantic out of the core runtime and move it to a domain where that kind of functionality could be implemented as a library/framework instead. Otherwise writing consistent IO libraries for Rust would be a massive pain in the ass.

The point of Rust isn't to be an opinionated framework that provides a set of prescriptive models for solving problems like Erlang/OTP does. The point is to be a generic systems language that you could use to build a new Erlang/OTP shaped thing with.

I realize I'm quite literally preaching to the head of the International Choir Association right now though. ;-)
Depending on how you look at it, it could be said that their 'response' has been there all along via the API.

There is a vocal minority that is looking for more powerful tools to manage their specific project's workflows, often related directly to the behavior of their audience, which sounds like an obvious opportunity for custom tools (to a software developer at least).

For many projects, the structure and interface third parties provide is almost always worth leveraging. Get 99% of your product from day one and spend your time hacking on the few additional features you may need.
We have at least a small user base in every state, and also a small user base amongst students who started with us and went on to be accepted into universities and colleges, but to date we haven't invested significant time or effort into growing either. We've been too focused on trying to work out what the business model will be at the end of the day. Would you recommend a different approach?
China to set up its own virtual currency
The Tor BSD Diversity Project (TDP)
Cool - feel free to ask your question :).
Do you have another computer to try that on or perhaps start your browser without add-ons?

I use Firefox as my main browser and read nytimes.com every day. I haven't experienced any of those behaviors, nor am I able to replicate them.
Nickp on schneiers blog comments?
I have done the research. It can mean all of the things that I mentioned.
>I actually don't think the NSA cares about reading traffic from everyone;

Im sorry but your assumtions are just wrong. We know from Snowden that they DO collect all the data and have suffisticated search and anlysis tools for things like social graphs.

They want to know with whom the targets talk. Thats why they are doing it.

> The NSA is a government agency tasked with the mission of intelligence gathering outside the US.

That does not stop them from doing it inside.

> Intelligence is far more valuable when you know something and others don't.

Backdoors in crypto or hardware are extremly hard to find and if you pit them in, you have a huge advantage for a long time or forever.

> The NSA has a huge advantage over those other countries' spy agencies in the form of resources;

Breaking encryption with brute force just does not work. We know from the snowden leaks that they almost never go after the crypto directly.

Even if they can break RSA 4096, try breaking all the millions of https connections a day. Its even worse if its not public key crypto.

Its hard enough collect the data without breaking encryption first.

You can also combine the too. They made sure that RSA used a weak default that they could break.
EdgeDB – The next generation object database
You don't do it in UNIX because UNIX is fundamentally broken. That's the point. You do it through specialist software that works around the various problems. A common approach (i.e. compromise) in high-assurance security was to split systems between an untrusted, UNIX VM and critical components running directly on a microkernel/hypervisor. The kernels themselves were built as robust as possible sometimes with every potential, control or error state known. The apps outside VM's often used Ada or Java runtimes whose assurance and features were customized for apps needs. Robust middleware handled mediation and sometimes recovery. Many systems like this survived strong pentesting and worked without reported failures the field (or only failed-safe).

Then, there's the shit most people are doing and that Bryan advocates with UNIX. I also called him out on it listing numerous counters... with references backing them... to his comment at vezzy-fnord above.

https://news.ycombinator.com/item?id=10325607

Secure UNIX had already been tried by geniuses for a decade or two with always same results: architecture, language, and TCB were inherently so complex and insecure that even smallest versions had many 0-days and dozens of covert channels. He didn't respond, likely since he uses assertions instead of evidence. And all published evidence that I've ever seen contradicts his view of UNIX model superiority in robustness of any kind, sometimes performance.

Now, he's making all kinds of assertions about unikernels, deliberately avoiding evidence on some (eg performance), praising UNIX model/tech, and ignoring faults in his own approach. Should we take his word this time given prior result? Definitely not.
I was thinking about this recently - there is a need for a meta banking service - basically a p2p banking service much like Venmo -- but also allowing for vendors.

The actual funds can still be housed in a traditional bank - but you can still have an account or CC number which you would give a vendor.

Whenever the vendor attempts to charge your CC number the amount goes on escrow hold only in the meta-space until you the user will auth it to actually come out of your account.

It sits between the real bank and the vendor and you and gives one more control over their money.