skysight-inc/HackerNews huggingface dataset:
You're trusting the provider of the program, not the provider of the server. Curl/bash from github? You're trusting Github to provide the correct content; there have been times before where people have been able to spoof other users. Signatures on the package (or the code) would prevent an issue like this.
Sometimes the free market needs a little help, due to the tragedy of the commons [1].

That's why the FCC has regulations on interference created by electronic devices. Reducing interference costs money. The free market punishes extra costs. The situation of networked devices with security-impacting bad features is analagous.

[1] https://en.wikipedia.org/wiki/Tragedy_of_the_commons
There is another way this problem will be solved. (For certain interpretations of the word "solved").

Tort law.

Manufacturers negligently sell defective products in the marketplace. (Reference the litany of weeping by Schneier and others about the sloppy and amateurish software in the IoT universe).

Harm befalls the customer or a reasonably foreseeable third party (oh, hypothetically, Dyn? Or anyone who sustains severe economic damage from a DDoS attack).

Lawsuit against manufacturer, distributor, and retailer ensues. Your favorite contingency fee tort lawyer at work here. No win? No pay.

Win or settle.

Now distributors and retailers will no longer sell malformed IoT devices because they have an economic incentive to not do so.

Or their insurance carriers will raise insurance premiums to cover the risk. Another economic incentive to not sell crappy products that will participate willingly in a DDoS attack.

In short, Schneier misses the economic incentives and the marketplace at work. He misses it because law is not his domain of expertise. Time will bring a lawsuit or two and he will become aware of this.

And we have avoided a Federal Department of Things (Internet) being inflicted upon us. That, I submit, is a boon of immense value.
Vikings, MERs and Curoisty/2020 each used totoally different landing technologies. Amazing they all worked.
It was the first index fund, yep
Rihanna
In Germany, too. A house and the land on which it stands do not form distinct properties but only one, the reasoning is they are physically connected and the house cannot be separated from the land while still being used as a house.

The GDR had in the years of its existence softened this doctrine due to its ideological despice for property in general and their conception of public property (sort of modern fief: delegation of usage rights) in particular. Under this conception it was possible to have separate ownership in buildings. This was more or less a incentive and financing game: let the populace build the buildings out of their own savings, and as long we have not abolished property altogether, they might as well own the buildings.

However the land registration (Grundbuch) normally includes the buildings. This was however handled differently for different types of buildings. Apartment houses were more properly documented, smaller buildings (holiday homes, garages) nearly never. This was a big problem after reunification, because buying a realty, one could not be sure if there remained rights from third parties to the buildings on the realty.

https://de.wikipedia.org/wiki/Volkseigentum#Sachenrechtsbere...
This is exactly how it will balance out. If this passes a threshold such that funds that take advantage of the phenomena will produce a meaningfully higher return than index funds then money will start flowing into such funds balancing out the effect.
Its nearly impossible to predict when someone would find vulnerabilities (or if they have already in secret, Bletchley Park anyone) in crypto primitives and the problem gets compounded we try to use untested crypto primitives such as those highlighted in this article.

AES has been around since 2001 and researchers haven't gotten past 7 of the 10 rounds so that significantly improves my confidence in its ability to not crumble under the most simple cryptanalysis.

Here's an interesting video by the author of one of the attacks on the inner round of SHA-3 explaining why public analysis is exceptionally important.
https://www.youtube.com/watch?v=uT4hrWkbBxM

My point is that though gaining popularity may be good because more researchers may find vulnerabilities but until these primitives are proven its probably not a good idea to use then in any real world application.
Sorry for the formatting:

curl >x
less x
. x
The speed Of the interconnect is absolutely critical. It depends on the problem somewhat, but if you are moving data back and forth cpu to gpu the interconnect becomes the limiting factor very quickly. So much of a limitation that for some problems you might be better of with a cpu or a puny gpu that is on the same die as the cpu.

