skysight-inc/HackerNews huggingface dataset:
A funny thing is I think >50% of them end up in Port Roberts, WA. It's an exclave of the US and relies on transiting Canadian border security, which generally prohibits felons from entering Canada, for communication with the rest of the US. As a result, most of the potential hitters from the mob, who are convicted felons, are less likely to be able to pass through, and they're also less likely to be able to easily bring weapons (although it's not that hard -- it's more that you'll get a bit of protection against casual interaction.)

WITSEC as well as international intelligence ops are suffering badly from searchable Internet histories, as well as biometrics at borders.
Why would you need secrets on a build server? If you need that much trust between your production servers, you should be using some external mechanism, which issues credentials with sensible lifetimes.
I was referring to the situation in the comment I was replying to, where a number of individuals have both valid and canary keys for unlocking an HSM, and the presence of a canary key when attempting to unlock causes the HSM to wipe it's protected key, but it can't be established which individual did not cooperate.

So the starting premise is that the device in question is already under the control of LE, a group of individuals has the ability to unlock the device (if they provide the correct keys), and they are being legally compelled to do so. In that specific situation, if anyone "defects" (provides the canary key), it's a crime, and everyone can go down for conspiracy, even if they themselves provided a valid key (which, in this scenario, is something we're assuming couldn't be proven anyway) and even if they never intended to break the law. That's the key part of a conspiracy prosecution - it doesn't matter which participant actually committed the crime, all the participants can be tried as if they were the "trigger-man".

TBH I'm not up for tracking all this down in the US legal code (got stuff to do, and IANAL), but here's the statute in the California penal code:

http://codes.findlaw.com/ca/penal-code/pen-sect-182.html

Note, in particular (heavily snipped for brevity/relevance):

> (a) If two or more persons conspire: [snip] (5) To commit any act injurious to the public health, to public morals, or to pervert or obstruct justice, or the due administration of the laws.

> They are punishable as follows: [snippity snippity snip....] When they conspire to commit any other felony, they shall be punishable in the same manner and to the same extent as is provided for the punishment of that felony.

There's no provision that the conspirators (or the prosecution) know which of their number actually committed the crime.

None of this would be relevant for HSMs on devices that aren't part of an investigation, or in general, any situation except one where a group of people are being legally compelled to enable access to evidence.

The bigger-picture point is just that using a split-key mechanism to give plausible deniability to each individual key-holder doesn't actually pose any problem for the criminal justice system. Legal authority would be pretty meaningless if it could be foiled by crypto gimmicks. IRL, it's "haha, very clever, now the HSM gets unlocked or all of you go down for obstruction."

edit: fixing formatting of the quoted blocks
I was reading HN on my phone, and this looked interesting, so I tapped the link. It took me to a brief page describing the three parts of the book, with a headline and one sentence about each part. At the bottom it said:

read online at:

• http://www.frontendhandbook.com

So I tapped the link. It opened a new tab with a brief page describing the three parts of the book, a headline and one sentence about each part. At the bottom it said:

read online at:

• http://www.frontendhandbook.com

So I tapped the link. It opened a new tab with a brief page describing the three parts of the book, a headline and one sentence about each part. At the bottom it said:

read online at:

• http://www.frontendhandbook.com

So I tapped the link.

Wait! Haven't I been here before?

There must be some other way to read the book.

Hmm... Some faint little gray icons at the top. Nothing there jumps out at me as a way to read the book. I keep wanting to go back to that compelling "read online at:" link.

But this time I skip past it. I go all the way to the bottom of the page where there is a faint gray angle bracket. What does it do?

I did it! I made it to the first chapter! Now I can read the Front-end Developer Handbook.

This is a true story. I really did tap the link that many times. I am not making any of this up.
EURUSD Cuts Through the 1.1016/17 Zone, Remains Susceptible
I've seen projects announced on and off to make a next-gen TeX or TeX-like from a clean start, but they never seem to go anywhere. I think writing a good rendering engine is just a ton of work.

Two approaches I see as plausible:

1. Use TeX as a "document assembly language" of sorts, a pure back-end rendering target not exposed to the user, and do your document markup/scripting in some other front-end language. Pandoc [1] is a start at building infrastructure for this. You can then build a new renderer too if you want, to remove the dependency on TeX, but at least in the meantime you have a pathway to producing quality output right now.

2. Build something on top of HTML+CSS (maybe also +JS). Advantages of this would be that it'd make it relatively easy to target the web with the same document source, and open-source web browsers have already sunk a ton of development time into rendering. CSS even includes a bunch of print-oriented features that in principle provide markup for most of what you might need here, though browsers for obvious reasons haven't tended to prioritize those parts. wkhtmltopdf [2] is a project aiming to build a to-print or to-PDF document workflow on top of Webkit. However imo the results are still not near TeX-replacement level. I believe the gold standard currently, if you want high-quality print out of HTML+CSS, is the proprietary PrinceXML [3].

[1] http://pandoc.org/

[2] http://wkhtmltopdf.org/

[3] http://www.princexml.com/
Nice. This is about 70% of the way there toward the fully visible conceptual graph I've wanted to make or find for years. I'd like to be able to see items from multiple zoom levels, for example. I want to be able to look at a bubble that says something like "addition of positive integers", and follow a sequence of arrows to every academic concept and career that makes use of addition.

Another thing I want software to do is highlight everything I think I know (maybe take some quizzes to prove it), ask me what I'd like to know, then show the graph and list of topics I need to learn in between. Based on another comment[0] it sounds like it would eventually be possible to use this data to do exactly that. So again, nice.
I will be looking for frequency of medication errors per medication. Giving someone a triple dose of advil or local anesthetic probably not too big of a deal, but a triple dose of phenylephrine or labetolol is asking for trouble. In other words, I'm curious of the rate of scary mistakes versus meh-don't-worry-about-it mistakes, though that terminology is not politically acceptable. Explaining any difference there would be fascinating.
Also they don't really need a credit history if they're given housing/car to start, and cash for secured accounts.
'Don't include "sensitive" configs in your Git repos' should be the correct title.

With regards to external dependencies, Vendoring is a source of debate and I don't think the larger community agrees on one rather than the other. More recently, Golang recommends Vendoring, and last I heard, refuse to support dependency management, so if anything you should look at their arguments for doing so.

https://www.reddit.com/r/golang/comments/2xpulb/the_go_team_...

I do thing this is important to absorb though:

Point 1 - a build must always be reproducible and deterministic.
Point 2 - a build that pulls in external dependencies relies on its external dependencies to be reproducible and deterministic.

When Point 2 is not 100% certain (reliability, changeable artifacts), Point 1 goes out the window. Therefore, Vendoring is a crucial strategy from a build engineering perspective.

The most common strategy to mitigate this in a non-vendored build is to have control over the external dependencies by deploying your own dependency platform for your organisation. The latest Artifactory, for example, has proxy support for many mainstream artifact repositories (gems, eggs, dockers, images, modules, bowers, etc.).

Now... this project I inherited has had modifications made to the vendored dependencies... smashes desk with head
Ok, thank you for the perfect straw man, right there in glorious living color. If an employer gets 30 male applicants for every female, then I suppose that fictitious situation would justify discrimination against women.

But there's no reason to assume that is the case. The evidence, in fact, is that women do apply for jobs and are not hired. Blind trials of anonymous resumes show that women would be hired, if only the reader didn't know they were women. That once hired, with nearly identical job histories for men and women, men are complimented for leadership qualities and promoted, while women are criticized for being bossy and demanding, and denied raises and promotion.

Willfully ignoring these well-documented issues is not the same thing as debating. Coming up with one anecdotal case (that 'constructive contrasting') and concluding that nothing should be done because there is no problem, is pretty much classic strawman argument.
Some firewalls, virus scanners, etc. treat "unpopular" as synonymous with "suspicious". It's very annoying as a small software vendor.
> There are some places where--for who knows what reason--both Firebug and DevTools have ignored breakpoints I've put in...

This might be because the js file you put them in is loaded with another URL and is therefore considered a different file (and therefore does not have your breakpoint). This is what I've experienced before.

This is a bs design, of course, and files should probably be compared via means other than URL.
> Do not include your compiled files or binaries in a git repository! Binaries (or executable files) will almost always be operating-system-dependent. This will cause major headaches if you have some developers using Macs, some using Windows, and some using Linux

I think you're doing something wrong if this is an issue. Unless you run on Windows, Mac, and Linux in production, your developers should not be locally running disparate platforms, they should be running whatever the production server does. There may be other reasons not to include binary programs, but this isn't really it.

> Furthermore, there are certainly good reasons (read: file-insurance) to commit these kinds of files.

What he calls "insurance", is basically the whole point of using revision control to me. I want everything linked together in a versioned dependency tree that's stored and manipulated with one interface. Whether it's code, text, or images, if it's logically part of the project, then it all goes together. If git can't do that for you, it's not the right tool for the job.

> Do not include downloaded dependencies in a git repository!

Works great if Github or whoever is around for as long as you want to have a complete history, and the project owner doesn't push out new incompatible code under the same revision, and the project owner doesn't delete "that old version nobody uses anymore"...
I think he was being sarcastic.
I have a close friend who is in your price range, depending on the length of the article. He's written for Business Insider, Cosmo, and Brooklyn Daily Eagle (from NYC).

Contact me at smt88hn@gmail.com and I'll forward his info.
This site pays you to shop and recommend products
Do you have experience in healthcare? 3% isn't shocking to me, in fact a number of studies of IV med administration have error rates narrowly on either side of 50% and serious error rates in the double digits. This report suggests that you're safer in surgery than elsewhere in the hospital :|

I spent over a decade working on technology solutions to prevent medication errors in hospitals but the bottom line problems that make it a hard problem to solve are:

1. There is a culture of individual blame and so (certainly most) errors go un-reported at all. Systematic identification and process solution is still not healthy, despite 16 years having passed since IOM did an admirable job shining light on the problem [1]

2. There isn't strong enough motivation to fix. It's easier to not report medication errors than to fix them. You or someone you know has probably been victim of a medication given in error one way or another. You just aren't likely aware of it. Many errors aren't very serious, or result in lengthened hospital stays (which guess what!? the responsible institution probably gets paid for). Even the consequences of serious errors aren't often (maybe even usually) attributed to the source mistake.

Like many things, money has driven the status quo (more money in ignoring than acknowledging) and it'll drive the solution. Accountability and solutions to this problem will come in the form of payers [your insurance company] finding ways to measure and not reimburse for consequences of errors. Once that motivation exists in a major way solutions will show up very quickly... it's a non-trivial, but also sub-ridiculously-hard problem to solve, from a process/technical perspective.

[Edit: I've been out of this problem space for 6-7 years now (because fuck selling things to hospitals [2]) so would love to hear from anyone who knows whether things have changed significantly and my take is now wrong/dated.]

[1] https://iom.nationalacademies.org/~/media/Files/Report%20Fil...

[2] Not that it isn't super profitable - particularly if you spend way more on steak-dinner-sales than making shit that actually solves problems! An ironically terrible/frustrating market for anyone who actually cares about clinicians or patients, though.
Bharat Gas Online Booking
Here you find out the whole information of Bharat Gas and its online booking, refill booking,or how to get new connection, transfer connection and further details of Bharat gas Services, to know more, visit: http://goo.gl/PMco8O
Proximity to a particular repair shop is obviously a factor, that's fair.

Where I'm at I can be at an Apple store talking to a tech within 30 minutes. For a major problem, I can be walking out of the store with a brand new laptop within an hour. Apple does all the same stuff with your registration, as long as you bother to register it, unlike the author.

Getting a PC fixed, on the other hand, it's pretty much going to the retail store where you bought it (which has a tech team that's barely qualified to install anti-virus software) or calling up the company and finding some mom-n-pop repair shop that services their warranty repairs.
But hiring is absolutely not done on merit. Its done on 'cultural fit' and that means, hire more guys like us. Women are widely discriminated against, merit notwithstanding. There is a fundamental problem in our industry, and denying it or throwing anecdotes around isn't helping us move forward.

And if 'straw man' offends, then I suggest learning to make other kinds of arguments. I call em as I see em.
they quoted $20k (ballpark) per mission - that strikes me as a little high for 25g to LEO. What is that paying for?

Using the old benchmark of $10k per lb to LEO 25g could cost $550.

Cubesats weigh up to 1.3kg and cost about $100k to launch (https://en.wikipedia.org/wiki/CubeSat#Costs) - so that works out to $2,000 for 25g.

Is that extra $18k going to bespoke mission planning work or amortized development costs or really great t-shirts?

This is very exciting, of course. I'm tickled by a non-game web-form having this label: "Select how many satellites you wish to launch"
"Unfortunately, VMware has explicitly asked for the filings not to be published and, accordingly, Conservancy has not been able to review either document."

Anyone more familiar with German law that can explain this to me? Normally, civil filings are open to the public in the U.S., which seems like a good thing, so I'm wondering why German law allows this.
Aren't all non-competes illegal in California?
I take issue with the case against generalist or 'Full-stack' engineers. Of course you'll find people better at things if they specialize. But learning core javascript very well along with things like HTTP, databases, css, html etc. I'd say you're a pretty solid engineer that can build full products.

Not a designer, you can work with a designer.
That's why I'm still inclined to believe "privacy vs. progress of mankind, pick one" soundbite. It's a perfect example of data that's really useful if collected this way at scale. Destroying large-scale data collection because advertisers/Evil Future Government is throwing the baby out with the bathwater.
Every time I've even considered getting the Windows PC out it has been the direct result of a game on Steam which had no Mac version. None has overcome activation energy.
German Consumer Protection Ministry Calls for the Right to Resell EBooks
Tried pandoc with markdown?
Well, cherry-picking then. "See, I can come up with one situation that isn't the same as all the rest; thus I refute the general claim" is plain wrong.

Semantic quibbling about 'reverse discrimination' is a standard lame trick used by those in power to justify their continued power. It doesn't fool anybody; its just selfishness.

And really, if you have no idea of the state of employment and the gender gap, what place have you in this discussion at all? Denying the widely published statistics and endemic problems in modern hiring is a species of willful ignorance I find breathtaking.

See, I take care 99 days out of 100 to reply evenhandedly and avoid any reference to others posting here; I try to stick with the topic and illuminate the issue as best I can. But today, I've been driven mad by the sophomoric nonsense.
100% agreed. It's not well-designed on the front-end for mobile. That would make me skeptical about the book itself since it's supposed to be about...front-end design.

But I think one should be careful about the distinction between front-end design and development. This book seems to focus on development, and as someone who's taken a couple of courses from Frontend Masters, I trust it to be solid.
My startup was not selected.

This was the first accelerator we applied to, and I of course obviously hold no ill will. I may try again in the future. I do appreciate that they said I would have an answer today, and I received an answer.

We are in the process of having our MVP built (finalizes in November), and will continue on as we have been.

In one way I am kind of happy. This is the first rejection to overcome.. who knows how many more we have ahead of us, but our passion to bring opportunity to every person who wants it will not be stopped.

I wish every company selected this year nothing but the best of luck moving forward.
>Note: This information has been disclosed to
>Google appropriately, they have chosen to not
>fix this behavior.

>The other day, my friend sent me a link

So did Google respond with a "No" or is 2-3 days with no fix considered too long?

I'm not diminishing the seriousness of this problem but it just got a whole lot worse being on HN after only 2-3 days head start on a fix to a major part of the Google product line.
I leave design to the designers. I think understanding how to use photoshop is a nice skill to have for working with designers, but I care more about a good engineering implementation for a mock than I do about the design ascetics of it. Front-end engineers aren't designers, they're engineers.
I think you're forgetting the most important part of the equation: China is still a developing country. In fact 50 years ago, it was one of the poorest countries in the world. As amazing as it's total GDP output is (by some measures more than the U.S. now) it has 5x the people. While yes there is some artificial currency devaluation, that is nowhere close to being the reason it's cheaper to live in China.
https://sitereview.bluecoat.com/sitereview.jsp#/?search=expi...
Wow, super depressing. Don't forget that there's more to this life than writing code, folks.
Current contents of "flymaids.com" is a 404 page:

Heroku | No such app

There is no app configured at that hostname.
Perhaps the app owner has renamed it, or you mistyped the URL.

Hosting appears to be by GoDaddy.
How in the world does a SMART-compatible Samsung SSD not have secrets?

Did they never read any of Snowden's leaks? :(

https://www.google.ca/search?q=nsa+hard+drive+firmware
QE causes asset bubbles. Negative interest rates promote (in theory) consumption over saving.

Economically, these are uncharted waters.
yeah, looks like they're analysing "reputation" for that particular category. Blech.
Should This Be the Last Thing You Read on Academia.edu?
I've had cold sore since before I could remember and certainly before I ever open mouth kissed anyone. Kids often get them from being germy kids. There's really no point in worrying about it because you probably already been exposed.

Take it from me, I have chronic cold sores and while they suck there really isn't much use in worry about it. Most people don't get chronic cold sores, I am in the slim minority.
I probably should've made that clearer.
Point Roberts? "Point Roberts also has a small airport and a large marina for air and water access; these two facilities allow direct access to the rest of Washington state without the need to enter Canada." https://en.wikipedia.org/wiki/Point_Roberts,_Washington#Tran... I suppose it might be harder for hitmen to stay low-profile when entering by boat or plane instead of car, but I'd think it's not really going to stop them. It's neat to learn about the place, anyway.
...and drunk drivers think they are driving just wonderfully, until they hit a post.
> I do think that TeX & LaTeX are close to a local maximum, if not al the way there.

Funny you say that since TeX's version scheme (in part) is that it approaches pi. And IIRC will be pi upon Knuth's death.
All a website would need to do is tunnel the entire site through a proxy that rewrites all of the asset and other same-site URLs so they are all the same type of synthetic token or hash. This would remove the ability to do host or URL based filtering, forcing ad blockers to download every URL and try to classify by content.

This isn't even a particularly complicated change, and I've seen it done before (circa 1997). As for how this impacts the ability to play the current "ad bidding" game, that is trivially solved by 3rd (4th?) party proxies.

Ad blockers can be inconvenienced even more by making the content unique every time it is sent by the proxy, preventing trivial matching by file hash. The end-game of this type of strategy is having the proxy serve up a single opaque block of WebAssembly code that renders the page to a <canvas> using custom and/or obfuscated font rendering.

This is almost certainly a stupid way to run a website, but I expect people that feel they are under attack from ad blockers to fight back in any way they can. Some of them are already trying to make up "moral" arguments (and legal wishful-thinking) against the recent increase in ad blocking. Obviously this won't work in the long run, but people that feel they are under attack are not know for making rational decisions.