skysight-inc/HackerNews huggingface dataset:
Well for one, systemd hooks to a large number of functions/subsystems that used to be more isolated. Logging, udev, dbus, churn, networking functions, etc. So it's a bit of a judgement call to say it has a larger or smaller attack surface than separating the functions out. I don't know how to really quantify if in the end it ends up more risky one way or another.
The OKCupid data release fiasco
>Scale these days is a solved problem, there is nothing they are doing scale wise that I can't do in a couple weeks using AWS.

Excuse me for being blunt, but this to me seems like a statement someone would make who has never worked at this scale.
Related, in a general sense (and with some of the comments here in mind): http://edwardfeser.blogspot.com/2012/03/scruton-on-neuroenvy...
once again, evidence how completely broken the ca system is. let the blame game begin.
Sohbet: sohbet odaları
"So if there's no rules mentioning an [a] attribute in the page, el.setAttribute("a", ...) will generally not do anything."

That's true in general but there are exceptions as usual. Changing @href may trigger not only [href] rules but also :link ones. And :link rules are always present at least in default style sheet. @value triggers :empty. And so on.

But if someone in some library in galaxy far far away (small library used by your application) will add that [a] rule then magically you will get a spike on innocuous el.setAttribute("a", ...) calls in your code.

That's one of points of having transactional yet explicit DOM update mechanism. We have jQuery, Angulars, React, Ember, Vue, (you name it) that definitely need such thing. Sites/webapps that do not use one of those are quite rare these days.
In all fairness, Obama's use of a smartphone was unprecedented. I read (but cannot find a reasonable source now) that Obama's Blackberry was tethered to a private base station, not any kind of public network, cellular or otherwise. So "secure smartphone" is a term that really means "secure infrastructure".

That infrastructure simply isn't scaleable.

[Edit: See this HN comment for sources. https://news.ycombinator.com/item?id=11306380]
Imagine person A invoices person B for services delivered. In such case, it is always possible to get A invoice C and then C invoice B. C would just be a middleman. There is nothing wrong with that.

Then, you could easily "chainify" the concept: A -> C1 -> C2 -> C3 -> B

Now you turn C1 into a reservoir. It does not pay out to A, because A prefers to save his revenue inside C1. Therefore, A never gets taxed on income that remains in C1.

Also, whenever reasonable, C2 and C3 pay for A's spending. That money does not hit A either, and not even C1. Therefore, A actually needs little actual money to be paid out to him. His expenses are taken care of by C2,C3, ..., while his savings are held up in the C1 reservoir.

Even though B could pay millions for A's services, in terms of taxation, A makes almost no money at all. The money remains legally stuck in the C chain. Even though A is a real person, the C chain is not. It is a chain of virtual persons: "incorporations". They used to exist only on paper. These days they only exist on a computer screen.

Moving nodes in the chain to another state or to countries, pretty much amounts to just updating a field in a database. Depending on what you fill out in that database field, you pay more or less tax. Hence, the reason why they consistently fill out the cheapest choices on the screen.

In other words, there is never a valid reason to pay income tax for a "chainified" income stream. Therefore, income tax is in reality not a tax on income but on the inability to "chainify" income.
Text in Senate Bill Would Allow Warrantless Access to Email
Awesome, thank you. My friend who uses Linux was interested in getting something like Qbserve there.
It's a POLA violation. Documenting this gross violation of expectations is not a sufficient apology.
Türkiyenin En kaliteli sohbet sitesi
"Institutional racism,” also “Systemic racism,” is not a vague, bogeyman term, it has a specific and objective meaning. It can be measured and has been measured, repeatedly.

In almost every area of American life, there are measurable effects. Blacks are more likely to be arrested than whites for the same crimes. They are more likely to be sent to prison and to get longer prison sentences given the same criminal records and the same circumstances.

As is often quoted, resumes with black-sounding names get far fewer calls for interviews than resumes with white-sounding names.

These are facts, and on Hacker News we prize facts. As it is so often put when talking about things like creationism, “You are entitled to your own opinions, but not your own facts.”

---

What I am finding more and more is a certain type of rhetoric, I will call it “Racism Denial.” It works just like Creationism Denial and Climate Change Denial. The denialist does not approach these discussions with any good faith attempt to discuss the issues or to weigh the factors on display.

The denialist has an agenda, and the agenda is to derail progress, to disrupt any and all attempts to fix what ails the system.

This is because the denialist fears that change will hurt them personally. The creationist denies evolution, because accepting evolution means turning away from the creationist God, which means letting go of the religious fervour that they have adopted as a core part of their identity.

The climate change denier denies climate change because accepting climate change means another step towards ending certain industries and jobs. They fear the loss of their income, the dissolution and decay of their coal mining town, the loss of jobs making gasoline-powered cars and a transfer of economic wealth to places like California where they make clean electric cars.

So let me ask you: What do you personally fear from people nodding and saying “Yes, there is systemic racism in America?” What do you think you will lose? What bad things will happen to you and to America if people stop pretending there is a problem and stop blaming blacks for everything that happens to them?

Why are you trying so hard to pretend there’s nothing going on?
I think you vastly underestimate Snapchat's scale and vastly overestimate AWS out-of-the-box scaleability.

Someone like Snapchat periodically surprises GCP with millions of QPS, something AWS would deem akin to DDOS. With AWS, you'd need to carefully setup infrastructure that statically accepts such scale. You need to plan, test, deploy resources, measure, etc etc. Snapchat has to do absolutely 0 of that - they deploy code. This is a major difference between Google and AWS - with one you can setup scale, but you pay for it, and with the other you get scale as part of your service, out of the box.
I always assumed that it was to completely kill it and that resistance was a side effect of not killing it...
Funny enough, State Department did in fact have issues with clintonemail.com mail ending up in Spam folders! Check the just released State Department report.
Afaik something like xinetd forks and execs a copy of the daemon for each connection and communicates over stdin/stdout.

This can work for simple services like sshd which fork for each connection anyway, but would never work for something like nginx or redis.
YouTube Content ID and equivalent takedowns of content on other services (including false claims, videos shut down because of incidental music, or actual use of content in a transformative way). Remixers/mash-ups. Romhacks/mods/etc. "Abridged series" (of the humorous variety, not literal abridging). Fan works of all kinds. The entire emulation scene. Tools for reading and rescuing content from proprietary file formats. Drivers developed through reverse-engineering to figure out how the hardware works. Projects (both Open Source and proprietary) potentially threatened by the previous ruling on APIs in this exact lawsuit. The old SCO lawsuit and all the time and money it wasted, plus the harm done by the FUD. Any project that has ever had to defend itself over "fair use" in court, whether successful or not.

That was about 5 minutes worth of examples; plenty more where those came from.
I wonder if antibiotic resistance will be the reason that people move out of the cities back to rural areas.

You can't get sick if you're not near anyone else.
Simple threaded web server in C using FastCGI
But it's also an opportunistic crime at which you'd be caught almost immediately. Supposing you rob or otherwise assault someone as an Uber driver, you can:

a) Kill them. First thing they do is check his phone logs. Oh, he called an Uber? Let's talk to that driver.

