skysight-inc/HackerNews huggingface dataset:
This ain't any old additional buyer. This buyer prints its own money.

http://www.economist.com/blogs/economist-explains/2015/03/ec...
Please no. Even if you are just changing copy, let me do it. Chances are you'll find a way to screw something up.
It's very easy to program. As the article says, anyone can do it. It's much harder to design systems that can grow without encountering pain points. The on-the-ground programmers should view it as a starting point; to turn into a company founder or system architect or manager. If I'm still coding day-to-day at 35, I'll see that as a failed career. But some people just actually love it; and for them, if they're happy with the limitations to their income and the risk of being replaced in 5 or 20 years, they should continue.
Source?
Because old people are bad and lame, right? How is this kind of remark allowed on HN?
Even the truly silly advice, like "Do not inject opinion," doesn't really do harm. (No force on earth can prevent undergraduates from injecting opinion. And anyway, sometimes that is just what we want from them.)

Geoffrey's writing would be stronger omitting "truly", "really" and "anyway". It isn't just novice writers who need reminders to omit needless words.
I really hate how that site plays video automatically and is using something to hide the player controls along with the ability to pause.
> too weird to live, too rare to die.

I disagree with "too weird to live" but at least it makes sense. What does "too rare to die" mean?
Or you could hire engineers who actually get the job done in a reasonable timeframe without someone else having to poke about in the code and potentially screw things up.
In case anyone is wondering which project this is:

The concrete contribution of the research report here
is the design and implementation of a fully compartmen-
talized operating system, MINIX 3. To properly isolate
faults, we have removed all drivers from the kernel and
run them as separate, unprivileged user-mode processes,
protected by the MMU hardware. Since all servers also
run in user mode in our design, only a tiny microker-
nel that does not contain any foreign, untrusted code is
left in kernel mode. Each component has only the mini-
mum privileges it needs in order to prevent failures from
spreading. In our design, driver failures are no longer
fatal and do not require rebooting the computer.
Fast password hashing is bad anyway. Slow schemes are better (assuming they come from a thoroughly tested library written by someone that actually knows what they're doing).
Mostly because I didn't want to spend my parents' money on it when I felt I had learned enough to get a job. I also decided I wanted to double major in Math but since it was just for myself I didn't feel like it was fair to my parents to delay my financial independence

I'm the opposite of you, I actually really enjoy learning from books. But then again, I typically like learning about theoretical concepts so that may be why books are fine for me; I just think about them, play with them in my mind, and do exercises if they have any.
You are not blind. There are no sources for the binaries.
The argument is duplicitous! :}

If you and I are responsible for a man who is exposed to doses of radiation everyday and I stand up and say, you know, we shouldn't have this guy exposed to radiation because it could be lethal, and you say, hoooold on, there's no such thing as lethal radiation, just lethal doses of radiation ... then I gotta wonder who you are working for!

Because both our points are that you gotta know how much radiation he is getting, and not according to some chart generated by someone who is benefitting from the labor from a distance, but actually what the effect of the dose is over the course of the guy's life.

We agreed about dose, but you don't tell me that I'm in the wrong for saying "halt work", by saying " but it's a question of dosage " and let the guy keep working while you do a 20 year study! You protect him first!
What is the ideal ratio of rent/net income?

Personally, I don't want to spend more than 20% of my net income on rent + utilities. That way, I can save 50% and use the remaining 30% for food and entertainment.

I am currently at 16% in Seattle and I leave in a very good apartment, but I got lucky.
Well, I was referring more to the situation where you're already reading something, or finished reading it. Obviously there is an opportunity cost that you could have sought out something better to read, but now that you're there - take what you can from it. In my experience a lot of people will dismiss an entire article based on one wrong fact or crazy opinion.

And when extended to people - just because someone says something stupid or wild doesn't mean everything they say is that way.
You mean decreasing share, right?
It's less that he's asking for help and more that this has happened multiple times and it's quite clear he should be allowing someone to audit the source code, not just search blindly for attack vectors. It's clear there are issues, it's time to invite some help.
What if I'm asleep? Or it fails?

Seems so much easier, and safer, for Amazon to just have a hard "don't charge more than this".

Increasingly, I wish this could be fixed at the banking end -- I'd like to be able to get my bank to enforce that I won't give more than £X to some company (obviously the company should be able to find this fact out, and not give me products worth more than £X).
Just to clarify... were the vulnerabilities in Firefox itself? Or were they in the extension?
You click the "down" arrow that's below the up arrow. You also need a bunch of karma, like 500 or a 1000.
Fair enough, just frustrated with the overwhelming number of "the modern internet is broken!!" posts that have been clogging up the front page lately. That also happened to be one particularly light on content.
Looks like the maintainer provides the sources in the release section:

https://github.com/bmatzelle/gow/releases
Hard limit of 72, beyond which many implementations will silently truncate, and reduced entropy from each character beyond 55 bytes.

Probably a good idea to pre-hash. Or use scrypt.
Holy shit you just articulated all of the reasons that hackers value their knowledge - and the very important quality of never giving up. You search. You go on IRC. You get the source and compile it. You step aside and learn a tool better in isolation - then use it on your problem. You poke, prod, test. And your understanding begins to form, to conform to the shape of the problem, the map of what you know, what you've tried, what you have yet to try. You talk to others to fill in the important blank of what you don't know yet to try.

Because that story you told is abhorrant, even profane, but all too common.
Why put the executable in source control without the actual source text files?
It appears to be one of those rare (but legitimate) GPL projects which do not disclose publicly viewable source, but should hand it over upon request if they are to obey licensing terms.

UnxUtils and DJGPP are other alternatives.

Speaking of which, this project has been posted on HN at least 4 times previously.

EDIT: No, they appear to be publicly available in Releases, as mentioned by another poster.
>AWS billing alerts

I don't want alerts, I want a fixed amount limit. If watching this sht was my day job then sure I'd be OK with billing alerts. I'm busy fighting other fires in my day job though & often won't see mails for days. By that time Amazon might have bankrupted me.

Amazon has some decent engineers & this is not technically difficult. Its very obviously a concious decision to not provide this very useful feature as any kind of capping feature will negatively impact revenue...but its also literally the only reason why I don't have a paid AWS account for personal use.
Use prepaid cards you load with a fixed sum.
I always felt weird about this kind of math, because problem don't have an "API", or an algebra, it's too open. But if you're into creativity and search then it's even more fun. Maybe a psychology thing in the end.

Took me far too long to find the triangle area.
The counter example is Iceland who told the banks to get lost and is the only European country who's economy is now ahead of where it was in 2008.

http://www.independent.co.uk/news/business/news/three-charts...
Why would it matter if you're asleep? It's the cloud, if you're not automating things you're doin' it wrong. I wouldn't do that, but you've already put costs ahead of uptime, so burning it down should be fine, yeah?

Amazon's market is largely not people who are worried about those kinds of overages, and I can't really blame them for not worrying about these kinds of edge cases.
Because the alternatives to neonicotinoids are broader-spectrum pesticides that affect other kinds of animal life, including mammals, as I've said repeatedly on the thread.

I don't know why you insist on being so overtly hostile, but whatever the reason, let me promise that it doesn't make you more persuasive.
Ha, I wanted to say Mantis!

I have used that to track stories/tickets/bugs for almost 15 years and it's my favorite. I love how the colors let me see at a glance what is most pressing. I find non-technical clients can use it without problems.

One thing a lot of modern systems suffer from in my opinion (Trello, Pivotal Tracker, Asana, Agile Zen), is that the space to leave a comment is about 2 inches by 1 inch. Who wants to communicate via that? I find that they work well at the top level of defining cards, but within a card I think their UI psychologically discourages communication, so people resort to email and other things. With Mantis I've always felt less friction getting people to keep the communication inside the issue tracker. When you consider that, I'm not surprised that people are saying they like Github Issues. It's one of the few systems where you don't feel like you're peering through a microscope.
> If we allowed a large automaker to go bankrupt

The 2009 "bailouts" of GM and Chrysler involved each company entering bankruptcy, and having the desirable assets of those firms purchased in bankruptcy by new entities in which the US and Canadian governments were (together) major (in GM's case) or minor (in Chrysler's case) investors. So, any sentence that starts with "if we allowed a large automaker to go bankrupt..." that concludes with describing a result that didn't actually occur is demonstrably incorrect.
sounds very similar to https://www.instartlogic.com/blog/dont-buy-the-javascript-yo...
Do beekeepers not bring their own bees with them though? It seems like unless they bring bees, there isn't much point to the migration...
Qora decentralizes the web, an Internet powered by people
The Week in Bitcoin Issue 29 – An Awesome FREE Weekly Bitcoin Newsletter
I disagree. The point isn't that no research should be done, but that nothing is safe. Your point was

"So we can also stipulate that the onus is on an the producers and beneficiaries of all the toxic mess of industry, to prove beyond a shadow of a doubt that their profit isn't coming at a permanent cost to the full realization of planetary health and sustenance."

That is an impossible task. Water is not safe. Oxygen is flammable. The number of things we can do that are not harmful to anyone or anything is closer to zero than you think.

If you set the bar at impossible, and I lower it to something achievable, it is bad form to evaluate my reasonableness as duplicitous.
I agree with you. SELinux should be on by default much like a firewall, but I guess I was referring to packages not shipping selinux policies leaving the user in limbo about why the software which is documented to work out of the box does not.
Well, it is kind-of possible for Ruby/Rails. I half-built such a system once. Here's what you do:

