skysight-inc/HackerNews huggingface dataset:
> Using an api service to with client certificates doesn't really help either, because if the application code can access the required configuration and certificates, so can an intruder with shell access (since the intruder most likely has the user permissions of the running application before doing a privilege escalation attack).

The problem here is that if your application requires the use of encryption keys, and the user which runs this application gets compromised, you have a problem anyway - since like most applications, yours probably also doesn't care about the key's security once it's in memory. If they get that far, the only thing you can do is replace/revoke those keys and take the hit.

In more secure non-cloud setups, encryption/decryption is being done by something like a HSM, a box with only one interface (usually PKCS#11) which can be used to encrypt, decrypt and sign stuff, and you never see the keys. You have software HSM's - and you could try to apply the same principal in the cloud, where you have an isolated box with only the very well protected and audited soft HSM running.

But not sure the cost of learning and maintaining such a system is worth it for most situations, where I would use an API service like Hashicorp's Vault. Most of the compromising of keys and secrets doesn't happen on your servers, but on your or some developer/user's work machine. How many crap is exchanged over email, dropbox links, slack, skype, ...? Keeping keys out of the hand of the user and eliminating the need for your users to have them at all is higher on my priority list.
You could get a Blackberry for $99/$199 on contract at the time, and BB was the dominant smartphone manufacturer of the day. It was obvious to most that the model you outline in #1 could change at any time, and most people figured it had to change...
Cooperative Scheduling with requestIdleCallback
Heh, happy to see doom9 still alive and kicking. They were the n°1 resource in the early days of mainstream video compression.
> It's far more useful than the current University arrangement, where 'everyone' gets to pay money to drink for 3 years

As shallow as it sounds though, it is bloody good fun.
Don't forget that DotCloud/Docker was originally basically a clone of Heroku, where "12 factor" dictated that all persistent data was stored in (non-containerized) Postgres.
Assuming you are better than the other players.
Diff Tools on Mac OS X
We've been using docker in production for two years now. Started with docker 1.4 and Rancher v0.15. Docker has had it problems with backwards compatibility, but we haven't had the mentioned filesystem problems.

Our containers are completely stateless. We use AWS's RDS and S3 to store state.
I found it interesting that the FCC's recommendation was to build an opt-out system, since this is so obviously anti-human and pro-corporation. It shows where their interests lie.

This kind of system should be opt-in only, with hand-signed agreements.
First, from Wikipedia [1]: "The Armitage–Doll model is a statistical model of carcinogenesis [...]"

Second, the paper itself [2] talks about cancer rates and uses experimental data for it (I just glossed over it, so I can't give a decent summary). This is a statistical model.

I think we disagree since you misunderstand what the term statistical model means. Furthermore, you are misusing the term "first principles." First principles really means that you start from a well established theory that describes how something works. From there you predict mathematically, or with a computer simulation, what the reality is. Using experimental data is strictly forbidden.

From Wikipedia [3]: "In physics and other sciences, theoretical work is said to be from first principles, or ab initio, if it starts directly at the level of established science and does not make assumptions such as empirical model and fitting parameters."

I generally have no idea about cancer research, so I have to trust you and cannot comment on the usefulness of the approach.

[1] https://en.wikipedia.org/wiki/Armitage%E2%80%93Doll_multista...

[2] http://www.nature.com/bjc/journal/v91/n12/pdf/6602297a.pdf

[3]https://en.wikipedia.org/wiki/First_principle
It's not a question of illegal or not, it's a question of whether smokers are able consent to the risks of smoking, and therefore whether the companies are absolved of damages.
Yes, I'm a security consultant and we often run this on client machines during security tests. It provides a nice assessment of the machine.
My GP is big on bones, specializing in old people. He helped develop some of the fancy bone scanners decades ago. He told me that astronaut bone loss is a solved problem, that if they want too they can keep bones strong for a year or more. He was of the opinion that when astros come back with reduced bone it is because they have been part of a study. The goal isn't to save all the bone, but to study exactly how little exercise is needed to achieve satisfactory results.
If not Docker, then what?
> That said, even if you submit a pull request or an issue ticket and the maintainer doesn't follow up, or is making the issue unnecessarily complicated to resolve formally and merge into the main branch, at least the record of your findings is there attached to the repo as a rejected pull request or a closed issue ticket, and that can help someone who comes along after the fact who maybe experienced the same issue you did and can benefit from your comments. Maybe that same person who comes along later will have the time to fight for having the changes merged, and can use your comments as further evidence that the issue is worth reconsidering.

In my experience, this is a continuous source of frustration and anxiety. Not responding doesn't stop the notifications, and on top of that it also makes the contributor look bad by ignoring follow-ups. It's much easier and less frustrating to just not file anything in the first place.

> I stand by the idea that finding the issue, but posting it on an unrelated forum (like HN) instead of attaching it to the project itself serves no purpose than to tell others who are probably not even users of the open source code "look at this problem I found/solved, aren't I great?"

This is just flat-out bullshit, and frankly says more about you and your assumptions than about CiPHPer (who, for the record, is somebody I know personally). Have you considered that maybe CiPHPer is just tired of arguing with vendors and getting nowhere, and has now resorted to just publicizing their fuckups in the hope that maybe that will change something?

To be clear: nobody owes any vendor anything. While I personally at least attempt to disclose a vulnerability privately before going public, there is absolutely no requirement to do this. It is first and foremost the vendor's responsibility to keep their software and its dependencies up-to-date, not that of the public. Be happy that it's being reported at all, rather than just quietly sold on the black market.

The reality is that vendors have been grossly negligent of security for the past several decades, and still continue to do so, using all kinds of shit excuses about how much time and money it costs to fix something they shouldn't have fucked up in the first place. Don't be surprised when security researchers get tired of that shit, and just start dumping vulnerabilities publicly when there are indications that the vendor is negligent (like is the case here).

Again: the change here is to come from the vendors, not from the security researchers.
I'm going to again avoid your analogies, again because I find them misleading in crucial ways.

If your talking about voter fraud via impersonation, I find you have even less of an argument then you did when I assumed you were referring to illegal aliens voting.

As I've cited frequently in this thread, stealing an election via in-person vote fraud is an extremely inefficient and difficult way to steal an election. It's ridiculous to suggest that you are concerned about voter fraud, and then focus solely on the types of fraud empirically proven to happen least. It's equally ridiculous to say that because the empirical evidence we do have disproves your opinion, then that research must be wrong and thusly you don't have an onus to provide any proof of your allegations. Much more voter fraud happens with absentee and mail-in ballots, but since these voters are typically white that is OK.

In any case, you are trying to dress up the actual intentions of the laws to nobler causes than reality suggests. State GOP parties have already been found in court judgements to use Voter ID laws as weapons to suppress minority votes, and I quote 'with surgical precision.' They've weaponized DMV's toward this goal, by shutting down centers in minority areas, cutting hours, and directing employees to avoid giving out free voter ID's and not advertise such services.

These laws are explicitly racist because they specifically target minorities to deprive them of their rights to vote, and this is why they have been, and continue to be struck down in courts of law across the country.
It's actually also quite common for undergraduate courses in the media industries.
Suppose we want to prove that every string is perfectly cromulent. I love it already.
Ok, I see that now, it was not always the case...it has been awhile since I looked through their documentation. TY!
Most agency advertisers have known about this for well over a year. To my knowledge, no one is particulary interested in it.
Where can we follow this project?
I heard Samsung Node 7 is gonna blow up!
It's quoted in current because these systems can operate on a range of voltages, depending on the batteries (or other power sources) used.
You and me both. To this day I deliberately don't think about it, because it just makes me sad that what seemed to be incredible potential was shelved. I guess the Surface products are the closest to that potential, but for a long time all we had was the iPad and awful Android tablets. And I still feel like all of it doesn't live up to the ideals the Courier had.

I'm now going to go and forget this comment happened so I don't spend the day depressed about where technology went.
I have dreams about this, and think the bare os must be a kind of hypervisor.

Then, on-top, you can launch "classic" OS like windows, linux, etc. Then also, the new OS.
I've been running docker in production for about 3 years.

Almost every time I've hit a problem, it has had nothing to do with docker (though everyone likes to blame it). 99% of the time the issues I've encountered are due to docker configuration (and yes the learning curve is steep) or the app itself crashing.

The one time I've encountered an issue with docker with databases (used elasticsearch) was a kernal issue (where the host kernal was out of date). That was the only time I had to care about the host OS in debugging a docker issue.

One thing that I recommend for anyone getting into docker - use docker-compose for everything. Don't use the docker CLI.

One of the major problems I have with docker is that (especially for beginniners) the docker command line tool can cause unintended consequences.

Every time you run docker run <image> you are technically creating a new container from an image. Once that finishes, the container still exists on disk. Using the --rm flag will cause the container to actually be removed after running it. I sort of wish docker would emphasize that flag, because often when developers are debugging or trying things, they will continue to run docker run <image> multiple times - not realizing that they are creating a ton of containers.

Yes, the containers are usually very light, but it caused a lot of confusion for me when I started out. And part of my superstitious self believes that the less dead containers you have the less likely you'll have filesystem issues.

A second source of confusion for new devs I've noticed is that the concept of volumes are somewhat confusing. "Why would I ever do COPY in my docker file if I can just volume it?"

Once you've worked with Docker, like any tool, you become more adept at avoiding a lot of the mistakes mentioned in this article. Which leads me to a point I can't disagree with the OP about - upgrading docker is annoying as hell.

Almost everytime I upgrade docker I end up having some obscure error. When I look on docker github I notice I'm not the only one, and often times the issues are just a few hours old.

But, what the OP didn't seem to realize, is that to avoid these issues you need to lock your docker version in production to one that you know works. Additionally, you need to not build your dockerfile in production. Build your docker containers with a build system and upload them as artifacts. You can either use an internal docker hub or do docker save to save them as a .tar.

Building while in production is a real no-no, even though it may seem more attractive than moving around 300-500MB images. You never know if that one dependency you apt-get in your dockerfile is offline for some reason. And you can't always depend on devs of dockerfiles properly versioning them anyway.
I don't dispute that "extreme anger and indignation" can change the world, but I'm not convinced that it effects change that is long-term good. Anger and indignation often lead to rash decision making, hostility, vengeance, etc. The world isn't really better when we trade injustice against one group for injustice against another, and extreme anger has an unfortunate tendency to do just that.
Germany still has apprenticeships (we call it "Ausbildung") and it's great.
Indian scientists detect crack in Earth's magnetic shield
There was an article about a Tesla fire at a Supercharger station in Norway a year back, and the firefighters back then said you were supposed to use water with some form of copper in it, and that it was too costly to use now, so they let the car burn.
> CE Pocket PC et al suffered the same problem as Symbian and everything before iOS: they didn't have the App Store, and as such it was a pain to get software for the devices other than through the OEM.

Huh? Software could be installed by downloading a file and clicking on it. In many ways was a simpler and more pleasant process than interacting with App Stores. The problem wasn't with finding or installing anything, it was with monetization. App Stores and always-online model made it trivial to charge people and show them ads.

Overall, I remember my Windows CE PDA with fondness. Using it was a positive experience, which I can't say about any smartphone I owned.
Great so we all have access to useless software code.
I Hacked the Middle-Out Compression from ‘Silicon Valley’ (2015)
Exactly. Opt-out systems are fine for things like organ donation, because a reasonable person could go either way. Building an opt-out system that no one in their right mind would ever opt into just reeks of anti-consumer behavior trying to hide behind a polite face.
"Issues with storage" is an understatement. Linux has major issues with storage. I see no way forward for Linux in that area unless they adopt ZFS.

How many filesystems has the Linux world created in the last 20 years? Of those how many are rotting piles of tire fire?

Filesystems are hard to get right.

ZFS is the way forward. For cross compatability, for reliability, for stability, for lots of use cases.

Btrfs is another tire to throw on the burning pile of other filesystems that won't work out in Linux.

Let the down votes begin.

But Linux has some major architectural issues that eventually the Linux faithful will have to admit to.

Containers.

Filesystems.

Observability. Though bless him Brendan Gregg is trying his hardest to help here.

Portability.

And this is what is so painful for the rest of us to watch or deal with. This inability for the Linux folks to admit these glaring architectural problems. Problems they refuse to look outside their bubble to see how others solved these problems and adopt solutions that have already solved these problems. They just want to continue to bury their heads in NIH soil. And double down on trying to solve these issues, poorly, on their own without any awareness of how others have solved these issues. People outside Linux land just might have the right ideas on how to solve these problems!

But I expect no one in that camp to acknowledge this and down vote away.

Sigh.
"Some products are inherently unsafe, and that is precisely what the costumers want."

Radioactive material in tobacco might be mutually exclusive from nicotine and MAOI content. My layperson guess is getting rid of the radioactivity would require prohibitively expensive hydroponic growing. It's the drug part that consumers want, and I'm pretty sure if given the knowledge and option they'd go for non-radioactive cigarettes.

Swedish snus is made to minimize tobacco-specific nitrosamines (TSNAs), but seems to not address Polonium-210 on account of the radioactive stuff being "comparable to that from the natural background radiation sources or dental x-rays": https://harmreductionjournal.biomedcentral.com/articles/10.1...

That excuse doesn't seem to hold up to scrutiny. Who really wants to have 10-20 chest x-rays done per day? Are "dental" x-rays really as weak as "background" radiation?

Alcohol seems to be in a similar position - see the popularity of nice wine and beer over e.g. guzzling cheap spirits.

I think people want health AND pleasure, and are willing to do their own hedonic calculus.
This does look interesting, but there's already degree apprentices out there doing essentially this in various employers, with an accredited degree at the end of the process.

We have a couple working in our office, and I've been hugely impressed by them

https://www2.mmu.ac.uk/apprenticeships/students/digital--tec...
And they removed digital audio from the headphone jack. It's quite a budget device they've been trying to make in all but appearance.
Matt Mullenweg Talks New .BLOG Domain
Don't let perfect be the enemy of good. Opening up code in voting machine would be leagues better than leaving it closed source. At least other experts in the field could verify it.

Its also not like every citizen today can or understand all of the vote counting procedures with paper ballots, even when just constrained to their ballot.
"Good" is a horrible app, but the wiping functionality is restricted to the data within the app. That's why the app is popular with companies for private devices, because it is very hard to export data from it.

Wiping a personal device to delete business data within one app would be illegal in a lot of countries.
Thirded. I've bought a few books and tried audio, youtube videos... Headspace is the only thing that's helped me keep a meditation schedule for more than a few months.

I know some people don't like how much Andy speaks during the sessions, but I liked it a lot. It also helps with that "am I doing this right? Should I scratch that itch? What should I think about? Or not think about?" feeling that comes up, because he addresses those feelings a lot.
Gerard is an ACM Fellow and a member of the NAE, and has been a leader in reliable software for NASA since he came to JPL from Bell Labs.
Why is that not a problem for the other EU member states?
Consider the economics of the companies who build web apps.

1. They have a process for producing quality work.

2. Changing that process entails learning a new process and the risk of producing work of lower quality.

3. The value the firms provide is in the quality of the apps.

It seems that your argument is that using a framework should reduce the effort a firm expends on producing an app and there is an implicit assumption that that reduction in effort should be manifested as a lower cost to your company rather than higher profits for the firm or higher quality in the app. That may indicate that your company is not a good fit for the services of the firms you have talked.

Nothing wrong with that, it's just market segmentation. Might even be a good thing since it avoids misaligned business interests. I mean if your company is a profitable ongoing concern without an app, then a bells and whistles app probably isn't critcal to success and a simple wrapper on a web app might be a reasonable first pass at implementing 'mobile app as a feature' because it is the simplest thing that might work.

It doesn't have to be rolled out multi-platform. It doesn't have to be rolled out to everyone right away. It does not have to be all grown up to be shown to committed users for feedback. Later on when there's a good 0.87, it might make sense to hire a consultant for the 1.0.

Good luck.
It's a wonderful read, and a good education.

On the other hand, it isn't a very practical solution to most people who are thinking "I'm not sure what algorithm to use here".
>"the observed relationship would be explained if a cancer cell was the end-result of seven successive mutations."

http://www.nature.com/bjc/journal/v91/n12/pdf/6602297a.pdf

That is clearly a process, not like the example of Muons and Kaons proposed to be similar (ie "A is correlated with B").

Of course, the next step is to figure out htf this process works.
T-Rays to Make Computer Memory 1,000 Times Faster
And importing talent is bad because...
they can't 301 if they don't already support TLS. If you attempt to connect to a site over TLS that doesn't support it, for starters port 443 is not likely to be open. 301 is part of the HTTP protocol, TLS is transport layer.
Profilers and impossible exceptions
Nicotine gum?
The danger is in the smoking, not the addictive substance.
"pay money to drink for 3 years"

Or 4 years here in Scotland - which reminds me that the university department where I studied and worked was in the Grassmarket of Edinburgh - which is an exceptional location for boozing.
Zero (cigarettes are highly addictive).

My point is that reality limits how much safer you could make a product. Would it be nice for cigarette or alcoholic beverages to be safer? Yes. Is it possible? Apparently not.

Either tobacco becomes a controlled substance (I am deeply opposed to this given the catastrophic social consequences of prohibition in general), or adults behave like adults, understand the risks, decide for themselves and accept the consequences. Maybe it's because I'm European, but anything else sounds like insanity to me.

By the way, I am not being judgemental in any way. I am an ex-smoker and I drink socially. If people want to smoke (without polluting the environment of others who don't) it's their right, and I completely understand. I used to love it too.
Google is building its own housing (and fighting to do so). We're seeing the return of company towns.

I don't think they're interested in lowering housing costs for the whole valley though.
1) Some languages have tail call optimization and sometimes recursion is the clearest way to express an idea.

2) Requiring a fixed upper bound when iterating a collection of objects is a direct contradiction of the ZOI rule[0]. Most programs should not place arbitrary boundaries on the number of objects they'll operate on. This is better adapted to systems with relatively fixed databases and a predictably low volume of operator and sensor input (i.e. flight management computers, train control systems) more than internet services.

7) "For this reason, most coding guidelines for safety critical software also forbid the use of all ansi standard headers like string.h, stdlib.h, stdio.h" should speak for itself.

9) Is pretty C/C++ specific.

[0] https://en.wikipedia.org/wiki/Zero_one_infinity_rule
Firefox used to have a preference you could set:

security.warn_submit_insecure

When set to true, Firefox would warn the user that the data they were about to send was not encrypted and would be sent over plain-text HTTP.

This setting was removed at some point (FF19, IIRC) and is currently (AFAICT) a NOP; cf. bug #799009, "Remove support for obsolete SSL-related warning prompts" [0]

[0]: https://bugzilla.mozilla.org/show_bug.cgi?id=799009