If you can do everything on the gpu then it isn't a problem but at that point why isn't the gpu your main processor?
Sure. I'm coming from banking (credit cards) by I've also been in insurance, forex and consulting.

I've been a web developer, full stack BI guy and a strategy consultant.
Wholesale Suppliers and All You Need to Know About Them
The movie Fantasia Sorcerers Apprentice was right! All the the household objects will rise and overthrow their masters!
Which sectors are big in London and Glasgow? Wouldn't mind startups either.

I see. Any sites you'd recommend for me to learn about housing in London?
It could still communicate by drawing more or less power...
The time for complaining about xz has well and truly passed. One might infer that the problems with xz are related to the attitude of other developers...

But I dogress. When you create archival packups you use must use error correcting systems. Par is a good place to start.
https://multipar.eu/
https://github.com/Parchive/par2cmdline
Had a conversation with a Chinese colleague after the huge explosion in Tianjin; they were worried that this sort of thing - industrial accidents, spillages, etc. - was happening in China all the time and they wondered why it didn't happen in the west. Of course these things all happened in western countries in the past - My feeling was that china is going through a hundred and fifty years of growth in a couple of decades. It takes an Aberfan, or a Boston molasses flood, or a Triangle Shirtwaist factory fire, to get a country to fix the liability and legal frameworks it needs. And China is going through all those learning events in a much compressed timeframe. Open question whether it's actually learning from these events, too.
Are these gates "regenerative", in the sense that you can combine them indefinitely in theory? Or do they lose power, so that after a few consecutive gates they lose their function?
Kubernetes has the concept of a pod, which is a group of containers that run on the same node. It does indeed solve that problem.

http://kubernetes.io/docs/user-guide/pods/
If it's easy to do and does not require electricity nor electronics then could it be that computers has been created in previous civilization and we are not aware of it yet?
Not in the type system itself, but you could write a lint to forbid heap allocation. This way, you could annotate a function (with e.g. `#[forbid(allocations)]`) to get a compile error when your function (or code your function calls) tries to allocate. This might not be easy, though :)
>We asked both current and potential users what most stands in the way of their using Rust, and got some pretty clear answers:

>1 in 4: learning curve

>1 in 7: lack of libraries

>1 in 9: general “maturity” concerns

>1 in 19: lack of IDEs (1 in 4 non-users)

>1 in 20: compiler performance

>None of these obstacles is directly about the core language or std; people are generally happy with what the language offers today. Instead, the connecting theme is productivity—how quickly can I start writing real code? bring up a team? prototype and iterate? debug my code? And so on.

I don't really see how this conclusion was reached from that data. The "learning curve" is almost certainly a reflection of the language being a little esoteric and the demands of the borrow checker. And "lack of libraries" is partly a comment on the ecosystem, but also partly shows that std is obviously lacking for some needs. Finally, "general maturity concerns" refers to worries that the language or std will keep changing, as is assumed they have not been perfected yet.

Those are the top 3 concerns and to me, both seem to relate directly to the language or standard library.
I'm not an expert, but index funds still purchase the stocks, so when the active investor bought a stock at an increased price, it would increase the market cap and so the index fund would buy some more of it from them.
It would cost $2500 in fees for me to buy a single share of every stock in the S&P500. Compared with $0 + some negligible MER to buy an ETF with the same money.
I'd call that responsible instead of cynical. If you know in advance that an asteroid is about to hit Earth, except the exact location you'd do the same.

In the case of SF, an entire continent is approaching very-very-very slowly.
OkTurtles home: https://okturtles.com/
Probably nothing: http://quoteinvestigator.com/2011/08/09/remain-solvent/
The router could provide password-protected web proxy to access the LAN IOT webserver. Then you've reduced the attack surface to the router.

It almost seems like we need some protocol extensions:

1) Standard auth protocol (not just web-based) for the router to protect the local computers. Some kind of user-and-software-friendly firewall. This could even extend to game servers and whatnot - what if the "shared password" for connecting to a hosted game server had the shared password implemented at router protocol level?

2) DHCP registration on a network should require a name, one that the user was prompted to provide at some point. No more identifying devices on you router by IP or MAC. You already need to provide a name for SMB or DNS, just finish the job and name all DHCP clients. Possibly this should work with DNS in some way.

This way user-friendly logging information can be presented to the user. Without that, routers don't have the critical information needed to tell the user which device is screwing up.

Edit: Google tells me this is already a thing... Sadly, good conformance on providing meaningful DHCP client names won't happen unless the FCC et al start testing IP-enabled devices for it.
In my experience, over-engineering is driven by a fear of refactoring. For whatever reason, refactoring is a process that is both culturally and technically undernourished.
That's certainly an interesting read but if I really care about something I'll usually generate PAR files. At that point, does it really matter what archiver I'm using at the time or should I still be worried?

https://github.com/Parchive/par2cmdline
Why not both? Both preparation and inherent ability are important. I find it implausible that everything can be explained by "mindset." Perfect pitch is a good example, it's a useful ability and cannot really be developed through training. Other factors are more subtle but are also fixed.
I believe his point is that you can't, because "actual skills" need not exist. It might ALL be luck, and outliers will exist. And, their existence doesn't prove anything about luck or the lack of it.
The free market will solve this problem with an existing and efficient tool.

Tort law.

A few wins in court will do the trick. Here is how.

A victim of a DDoS attack sues manufacturers, distributors, and retailers of that product for selling a defective product--the IoT device used in the IoT attack.

As soon as there is a win, the product disappears. Distributors and retailers must now price in the externality of the risk created by the product. It is far easier to take the product off the shelf. Therefore the manufacturer must either make a better product or die.

We don't need government regulation. We just need time. The legal system will do what it is designed to do: assign economic consequences to the right parties.
Index funds still have an input on the corporations.

https://about.vanguard.com/vanguard-proxy-voting/update-on-v...
Swift still has automatic memory management. It may not have a tracing GC, buy that's not super relevant from an ergonomics perspective (except that potential cycles require extra work/annotations).
The other thing to keep in mind that index funds slice and dice the market in many different ways. The classic "Index 500" fund is a market-cap weighted fund. But there are many other types of funds. For example, Vanguard has 62 different index funds. And there are fundamental weighted index funds which, "...may be based on fundamental metrics such as revenue, dividend rates, earnings or book value". (http://www.investopedia.com/terms/f/fundamentally_weighted_i...) There are funds which take different selections of the market (top 1000 stocks or top 100 stocks, etc).

So somebody might purchase an index fund and think they are investing passively, they are really actively choosing a passive strategy.
You're not the only one who finds JS and its ecosystem disgusting.
I love rzip but it is important to note that it is not a stream compressor. So it is unsuitable for most of the use cases of LZMA2 which can compress data on the fly or have data appended on the end of a file at a later date.

So rzip is probably excellent for archival situations (not counting any flaws the algorithm may have) but not so great for things like compressed tarballs (which are meant to be appendable).
I am working on a multiple large reactjs project for more then a year. You need to think in terms of components.
But in the event of an extreme rally, your picked stocks can make you a huge return. Fast. Then you cash out and play it safe.

Risky, but this is why people try to beat the market. This is the allure of gambling.
GitLab 8.13 Released with Multiple Issue Boards and Merge Conflict Editor
I started doing push-ups every day. I hate push-ups and I am not very good at them, to make it easier I do them on an incline and it has helped tremendously with my shoulder and neck pain.
The part where you repeated Verisign's mistake in breaking a fundamental protocol.

NXDOMAIN. Kind of a thing, and important to protocols other than HTTP.
"Bugs that can be founderstood at compile time" is a complicated category, since it depends on how much you lean on your compiler to help. For example, wrapping primitive types in semantic wrapper types can be an easy way to catch errors where you mix up parameters. And with a sufficiently powerful type system like Idris you can theoretically catch literally any possible bug at compile time.
It gets easier and easier to beat the market (due to less people trying) until eventually investors can make enough money doing that to earn the fees they charge for trying. There's an equilibrium when that happens.

EDIT: Or, to put it in EHM analogy terms, the number of people looking for loose change on the sidewalk will go down until there are few enough to support themselves from the money people actually drop.
That's the argument from A Random Walk for index funds: even if such skills exist, they're indistinguishable from luck, therefore one can't make an informed choice of active fund.
I also don't think library maturity is necessarily the only problem that makes working with libraries difficult at time. You can get burned pretty easily by someone not having e.g. Send + Sync on an essential library data structure. (Though maybe there's a way around it other than forking?) That metadata ends up being very important
They may also play version of martingale strategy where they pay for higher returns now with increased losses if some rare event in the future happens. This is how very successful hedge funds can beat the market for decades. There is hidden risk somewhere and you better jump off before it is realized.
Here's an old article with lots of numbers and performance graphs:

http://blog.zachbjornson.com/2015/12/29/cloud-storage-perfor...
It's impossible to perfectly distinguish them. Anyone that seemed to be skillful could just be incredibly lucky.

But you can get determine a likelihood that they are lucky by monitoring their performance over a long time / lot of games. It's just that if you are evaluating a whole lot of people looking for a rare skillful person, you need a whole lot more time/games to be sure they aren't lucky than if you just had one person to evaluate.
As a recent immigrant to Finland the population system there is pretty fascinating. Seeing how many men/women share my forename was pretty cool, for example.

One of the immediate perks was moving house - I updated my address in the population index and suddenly all the companies that bill me and send me mail had new details. No extra effort.

(Of course then I had to update my contact details on domains, and online stores outside Finland, but it was a great timesaver.)
Managers are always suspicious that engineers are doing the wrong things. Living under this cloud is just part of being an engineer.

Granted, my experience is more with hardware than with software, but getting a design "just right" can be costly in analysis and testing, and there's a palpable concern that if you aim low rather than high, a substandard product will get pushed out the door. It can be exponentially more costly to correct a weak design late in a project than to over-design it early: Subsystems and schedules become more inter-dependent, the closer you get to launch.

I can give you a good design in six months, or a bad design in twelve. ;-)
Join 2 CSV Files by Go and LuaJit
So whose preventing you from only using the same basic structures when embedding it like JSX, with Javascript? I don't see why learning a different syntax for the templates improves anything you say. The for loop does not look any better/easier just because you slightly change the way you write it, but you now depend on yet another language.
Over Engineering Is Definable, and Reducible
Private individuals can be members of political parties and this is not something that should end up in the public domain. Really, this is about as easy to understand as it gets, in fact in many countries such party memberships and who you vote for is kept extremely secret to make sure that votes can be bought and/or to make sure that there is a place for 'unpopular' parties and candidates.

It's a cornerstone of democracy. Some countries take a much less serious approach to voter registration but especially in Turkey such lists are social dynamite and the release of those lists was absolutely uncalled for and irresponsible.
Typically there is a three way way split: college, dept and prof/student.
I know students who drop out rather than give up too much to the university.

I was a Stanford grad student in the 1980s when these policies were still being worked out. There were cases of grad students being abused by the commercial interests of their professors before the university clamped down. These abuses included postponing the publication of results which could delay graduation or an academic career. Now profs and students can only spend 20% of their time on commercial interest or should take a leave of absence and leave Stanford facilities if they want to work more. The just retired Stanford President did such when creating his RISC computer company MIPS. Also you can only delay publication one year.
It's in Assange's interest to let some people believe he has been killed.
Unrelated question: was there a reason you swapped the iterator and container (x and y) in your angular example compared to the others? Just to keep 'x' before 'y'? It confused me a bit.
If you miss any necessary APIs, contact the Mozilla folks working on the Firefox implementation of WebExtensions (e.g. via bugzilla.mozilla.org). They are usually pretty reactive to (sensible and well thought out) proposals to extend the API capabilites (and reduce the gap to their other APIs). If you need any help, drop me a message @fbender_dev on Twitter or @fbender on Github.
Info on Opportunity watching for Schiaparelli EDM: https://news.ycombinator.com/item?id=12763583
I recall someone commenting that most non-fiction books have only 15 minutes of true comment. The rest is commentary and persuasion.

