skysight-inc/HackerNews huggingface dataset:
This matches my experience with react-router. I use it in a few side projects, and I have the feeling that there's been a lot of "design-thrash" - every new release seems to bring a new interface and new ways of doing things, without much real benefit.
Google cache: https://webcache.googleusercontent.com/search?q=cache:mPkna3...
I've been supporting hydrological data collection for over two decades. When I first started in the early 90's, there was no clear defined trail on 'how to do it'. I learned over time what works and the right way to do it. I'd like to make a few comments.

You asked about organizations that engage in 'citizen science', I would start with the NOAA Co-ops program https://www.ncdc.noaa.gov/data-access/land-based-station-dat... . This would give you the basics. Another route taken is through a college based program. http://iowafloodcenter.org/projects/stream-stage-sensor/rive... As you can see, Iowa has a program that is on the lines of what you are looking at.

You mention about cheap 'disposable' sensors. Truth be told, no reliable sensor is truly cheap. In sensing, we look at repeatability, accuracy and resolution. In the design of a sensor we also look at interfacing and field calibrations.

Field data collection systems are comprised of several parts. Power, Sensing, Data Logging and Telemetry. It's interesting, different vendors of this equipment take different approaches. Everything revolves around the abilities of the data logger. Let's look at several:

Hobo: http://www.onsetcomp.com/products This is a pretty good company. The sensors have good accuracy. The products are reasonably priced. However, you are locked into their products and limitations. I've seen Hobo used by students in course work.

What does the USGS, USACE, NOAA and BUREC use for data logging? They use capable data loggers that can accept SDI-12 and ModBus based sensors along with Analog based sensing. CS: https://www.campbellsci.com/dataloggers and Sutron: http://www.sutron.com/product/xlite-9210b/

As brought out in this thread, Telemetry is the weak link as the trade offs are range verses bandwidth verses data charges, etc.

The notion of Real-Time data is also a factor. Is Real-Time 'right now', every 15 minutes or hourly? All play a factor in telemetry.

@RiverKey2640
Sounds to me that more effective police cooperation could be good to.

For example here in Norway we have, as I understand it, bilateral agreements that allows police officers from the other Scandinavian countries to enter Norway for search end rescue, and in some other cases if it is an ongoing situation. They may also request limited police authority in Norway by calling the local head of police (a relative quick and informal process).
This post is confused. Employer-sponsored healthcare is excluded from both payroll and income taxation which makes it very attractive for employers to offer. The author doesn't understand how marginal tax rates work. Only incremental dollars are taxed at the higher rate so it's not like you hit some taxation cliff. If health "insurance" really was "insurance" it really would be a "bet". Instead, it's become more of a payment plan with an insurance component. "Real" insurance is now called "catastrophic insurance" and is dying in the US (I think Obamacare basically outlaws it).
I know it's an area of some debate, but at least to me, greenlets are easier to write and understand than callbacks, by an order of magnitude.

Greenlets work especially well with Python's "with" statement. You can have a database pool like this:

with (yield from pool.connection()) as conn:
users = yield from conn.query('select * from users')
for user in user: ...

Now your database connection is only locked up inside the "with" statement, and the whole thing is asynchronous even though it's written in a synchronous style.
> TL;DR

You missed a good, interesting and thoughtful piece.
I'm thinking it should be pretty easy to get datagnan to work on one of these?

http://makezine.com/2015/09/24/the-9-computer-is-shipping-to...
Humane Offices: SAS
There's no information on the page about what it does, but it looks superficially similar to Mozilla's Focus.

Why should I (or anyone) use this and not Focus?
Forget the coal, make methanol from water and co2.
I'd gladly pay the increased tax rate if I didn't have to deal with all the BS that surrounds using health insurance; in/out of network, deductibles, companies trying to get out of paying, etc.
> so they take no risk of paying taxes on something which might be worthless

If a the time of a liquidity event the stock is worth less than an employee's strike price, they'll still be underwater. They'll either owe the loan back (the difference between the strike price and exit valuation) or the loan is forgiven and they owe income taxes on the forgiven debt. So there's still risk of owing tax on equity worth less than the current valuation at the time of their offer, right?
How to maintain a fascist state and get away with it while doping your children into oblivion.
EDIUS Pro 7.50 Full Version Crack and Serial Number Download
Beliefs Grounded in What Matters
An odd thought, but perhaps the decline in editor numbers also has something to do with an increase in the number of wikis in general, mostly aimed at specific audiences and about specific subjects. Back in the early/mid 00s, Wikipedia was the site you'd contribute to if you wanted to write general encyclopedia entries about something that's now seen as fairly niche (like say, a certain TV show, film series, game franchise, etc), and from there you might become interested in editing other pages on less specialised subjects.