b) Rob/rape/etc them. Uber has perfect records of the identity of their drivers and who got in which car. You will be caught or at the very least banned from receiving fares instantly.

These harms are completely self-limiting. You get one shot at a crime, at best.
Self-Driving Truck Acts Like an Animal
XESS is biased toward the segment of the market they play in which is centered around computational applications where having a micro on board is usually desirable. There are many more places where simple glue logic is needed and a small, cheap FPGA/CPLD fits the bill. One would hope that Altera's (and possibly Xilinx's) new masters won't fuck this up and shutter their low end devices but that doesn't mean there won't be demand for them into the future. People with a need for these types of FPGAs aren't XESS customers so they are blinded by the limited scope of their own business.
UNIX was designed to run background processes and do offline computing. I log into multiple remote systems every day and connect to my ongoing tmux sessions in other countries. This isn't exactly an unusual use case. Banning this is a big downgrade in functionality.
> I really dislike the idea of having one project handling everything on a box

Whatever you do, don't switch to a BSD.
> that argument is completely inapplicable to things like power plants

Actually, it's not unheard of for waste heat from power plants to be used as residential heating.

https://en.wikipedia.org/wiki/Cogeneration

Some of the nordic countries use local power plants to create municipal steam for heating homes, I believe.
This is just an announcement of an announcement. We can wait for the real thing.
Florian Müller is a German lobbyist, the writer of the blog FOSSPatents, and a consultant for Microsoft and Oracle.

https://en.wikipedia.org/wiki/Florian_M%C3%BCller
If you have the money to play the odds like that then more power to you.

I just don't like the acknowledgement that most of their investments will fail.
Otherwise, it is acceptable and in the best long term interests of the company.

Maybe the best long-term interests of the company aren't aligned with the best long-term interests of our society. If, hypothetically, the market took over, and drove racial equality/diversity in a direction such that we almost literally ended up with a white male overclass and everyone else their servants/slaves, would you shrug and say "well clearly white males are just better for the long term interests of the companies"? Or would you wonder if there were maybe some non-market-based factors at play...

"The market" doesn't magically solve all problems. It's not a simple matter of companies making non-discriminatory hiring decisions. As of now, the average white candidate probably is more qualified than the minority candidate, because of a complex web of social factors and experiences tracing back to birth. So they would always get selected by "the market," creating a feedback loop leading to the scenario I described.