* Gather coverage information when running tests or compiling assets.

* Use that to generate Rakefiles for running tests / compiling assets that have dependencies on the source files they would touch.

* Run the tests once, recording information about the git status of each dependency.

* When the git status of a file changes (i.e. you've just fetched some changes), mark the dependency as dirty

Even better, it you're gathering coverage data and know the test status for each commit, then not only can you show the commit that broke the build, you can show the particular part of the diff that broke the build.

Here's a guy who was trying to do some of this: https://github.com/Genki-S/ttnt
I would advise you not to ask technical questions on Twitter ... but what's your real problem.
Most of the sources and binaries are from 2012. That version of bash would have the shellshock bug(s).

This project is a Good Idea, but it would be overwhelmingly more useful if it tracked modern versions.
Watches are a niche market with die-hard enthusiasts and fervent collectors. If you are planning on purchasing a high-end watch, you're more likely to step into a jewelry or watch-only shop, or watch specialist or distributor. Big box stores simply don't carry these types of watches nor are you getting the best deal for one if you find them there. Not to mention, you're at risk that it might be a fake. We're talking about brands such as Patek Philippe, Audemars Piguet, JLC, Vacheron Constantin, Rolex, and Hublot.
san francisco is absolutely miserable when it comes to dating. it's the only place in the world (the WORLD) i've been insulted to my face for trying to talk to women when out at night. i spent my early 20s there and i regret it immensely. i think it stunted me. no shit.

now i live in LA, which is fine but not stellar in this area.

new york is basically paradise for young single men. it's next-level.
Yeah that's good! I like Heidegger in that he traces the root meaning of words. So philosophy is love of wisdom, and everyone knows that but they seem to mistake the field for metaphysics and whatever else incomprehensible word jumble it loosely applies to.

Maybe it is a love of wisdom that drives some philosophers to drone on endlessly because maybe they feel we need more sleep!
Yup - frankly I'm very wary of anything that is an uncertain amount.

Did the same with my cellphone contracts - take expected spend, triple it and make that the limit. Put a number on it (even triple) and I can deal with it...just not liable for "unknown".
I would have assumed of course that the size limits were because the passwords were being stored in plaintext in fixed-length fields, but I guess they wanted to make sure they were 'complicated' enough? I guess salted md5 is literally better than nothing.

The character limits for usernames, though... smells like a SQL injection issue. Which is an obvious and completely naive thing to assert but they're using PHP so my immediate thought is that they're passing raw userdata into the database as strings.
I read a book on local investment and slow money but I can't remember the name of it. It talked about how the stock market has become divorced from putting money back into business creation. How it is just the sum of the money people have laying around. I want to extrapolate that to housing and blame the high values on investment divorced from construction but now I'm just repeating your question.
And the HN thread: https://news.ycombinator.com/item?id=1002723
Eighty columns is a good standard, I just think people forget how small it can be, and why it isn't always a problem. I've written tons of code that looks fantastic, if only I could use 85 columns, but rewriting it to use less just makes use of some pretty clunky constructs. All these extra "()"s and "/"s aren't actually helping make the line more readable, it just makes it fit into a rather arbitrary column limit. And at that point, you'd be thinking that the best way to make your code the most readable it can be is to use more columns.

So I don't think 80 cols is a hard limit, anymore than I think writing code in a terminal is a hard limit. I use a non-terminal text editor. I do it because it makes it easier to read code and format it how I like. I see little reason why anyone should be jumping through hoops to accommodate that. By using a terminal editor, you've already decided you won't get the best formatting, because you sacrifice the flexibility that allows it in exchange for something else. You should be expecting things to wrap around awkwardly on occasion.

Eighty columns is a good target width, but it's not worth proliferating clunky constructs to conform to. That's no better than having code wrap. (Of course, someone could also write terminal editors that allow text to go longer than 80 lines. Why are you using an editor like that if it can't do something this simple?)
Well, if you're an analyst, you analyze the data you have, not the data you need. Or something.

I suspect the people paying for this research are in the watches sold in department stores industry. To some extent, they're only concerned about their little microcosm.

Then these reports get churned out and Bloomberg publishes them because they need to publish something and it's cheaper than doing more extensive research of their own.
Billing alerts go to SNS, which can deliver to email, SQS, or Lambda.

You can actually automate the response if you want; it doesn't have to be email-read-by-human.
You're in AWS. Why do you think alerts mean you need to be watching for them? Alerts come from CloudWatch, to SNS, and from that can go wherever you want them to. So do that, with the tools they've already given you. And this lets you kill only what you want to kill--I mean, do you want them to dump all your S3 buckets? Or just, say, down all your EC2 nodes?

It's not about capping features being negative for revenue, it's that the customers who want it don't matter; if it's not something a company dropping $20K/month is going to use, I doubt it's really worth the time of day. You are a Linode or DigitalOcean customer, and that's not a bad thing, but I think that AWS is not the right place for you and I think that they know that.
I imagine Amazon would still come after you in court for the rest of the money?
>The economy is like an organism, not a washing-machine. The most optimal repairing mechanism is itself.

organism have finite life, they die. Washing machine can be maintained/repaired indefinitely. Of course cyborg is the best way.
Channeling my inner stallman. This looks like a lot of GNU utilities for windows, just like the name says. But the title says Linux utilities.
> No F# native ORM work on OSX as-is. Sql Type-providers neither. You can make some basic stuff and crash faster after you try anything barely complex, like do a search ;)

There exists a very good ADO.net wrapper for F# called FsSQL

https://github.com/mausch/FsSql

Dapper can also be used with F#: https://gist.github.com/vbfox/1e9f42f6dcdd9efd6660

Neither are true ORM compared to say nHibernate, but both include mapping to .net collections. I generally prefer this approach over a true ORM for flexibility.
So when you hit the limit you want AWS to stop your spending... how?

You're spending $/hr on compute, so terminate your instances. Plus your EBS volumes, so delete your drives. Plus... S3? So delete all your data?
Actually all professions are much more stratified by intelligence than in the past (this is side effect of meritocracy). There is lots of research on this - this is just the first paper I found on google [1].

In regards the rulers have a look at their educational background. In the roles that really matter they are all very clever.

1. https://www.staff.ncl.ac.uk/daniel.nettle/britishjournalpsyc...
Go isn't designed for the same purposes as Python or Ruby, either. It's statically typed and far less expressive.
Don’t punish old trials and former customers
I have to wonder what sort of code your average bootcamp graduate is really capable of producing. I'd say that you could get really, really good at a single concrete stack and toolset in that time (e.g. osx, bash, Linode, postgres, rails, chrome, sublime, chrome dev tools, maybe nginx, wireshark, redis).

But as soon as you swap out even one item, the pain will start.

Now do it with Windows, power shell, Azure, mysql, php, firefox, notepad++, firebug, IIS, mongo. Now do it with Linux, zsh, Digital Ocean Meteor, Safari, vi, django, apache. Now do it with Linux, bash, AWS, Java, Spring, Oracle, Eclipse, Glassfish. Now do it with RedHat in Docker on AWS running Postgres, Redis, Nginx, Java and Node, over WebSockets over any browser.

Now you will know what you are doing. It will take about 10 years.
My first post. I wanted to put something up that would spur interesting discussion. I'll be sure to look closer at how I name a submission.
Takashi Amano, nature photographer and aquascaper, has died
So it's not possible to encourage signed commits and add verified badges to combat the issue?
Thanks again. I agree, I've written a lot of code that would be clearer in 85 cols than 80, and some code that would have been clearer in 160 cols too.

I think we're agreeing mostly.

The problem with 'ish' is that I see it as worse than useless. 80cols-ish is what? 90 cols max? Why not just use 90 cols as the standard? If I have to scroll my whole window or resize it to read your line, is that really better than if it had an extra break? Some people may think so, but I don't, personally.
As I recall, it was the FCC; this is from the episode where they are at a trade fair and one of them is manning the FCC booth.
Tech Firm Ubiquiti Suffers $46M Cyberheist
Astronomer Uses Stars as Musical Instruments
Hard to say what the intent of the people that made this was, but even if it's not terribly useful, it's pretty clever. Maybe they would use it to bind 6 volumes of a series together?
Considered that - you'd still be legally liable for the full amount even if your payment method bombs out.

That said I do use this in a personal capacity - all my finance flows through a "burn" account that I keep cruising at a low-ish fund level. So if the sht hits the fan (fraud, overcharge etc)...so be it...I'll fix it once the smoke clears.
Individual organisms die. Short of existential events, ecosystems last.
How to schedule jobs in your Node.js service
In contracts most terms are not defined. This allows the judge to interpret them according to their common meaning, for example https://en.wikipedia.org/wiki/Patch_(computing)

I don't think most people will consider an entire program a patch.

Having us sign off on every patch defeats the intent of the clause. The intent is to give our customers a way to submit merge requests on https://gitlab.com/gitlab-org/gitlab-ee/merge_requests and to be able to comment on for example Stack Overflow with fixes they made so other customers can learn from that. We don't want to slow down that process.
my immediate thought is that they're passing raw userdata into the database as strings

That was my first thought too. I'd guess that it's a vulnerability somewhere in the code for handling the forums.

I would be willing to bet that they could get rid of a lot of the attack surface just by using standard services for certain things.