But now, thousands of wikis exist, about every subject under the sun. Many of those are very popular, have more welcoming communities, etc. So people don't join the general site any more. If they care for say, Star Wars, they join Wookiepedia. If they care for Pokemon, it'd be Bulbapedia. Or one of the many others listed here:

http://tvtropes.org/pmwiki/pmwiki.php/Main/TheWikiRule
OP's point (I'm guessing) is that transmission is the problem with remote generation like this. Production of liquid fuels would probably be better than the enormous cost of building transmission capacity and the associated VAR and resistive losses.
A taste for makers
Oh but this company pays annually and you got hired in January. Sorry ;)
I think the main opposition to single payer in the USA is that it's counter to some of the bedrock principles the country was founded on, such as freedom, independence, limited government and personal responsibility.
I'm skeptical of this as well, and while I had no problems with react-router on a side project, I have misgivings with the router being coupled to JSX - IMO, this is an unnecessary coupling of what should be service logic to components.
>By that time, your real problem is simply that you've stopped breathing, which turns out to be a big deal.

With some training holding your breath for 3 minutes is doable for anyone, and the record is something like 8-9 minutes..
Instant Backlink Builder to your website.Create free backlinks
I don't like her analogy in which she compares solar panels to smokestacks. As she points out, smokestacks were not a complete solution to air pollution because they merely moved the problem somewhere else. Solar panels are in no way comparable in that respect. The analogy only works if you consider energy production to be itself a problem.
Fabs are very expensive. You can see numbers ranging from 4 to 10 billion dollars each. Those are the fixed costs that you now need to spread over production. It looks like Nvidia does around 20 million chips a year. If a $4bn fab was useful for 4 years, then those fixed costs work out at $50 per chip!

If you make other people's chips on the same fab then the per chip costs go down, assuming there is spare capacity. The economies of scale really do help. Which is why there are a few foundries who do most of the chips, and those foundries can spread the costs over a large number of chips including later ones that don't need the newest process. For example Intel is known to do their CPUs on the current process, while doing the chipsets on the older processes.

In other words, work out what set of numbers would make sense, and you won't be able to find any. New processes keep getting more expensive, and competitors adopt them too, so you have to sustain your current fab as well as the work to do the next generation one. This requires a lot of available money.

Don't build a fab unless you are sure you can use almost all its capacity for the next several years.
Didn't he abandon the whole idea of playing with neuroscience, dropped out again, and went on to work at Twitter?
"I tried once or twice to edit articles but was quickly rejected by editors that usually believe they sort of "own" the content."

I have experienced this as well. It is difficult to believe and truly inexplicable, but there is some perceived status related to editing articles and making contributions to wikipedia.

It is very safe to generalize the young, white, male keyboard commandos who are staking out their turf in this way.

In the meantime, actual adults with real contributions to make (and normal, grown-up lives to lead elsewhere) cannot do so. In response to a child comment, below, No, no I will not learn to play the game and learn the tactics needed to bully my edits through.
I have had the exact opposite experience with machine learning and statistics. In my experience, those who come from the 'statistics' side tend to use constructs, like null hypothesis significance testing, which are not consistent even from a theoretical point of view. And further, when they use them, they do awful things like p hacking, or using a direct comparison of t-stats as a model selection criterion, which are further rife with theoretical problems, not to mention lots of statistical biases and so forth.

I find the machine learning approach is far more humble. It starts out by saying that I, as a domain expert or a statistician, probably don't know any better than a lay person what is going to work for prediction or how to best attribute efficacy for explanation. Instead of coming at the problem from a position of hubris, that me and my stats background know what to do, I will instead try to arrive at an algorithmic solution that has provable inference properties, and then allow it to work and commit to it.

Either side can lead to failings if you just try to throw an off-the-shelf method at a problem without thinking, but there's a difference between criticizing the naivety with which a given practitioner uses the method versus criticizing the method itself.

When we look at the methods themselves I see much more care, humility, and carefulness to avoid statistical fallacies in the machine learning world. I see a lot of sloppy hacks and from-first-principles-invalid (like NHST) approaches in the 'statistics' side. And even when we consider how practioners use them, both sides are pretty much equally as guilty of trying to just throw methods at a problem like a black box. Machine learning is no more of a black box than a garbage-can regression from which t-stats will be used for model selection. However, all of the notorious misuses of p-values and conflation over policy questions (questions for which a conditional posterior is necessarily required, but for which likelihood functions are substituted as a proxy for the posterior) seem very uniquely problematic for only the 'statistics' side.

Three papers that I recommend for this sort of discussion are:

[1] "Bayesian estimation supersedes the t-test" by Kruschke, http://www.indiana.edu/~kruschke/BEST/BEST.pdf

[2] "Statistical Modeling: The Two Cultures" by Breiman, https://projecteuclid.org/euclid.ss/1009213726