The market is definitely not going to provide equality of opportunity. If that's something we care about, we have to actively push things that direction.
I used to work there a while (5 years) ago, and I don't think you understand how this company works.

There are internal groups where features are discussed and debated all the time, and even all hands Q&A sessions with Zuck (weekly IIRC) where sometimes hard questions are raised.

Someone amongst the many engineers with access to the repo will eventually end up spotting shady code if it exists. They might raise this with a colleague first, or in an internal group, and the matter might even bubble up to the Zuck Q&A if it's intentional and particularly controversial.

This level of internal openness is unusual at this company size, and since there are people joining & leaving all the time (including interns who AFAIK have the same level of access to the code) it would take just ONE disgruntled whistleblower to ignite a scandal that the press will be instantly all over like piranhas smelling blood, this being Facebook.

Therefore, doing evil covertly like you suggest just isn't worth the risk for FB, period. Not happening, won't happen. When you see headlines like "Is Facebook eavesdropping on phone conversations?", Occam's razor is always your best friend.
Because people buying homes tend to not live alone. And 150k is pretty middle of the road for established tech workers in SF, so in reality you're looking at two people making 200k each.

400k/yr can buy you a home in the Bay Area easily.
> That makes Oracle's win on the subject matter issue basically a pyrrhic victory for anyone looking to protect their APIs. They're protectable, but can't be protected in any realistic scenario.

Good. The CAFC ruling is indefensible, like most everything else that emanates from that court. If nothing else this ruling strikes me as a workaround for having an appeals court that is bought and paid for by special interests. For copyright and patents, the courts are so heavily stacked in favor of major rightsholders, and so abused by them, that for those who favor copyright reform it's probably well past the time to hope for rightful justice under the law and better to adopt a "victory at any cost" stance, much like our opponents (i.e. Oracle, etc.) already do.

If Google weasels out of liability because of some lame fair use defense that probably "technically" shouldn't pass muster, I can hardly give a damn given how often the law is twisted in the other direction already.
Phage therapy is super interesting, but there are a lot of technical problems. If I ever leave software engineering, it'll be to go back to mucking around with phage.

Immune clearance: The immune system really enjoys soaking up phage. Blood titers drop stupidly fast. Maybe we could flood the colon with a phage-bearing solution to handle GI infections, but in general I'm really skeptical. There was a paper ~8 years ago describing serial passages in rabbits to enrich for immunocompatible phage. Don't know if further work has been done here.

Specificity: Phage really, really like their hosts. I had a strain of Phi X174 in lab that would simply never infect wild type E coli. To deploy phage effectively, you need to culture whatever it is that you're after. Next you'd want to infect the pathogen in culture and pass your phage for O(many) generations. A lot of human pathogens are just miserable to grow.

Efficacy: Antibiotics are just better at killing bacteria (resistance aside.)

Regulatory: You'd need to convince the FDA to approve a viral cocktail that is potentially going to kill the patient through anaphylaxis.
UBER ATC is disguising research as fake job interviews?
From what I can tell skimming their papers, no. Their technique really is based on solving a PDE to fill in the gaps in the image. Neat idea and I'm a little surprised that it works so well. Compressed sensing relies on an equivalence between a discrete and a continuous optimization problem under very specific assumptions, which allows the sparsest possible solution to an underdetermined linear system to be found. In this work, there's no optimization, so no compressed sensing.
Actually, that attitude is exactly what one receives from the systemd crew. They, and only they, know what you want, when you want it, and they always know better than you do.

That's why the systemd crew generates such great hatred.
I wonder how suitable this technique would be for compressing video, since it seems to work on volumetric data.
Your example doesn't make sense. Keep in mind that an out of bounds array access can cause a lot of problems; in the best case, it would cause a segfault, and in the worst it would allow for code injection. So there isn't really a case where accessing an array out of bounds makes sense. That's where the idea of "expected vs unexpected errors" comes from.

Another way to think about it is that some errors can be handled and some can't. For example, most of the time you can't "fix" a segfault, so it makes sense for that to just crash the program.
'The details of your involvement will be gruesome' if you continue suing us
NASA Space Apps 2016 Winners
If some other media outlet (say NY Times group) was being sued into the ground by some billionaire, there would be a huge uproar.

But because this is Gawker (a universally media-hated media outfit which regularly and cheerfully exposes the corruption, decadence and double standards of regular media), nobody cares.

Like it or not, they have played an important part in exposing and shining a light on Silicon Valley shenanigans, incompetence and plain criminal mis-management.

I sincerely hope they win this case, especially as it is being used as a stalking horse.
They're filing for class action, and the class of patients who got bogus tests is pretty big....
I should've clarified, I was referring to large media organizations. An independent media organization that has no viewers is not terribly useful. If you know of any independent online media organizations approaching the scale of Gawker, let me know, I'd love to hear about them.
LinkedIn is doing a pivot
> or ... Cygwin