I used to feel awful if I did t finish a book because the author created it with a certain vision. As I get older I've realized how limited my time is, and I am more content with a quick skim for many.
Shutting it down or not is up to those that run WL, I'm fine with them continuing to leak whatever people send them, in the meantime I'd love to see a serious competitor.
I usually try to argument with them, that's what a discussion is about, a exchange of argument and a test of there validity. Everything else, is just bubbling oneself into another ideology.
> if you're using an https url then you should be ok

You're trusting the server in this case, not the contents being provided by the server. There's no way to verify that the contents attributed to eridius on github are the same contents that eridius actually put up there.

Github in particular has been shown to have problems with spoofed users.

Let's go one step further. I have a `curl | sh` script for you to execute to install Docker. Just run:

curl -fsSL https://get.docker.com/ | sh

Oops. That was actually get.rekcod.com, with a RTL unicode character embedded. Or a unicode C which doesn't map to the ascii 'c'. Or I am able to mitm and strip the TLS. Or...

The vulnerabilities go on and on. Using only HTTPS, you have no way to prove that the code you got from get.docker.com is the code that the docker engineers intended for you to use.
tl;dr: It is the only way the troll can participate in the greatness/fame/notoriety (as the case may be) of the trollee.

FWIW, YMMV.
> Rust was absolutely designed for programmer productivity. Source: I was one of the designers.

If you mean productivity as "memory safe and no null pointer errors" then Yes, Rust is productive compared to C,C++ or even Go. If you mean productivity as "ease of use" then no, Rust is not easy to learn or to use compared to Go.
React can be used without JSX like Mithril is doing. In fact, pretty much all the JSX compiler does is convert those to React.createElement()..
I'm not saying Vue is better or worse, having never used it. And you bring up some good points. But I had to chuckle a little internally because your post could almost be a case study of pg's blub paradox article.
The Real Cause of the Financial Crisis: An MIT Blackjack Team Perspective
Why wouldn't they do the merge now instead of 48h before release, so they have more time to see if there's any problems with it?
It's still NIST compliant crypto on the outside regardless of the inner contents. Assuming NIST(GOST(plaintext)), NIST would be terribly broken if using GOST ciphertext as the payload weakened the security.

It's crypto 101 that, given a ciphertext without the key, an algorithm's correct input should be indistinguishable from random input of the same length.

I'm shocked that you think the plaintext contents would have an affect on whether or not something is NIST compliant.
Solving the Student Loan Crisis with IQ Tests
Scientific paper written by iOS Autocomplete has been accepted for a conference
You might not see any connection, but it is nonetheless how people use the word. Human language is mainly about humans and their relation to the world.

If your black box contains Einstein, then yes, it's a creative act. If it contains an artificial consciousness, then yes, it's a creative act. But if it contains infinite monkeys typing randomly into LaTeX producing infinite physics papers, then no, that's not creativity, just the generation of novelty.

I could call a red rock-face "angry", and I could call a mountain lake "tranquil". But that's projecting emotional states onto the external world. Calling dice creative is projecting a cognitive state onto the world. Sure, it works fine as metaphor. But it's just analogy, not homology.
Bowling Alone: America's Declining Social Capital [pdf]
This is an interesting approach to get past NAT: https://thehackerblog.com/sonar-a-framework-for-scanning-and...