[3] "Let's put the garbage-can regressions and garbage-can probits where they belong" by Achen, http://www.columbia.edu/~gjw10/achen04.pdf
America (disclaimer: I'm a US citizen, born and raised) has this delusion of rugged individualism, that everyone should pull them up by their bootstraps. In reality, everyone who is successful is simply taking advantage of those who came before them, and shared infrastructure (both the physical an economic types).

I don't see Americans adverse to Medicare, which is essentially single-payer for anyone over 65. Why does being under 65 mean you should die in the street without healthcare?

Single payer is cheaper/more efficient than our current system. We just need to find the political will to implement it, and cut the legs out from anyone attempting to stymie that change who is currently profiting from the status quo.
Well, the US has far more citizens killing other citizens than than the UK, that should be kept in mind if you are on the verge of calling the police basically murderers. It's convenient that you don't consider how often police are murdered by citizens either.

I don't think it's naive not to be a conspiracy theorist. Sure, there are some cases of police murders and other misconduct but it's hardly the norm and it is rather spurious to think every run-in with the police lurks the head of a grand conspiracy or a cover-up.

When you watch the news in the US from the UK, keep in mind that many have a vested interest in telling a certain narrative.
With C++ one needs discipline to make up for the lack of type safety that one can get in other languages. This is of course not so great, because it relies on the programmer to know various idioms/patterns.

In your example, it would be a major red flag in code review to create a reference like that. Some code constructs are just asking for trouble.

I think the reasons behind still having errors despite tools like Valgrind and ASan are:
a) many devs don't know about them or use them
b) you need 100% coverage to remove all errors

Using said engineering practices will not result in a completely big-free program, but it will have a significant impact on the quality. For something that doesn't have the nightmare security profile of a browser or various other exposed services, that can be just fine, even if not ideal.
Employer dental care is one of the best deals you can get. Find a dentist who optimizes for insurance and you will get back way more than what you put in. This works because few do it.
I think the next generation of online encyclopedia will let a writer "own" a complete version of the article, and the readership/editors will vote on the best written article.

Kind of like Urban Dictionary, except serious.
According to the article, holding your breath in a vacuum is not wise.
I think that if you had a person with average IQ spend time studying vocabulary, they would get a significant boost on an IQ test as well.
There are aspects of React Router that are annoying, but I am glad not to be writing code for matching routes. Works for me.

Also a fan of https://github.com/relay-tools/react-router-relay, because Relay is great.
The sahara could be a source of endless solar energy. But for the obvious political and technical considerations Europe probably first should look into installing large solar plants in Spain, Italy and Greece. Not only would it support the economies of those countries, but it would be very easy to connect those solar farms to the European grid. Also it would give a nice daytime distribution of the power as Spain and Greece are at the western and eastern borders of the European Union.
They're retracing a lot of the ground explored by Less Wrong.
Look up "Rationality from A to Z" for a (long!) series of essays on all the topics that were mentioned.
Because your earnings ability declines. And dying in the street is a 100% myth.
That's fine. Thank you for the response.
> The problem is that Blockstream and those acting on it's behalf oppose any increase in blocksize.

.... because Bitcoin Core developers find that most block size increase proposals seem to be incompatible with Bitcoin resource requirement minimization. Absent the existence of Blockstream I suspect the currently-non-Blockstream developers would still prefer to focus on their own understanding of Bitcoin, rather than popular sentiment on Bitcoin block size limits. Anyway, Bitcoin Core developers have done just that and have organized a FAQ regarding some fascinating proposals and implementations they are working on for how to increase capacity: https://bitcoin.org/en/bitcoin-core/capacity-increases-faq

> and would relegate Bitcoin to a settlement layer

Ehhh settlement layer is sorta unfair. Existing "settlement layers" are things like Target2 RTGS, which turns out to be a typical centralized payment processor under the hood. oops.

> where high value transactions between major financial players take place and nothing else.

Transaction fees offer prioritization for inclusion, true. I don't think it's reasonable to blame Blockstream for an absence of a solution to this problem :-).

> Raising the block size doesn't preclude Blockstream from implementing sidechains but keeping the block size small as Bitcoin grows very large will make Blockstream's sidechain scheme absolutely necessary.

Nah any form of sidechain would work, not just Blockstream's implementations. Also, from an experimentation standpoint, sidechains are necessary regardless the value of the block size limit.

> If the block size were allowed to grow it isn't clear if the value proposition of sidechains would be as strong.

It would be just as strong, read the sidechains whitepaper: https://blockstream.com/sidechains.pdf (basically they are valuable as an experimentation tool, even if they are not being used by businesses; indeed, Blockstream could experiment using sidechains prior to gathering consensus for deployment of features on the Bitcoin blockchain, which is itself quite valuable to Blockstream).
The angular 2 beta is already in production use within Google, so I don't think it's going to change that much for the final release. It's also quite different than 1.x, so unless you are going to want to work on migrating or maintaining 1.x projects learning 1.x isn't going to help you that much.