Or not, because windows will kill all processes that are part of the users session when they log out.
JPEG is the go-to format for showing your compression is better at high compression rates because once you get past a certain point you don't have enough data for coefficients and JPEG ends up storing most of it as flat 8x8 blocks.

It's not representative of the performance of JPEG becasue You typically don't encode JPEGs at that bit rate.

It's basically taking advantage of the fact that JPEG dips first.
http://article.sapub.org/image/10.5923.j.ajsp.20120205.04_01...

Also be wary of things that report compression rates rather than bits-per-pixel. You can get the same image quality at 200:1 if you start with 48 bit colour, The bits per pixel would be the same but if your original data is excessively precise you can throw a lot of it away at no perceptible cost.
The refutation is they tried again after a failed attack, but not the successful one.
I'm an American born to a Brazilian father and American mother and I can confirm that racism is more than alive and well down there.

At least where the paternal half of my family is from (the northeast)
Maybe. Which is also sad.
Is a 100 million 'scaling up' these days?
That's a lot of salt. I can't take seriously people who take tumblr seriously. Maybe I'm lucky.
> So many things to keep in mind, so many dependencies, so very many points of failure. If just one of these libraries is abandoned, or has a breaking change, your entire development environment is dead. Is this the current state of frontend web dev, or are these guys just overdoing it for the sake of the tutorial?

This tutorial is trying to guide you over the initial hump with the tooling by letting you hit the issues you'd hit if you were learning it on your own (like dependencies which need tweaks to your Webpack config to work properly like sinon, enzyme, moment...).

They _could_ have handed you a completely pre-baked config and got to Hello World in step 2, but you wouldn't have learnt anything about the tooling.

In terms of a development library you depend on being abandoned or broken, I've extracted my React development environment out into a separate npm package [1] and it's still using Babel 5, auto-prefixer loader (which is deprecated in favour of using PostCSS directly) and is working around every version of babel-runtime v5 after 5.8.29 containing a broken version of an important module. By pinning your dependencies, you can keep using old or deprecated versions of things until you're ready to upgrade, and by managing development tools in an external module you can upgrade your projects when you're good and ready by bumping a version number.

If you do that, starting a React project (or any other project which gets tool-heavy for apps of any size) can be a 1-step proceess you can have an understanding of the tooling, and you have a way to keep it manageable over time.

[1] https://github.com/insin/nwb#nwb
It would be interesting if browsers started stochastically rejecting their certificates. Maybe only a few percent chance today, so a simple reload will solve. Prudent sites would see the writing on the wall and migrate away. As time goes on, the pain ramps up.
More likely that we'll start seeing bleach and ozone being used in hospitals to clean again. Probably radiation too.

I know that bleach is used, but hospitals used to smell of the stuff.

Amputations are going to make a comeback big time.

Its going to be interesting if you can't go into surgury for fear of getting post op infection.

This will be interesting to watch.
I think people are upset because we're creating a lot of technical debt here. Every new "feature" we add creates a larger learning curve, makes a system that much more complex, and adds more to our maintenance costs. A simple and modular system that allows the user to combine easy-to-understand-parts in a succinct fashion to achieve functionality that __meets their requirements__ usually is superior to monolithic one-size-fits-all solutions. In short, composition generally is preferable to monoliths (after a certain point in complexity.)

I think most of us agree to this, and I haven't said anything we all don't already know. We just all disagree where that complexity tipping point is, and that's why some of us hate systemd and some of us don't see the problem.
A linearized network protocol is not an API. That distinction is very clear. Read the Microsoft protocol specs. They say nothing about API's used to send/receive the protocol - only how the protocol elements are encoded on the wire.

The API's that Samba uses to access that protocol are nothing like the Windows API calls (and are a completely independent implementation).
What evidence do you have that "we know this to be false"?
Yeah, I need to do that. For the moment, use this instead: http://www.digitalmars.com/articles/b89.html
If more people knew how to program wages for programmers would drop and you could hire more of them. I wouldn't mind having 2-3 more programmers right now.

Even if you're right that no new businesses would be created by educating people which is ridiculous, we would employ more people because they would be cheaper.

Also if wages drop for a career it is less risky to start your own business because the potential wages lost are reduced.

I mean, just about every industry is short on qualified people as their salary approaches $0.
If South Africa hadn't mandated that companies have a certain percentage of blacks in senior positions, then the economic and political power still would have been heavily lopsided towards the white minority after apartheid ended. Things aren't golden and fantastic there now, but it's still more equitable than it would have been without that affirmative action.
> the way anyone at the scale is on-premise or on AWS/Azure

Can you expand on this? How/why would anyone developing a potentially high-traffic app have to worry if they are e.g. leveraging AWS fully? How does that compare to google cloud?