I'm not sure how good the v2 docs are right now (haven't dived into them much yet), but I'd say you are probably best off to start learning v2 now and get a head start - Egghead.io has Angular 2 tutorials up already so you could try those. Angular 2 is looking really good, and seems to be a big improvement in performance and simplicity over the first version, so I'd recommend learning it.
Zephyer314 hello, interesting read. It is interesting to me that the lowest cumulative level for the tuned model is approximately equal to the lowest cumulative level for the simple model with no tuning. In fact if we had been only looking at the results up until Dec. 12 or so we would have concluded that the simpler model works better and barely beats the house and that maybe the performance of the simple and tuned models are converging.

However, they now seem to be diverging with a clear advantage to the tuned model. If you had been actually using this to bet you might have given up on the tuned model around Dec. 7th when draw down was at its worst.

What will really be interesting is whether the performance over the rest of the season continues to diverge in the current direction or if the performance tends float up and down around the break even line.

Is one of the parameters a progress through the season index? Anyway thanks for sharing the example.
Swift: Commonly Rejected Changes
Well, the industry asked the question and then left the DESERTEC consortium.
> How is this related to the article? You seem to be talking about public perception of wikipedia while the article mainly focuses on the falling number of active editors.

Well, in fairness, the declining number of active editors is likely linked to the public perception of Wikipedia.

Teachers and professors hound into students Wikipedia is not for academic use and is full of nonsense and other wrong information.

Most of the time, this is not true.

We would be better off teaching students Wikipedia isn't an appropriate source to cite, but rather a great research tool which links to it's proper sources, which you may cite.

The stigma the education system has built up around Wikipedia is surely effecting the number of people contributing to it.
Unfortunately, in our case the platforms were Android and iOS :)
Likewise, OpenGL is a pretty standard tool for mobile.
Inadvertent BitTorrent from BYOD swallows bandwidth
I'd agree were it not for this:

>Seventy percent of the land of the Angle is held in trust by the Red Lake Indian Reservation (Ojibwa).

It sounds like 70% of the land is not the U.S. Government's to give.
Interesting idea - but you could certainly do this in any spreadsheet application with multiple cells to represent ranges etc.. I think the of estimating probabilities issue can be considered to be more of a practices issue than a tools issue.
There's also some degree of moral judgment involved. It would be much easier to sell single-payer to Americans if coverage was denied to lifestyle illnesses. It's easier for the American ethos to swallow charity for the poor sap who got brain cancer from an errant cosmic ray than for the obese chain-smoker with type II diabetes and lung cancer.

There is a long history of Puritanical thought running in American culture, in which personal virtue is reflected in outcomes.
Yeah same here. Using it in production has cost some time upgrading. Not looking forward to another upgrade just a few months later.
As others have said it's mostly the desire to learn. A lot of the brightest reverse engineering I have met started off hacking video games. They started with a desire to either understand the game or create cheats. From there they dug into the code.

Reverse engineering has a very romantic view from the outside. In actuality a lot of it is learning esoteric topics and boring concepts to be able to apply it to a single task. It takes a certain mindset to stick with it.

The main pre-requisite is being able to read and understand assembly language. From there it's operating system fundamentals, memory layout, compilers, basic understanding C & C++ and Python is popular in the RE community.

The RE sub-reddit has a good introduction for beginners.

https://www.reddit.com/r/ReverseEngineering/comments/hg0fx/a...
Here's an idea: What if they studied customer behavior and found that when the traditional 2-year contract is up people started shopping around with other providers to see if they could get a better deal, and an unacceptable number were then lost as customers? I'm betting this happened quite a bit, actually.

With the new system when the two years are up (assuming the phone wasn't paid off before then) the customer automatically sees a nice little drop in their bill, which may make them feel more positive about staying with the company, or upgrading their phone again with the thought of "I was already paying that extra amount before anyway".

Just a thought, but I wonder what kind of research has gone into this sort of thing.
Any plans to add different probability distributions? I do this kind of analysis by hand for things like project timelines and cost estimates, but I model each variable with a double triangular distribution (http://www.mhnederlof.nl/doubletriangular.html). You provide a best case, worst case, and then the most likely case. The distribution approximates the long tails on many kinds of distributions.
I went to see Event Horizon in the cinema when it first came out, with a couple of schoolfriends. There was an oldish couple in front of us, maybe in their 50s, possibly expecting a repeat of 2001.

Eventually the film finished, and we all got up, slightly dazed - couple included. The woman said to the man, with pursed lips - "Next time, I'm picking the film" :)

The drive home was about 40 minutes, and my friends and I were silent the whole way. But I'm sure if I saw it again, it would seem adorably tame.