skysight-inc/HackerNews huggingface dataset:
> Frankly, I am having a hard time believing that HE.NET failed that badly.

Believe it. HE has many, many netiron-based routers in their network and many, many ASNs as transit customers. the hardware doesn't have the capacity to implement complete filtering for everyone.

between hardware-constrained equipment being replaced and the tireless work Job Snijders (& others) are doing with route security, these kinds of episodes will become far more difficult and occur much, much less.
I ride a self-driving car on the streets of one of China’s most congested cities
Why would you ever want to have any kind of login / API on a firewall accessible on a public interface?
> It seems like your reasoning and the reasoning of the author could be applied to any statistic testing the reliability of a hypothesis, not simply p values.

Precisely. That's the point. Hypothesis testing is inherently absurd.
Effect estimation, rather than relying on p-values, is one approach that provides far more context than just "Is or is not significant".

Also training your scientists - especially those outside the physical sciences - that effects likely aren't fixed in a meaningful sense (i.e. the effect of smoking on lung cancer isn't a universal constant in the way the speed of light is), at which point multiple estimates of the same effect from different groups and populations has value.
Thanks! Do you know how I can access that page he is on? I'd like to have a click around myself.
> As a male engineer I'd be happy to spend half the time going around and chatting, listening, massaging and organizing games to help colleages / team mates destress and feel energized and motivated.

Well, I can relate to that. Sometime I can really use some massage at work while chatting with my friendly co-workers (about work), which will makes me love my job and maybe increase my productivity.

Sadly, I think ask our company to hire a massager is too much for them :(
I think the irony that the the device to catch plastic is also made of plastic, seems to be lost on a lot people. More so that the project is unlikely to succeed, and if as some people are predicting, it's not storm proof, then it's very likely to just be adding [it's mass] to the problem.
Personally, I find Redux to be a joy to use and write code with. I agree that there is a lot of "boilerplate" for new developers, as Redux does not really come with a batteries-included "framework" to build CRUD apps -- that's on you to figure out and write.

One you do write this framework in Redux, however, you can reuse it and the amount of unnecessary boilerplate goes to near zero in my experience.

We just need a de facto open source framework built on top of Redux for people who haven't worked with it extensively to build with.
I flew across China last month ... Lots of open cast coal mines, each with a power station next to it .... But they're planning ahead, those power stations are surrounded by thousands of windmills, more than I could count leveraging the power distribution network
It’s ok to hire males for entertainment, just not females. Hastag feminism.
Also that those tests are actually testing the same thing, which is tricky with your "two different mechanisms" requirement a lot of the time. My field is currently struggling to get a handle of what one should do in a particular circumstance when one test is negative and the other positive (for those interested, PCR + and toxin assay - for C. difficile).
the ones about red spiders
I investigated MST for a React Native project and found the the additional overhead it created for frequent state updates was too much - in a synthetic test updating state every frame, it resulted in a 30-40% increase in CPU usage on a real device vs. plain MobX which for our application probably isn’t acceptable. If you know you won’t be making really frequent state updates or CPU constraints are less important it seems like a great option!
Refreshingly honest, I expect. Western companies do exactly the same tricks but are sly about it. And the HR department must be in on it. Just look at LinkedIn.
I was writing a mail but since I saw you are here, I thought maybe I should share this questions here itself. Hopefully others might chip in too:

1. Is it a black & white phone? Or does it use e-Ink (how comfortable is it for the eyes)? (You have mentioned I can enjoy photos with full colour with some "Colour Touch" tech but that's it, there's nothing else regarding it at all). Do you have another website or page where you have discussed your specs in detail?

2. What about battery life? If, assuming, it's not a colour screen then does it have a ridiculously good battery life?

3. Is this phone already a reality or is it just a concept phone or designs as of now and you will be developing it later?

4. What about the privacy and security aspects of this phone?

5. What version of Android is it using, if at all it is using Android? What about updates - any promised/guaranteed date of OS version upgrade?

6. International shipping? International warranty? How do you handle this?

7. Any plans for a smaller phone, something like iPhone SE/5S size (mentioned this as its my current phone)? I mean in ~4 inch ballpark.
Yep! I’m sitting on one of the new electric buses at Schiphol Airport right now. They are so quiet and smooth.
I have always said that the GCP HTTP(S) load balancer is the hidden gem in cloud. I'm glad it's becoming more and more popular (also feature rich).

One feature that must be mentioned is that it allows you to cache content (could be anything: HTML, JPEG and more) for as little as 1 second! CloudFlare requires an enterprise plan and even then you cannot set a TTL lower than 30 seconds.
You can end up with a Ph.D. in some fields being exposed to almost no statistics, or only statistics which work in very confined settings (certain experimental sciences where "Just do an ANOVA... is genuinely the answer to almost every question).

That often works...right up until the moment when a scientist has to step outside that context.

This often cuts both ways though. I have seen beautiful math and statistics around problems that don't make any sense if you've taken more than one semester of microbiology.
Performance was my main concern with MST, most notably if your data modelling involves A LOT of entities, things can get slow: https://github.com/mobxjs/mobx-state-tree/issues/440. Binding methods on every instance of an object is a lot of overhead.

I really liked using MST when I spent a few days fiddling with it. However, I really don't want to get trapped with perf bottlenecks I can't easily fix. Whether I'd actually run into trouble - I have no idea, but vanilla MobX is excellent enough that I'm happy sticking with it. I'd love to use MST more though.
Kate Middleton’s ‘luxury’ birth cost less than the average U.S. birth
The difference between something that requires a bad actor and one which is an outcome of a system working as intended is pretty huge.
I know. I've seen _many_ other higher-level abstractions on top of Redux (per my comment elsewhere in the thread). A year ago, I opened up an issue [0] to discuss ways we could improve the "getting started" experience, reduce boilerplate, add better abstractions on top of the base primitives, etc. The thread got some decent comments, but nothing really concrete came out of it.

A few months ago I had a little bit of free time, and threw together a tiny "starter kit" library [1] that is intended to simplify a couple of the common pain points (basic store config, and writing reducers with immutable updates). I haven't had time to push it further, but long-term it's likely to become an official Redux-branded "use this to get started" addon.

I'm very open to further ideas and suggestions around this topic.

[0] https://github.com/reactjs/redux/issues/2295

[1] https://github.com/markerikson/redux-starter-kit
Thanks for doing what you do.

I contributed some of the initial documentation [1] for testing middleware back in the day.

Wondering if there are any areas in particular you'd be looking for contributions? I use redux every day and would like to contribute back some (if it would be helpful).

[1] https://github.com/reactjs/redux/pull/559
He's describing a multiple comparisons problem, not p-hacking, enabled by, essentially, ease of statistical computation. An honest researcher can trigger his problem without ever p-hacking.

See: Genome Wide Association Studies.
Except that rural votes are magnified by the Senate distortion.

https://en.wikipedia.org/wiki/National_Popular_Vote_Intersta... is one step towards sanity.
You made my day, awesome footage.
Thanks, I appreciate that. I will avoid the LA area when finding my next gig.
I really enjoyed this writeup. Having just finished a year in the field on the engineering side, and reading many papers without an academic background, it’s funny to recognize who are the “math” types and who are the “biology” types at work. Puts things in perspective.

I’ve been pushing for more ensembles and multi-label classifiers because I want to orchestrate the pieces with logic to fill gaps until stats methods outperform (given enough new data in nice annotation-friendly structures).

The “math” types seem to feel like there’s a neural net solution to every problem or that we can expand the multi class model to cover more domains despite being mostly saturated with high accuracy. Sounds awesome but I’m impatient!

The “biology” folks seem to be most attracted to neatness or parsimony. We had some great bikeshedding sessions around adjacency list vs materialized path (ltree) in postgres for label hierarchies. Abstractions can be useful too!

Any tips on being a better experimentalist and pushing academic colleagues towards better solutions in the field?
Even though I knew the content deserved it, I upvoted just based on the title.
That's basically webOS.

If you get webOS working on your hardware, you will have a small pile of very staunch supporters.

A couple of realistic caveats, and novel ideas to solve them:

1. webOS is not Android.

Android will eventually mean Fuschia, which will mean bye bye to Linux driver blobs. I'm not sure how the scene looks right now in terms of trying to squash an Android kernel and blobs together with webOS userspace. Might work, might produce rueful laughter.

One interesting thing you could do is lead a community effort to get webOS running on top of Fuschia, which is still very new but functions well enough to fully come up graphically and boot into a Chromium-based session (yep!).

To me, that suggests enough of the Fuschia core is "set" and unlikely to change that RIGHT NOW is the perfect time to quietly catch up to feature parity with alternative userspaces, and when Android does "the big switchover" (it's obvious that's the goal, Fuschia has things like 120fps update targets etc), you'll suddenly have more hardware support than any other platform.

2. webOS has no real apps.

No point denying this is true. Facebook isn't releasing a webOS app. That cements a lot of things. There's also the fact that LG bought webOS for TVs. That did nothing to kill it on phones, but the move certainly did shift all of the tech-prosumer expectancy/focus over to the TV space and leave the webOS-on-phones/tablets sector full of tumbleweeds. And nothing's really changing that.

The webOS-on-Fuschia idea would be unlikely to trigger wholesale adoption of the platform. Not going to do it.

I see a couple of alternatives:

0. You kind of get dual-boot for free anyway

1. Implement hardware-accelerated KVM for ARM on Fuschia, and run Android in a VM

2. Implement kernel-level containerization/virtualization aka what's described under "Virtualization" in http://kernelthread.com/projects/

3. Figure out how Fuschia works at the kernel level and work out how to run the webOS and Android userspaces side by side, either running simultaneously or stopping one to launch the other

(I don't typically start lists at 0, but that first point felt so obvious I used a 0 so I could include it in the list.)

You get 0 for free, and dual booting will appeal to some who want the closure of "Android is simply not running".

1 is... I included that one for comparison :)

2 and 3 seem interesting. I'd tackle these by seeing how the Fuschia team react to being engaged "from the outside". You could lead that effort; I don't think anything is being done in that regard at this point (eg unlike how Chromium does get lots of external contributions from individuals).

Well, that's my 2c anyway.
Why?

In my own app, I store a variety of data in the Redux store: data fetched from the server, UI state like modals/context menus/tabs, app control state like "current selected item", etc. Certainly not all UI state _needs_ to go into Redux, but there's nothing wrong with storing UI state in Redux. Totally depends on where and how it's needed.
I resisted for a long time, but finally switched from a callback model to Mobx and the reason was that ShouldComponentUpdate and ComponentDidUpdate started becoming unbearably hard to manage.

So state management libraries are not solving a unsolvable problem, they are here so that we can write cleaner, more efficient code that potentially can become more performant. At least that's what happened in my case.
The same picture but in a video with a very fitting song imo: https://vimeo.com/124610461
nobody's offering Google anything, rather, Google is offering developers meta data for HTTP requests.
What are you driving? Even my 6 cylinder sports car stays usually well above that, and my everyday Ford Focus rarely goes below 30.
When I first read the title I thought of my observation with the migraines I get. Personally, migraine pain only onsets when 'everything is ok,' in terms of safety, stress, food and hydration; but the other symptoms will start at any time.

For example, while rock climbing once, I was getting down from the top of a mountain, seeing those 'squirlly refractive light worms' in my vision that some people with severe migraines get. I had all the symptoms of having a migraine--and was lucky I didn't die on that mountain--but the debilitating pain only came when I was down, in the car, away from danger, with food and water. This is how it always is.

Given this experience, I believe there must be a lot more to the psychological-physical aspect if interpretations of pain than what is shown here, and personal experiences may be why others are jumping to conclusions.

Also: those poor mice
Test Equipment dot Net is running the Rigol promotion through June:

https://www.tequipment.net/rigol-promotions-and-offers/
As an aromantic man, I do feel more energized and motivated after a chat or a card game with my (mostly male) colleagues. I'm somewhat averse to body contact, so I wouldn't make use of a massager, but so long as it's just an extra perk like a Googly ball-bath (they have those, right?), I don't see the problem.

Not being sexually attracted to someone doesn't mean that their company won't be refreshing or even uncomfortable. I think that's much more a matter of personality, and gender is only a secondary factor in whether you'll find someone likable or not.
I think you mean <10 nm?
The problem still stands then.
It used to be a specific feature size: the length of the gate. But, even as the wheels came off of that pretty quickly, the convention stayed pretty simple and familiar: each process node halves the size of the one before it - you can print double the number of transistors at the smaller process node. To make the math work out, that means each process node "name" is sqrt(1/2) ~= 0.7x smaller than the last, which gives you the easy-to-follow node names from 3um to about 3nm (when people tend to switch to ångströms or picometers since it moves the decimal kindly).

Even as things got sticky due to advancements in transistor construction meaning that old metrics like gate length were obsolete, we were still roughly following the trend laid out ahead of us for decades. A new process would double your density, letting you roughly cut the size of your old chip in half.

...Until a few fab companies just up and decided "You know what, fuck it, we can't actually catch up to Intel, but if what if we just... say that we did?" (...and I wish I was kidding. Take a look: https://m.eet.com/images/eetimes/2013/10/1319679/20-Value.jp... vs https://m.eet.com/images/eetimes/2013/10/1319679/16-Value.jp...).

So pretty quickly, TSMC decided that they'd just advance the node table, despite not actually increasing the density by double as you'd expect. "Next generation" 20nm processes became "16nm" and "14nm" on marketing docs, despite the process capabilities not changing that much (or even at all in some cases), with the only thing close to a justification given is that "FinFETs are different. They perform better than planar FETs so we should be able to give them a new node name." GloFo and Samsung quickly took the bit and followed their lead as they began FinFET manufacturing.

And apparently since nobody blinked an eye or set off alarm bells about these fabs basically lying about their capabilities, they got away with it and are now continuing the trend downwards. "10nm" processes from TSMC, Samsung and GloFo measure up to Intel's 14nm, and now "7nm" processes measure up to Intel's 10nm. It's actually pretty surprising Intel hasn't thrown up its hands and joined them on the fun, or even come up with their own marketing spin on it yet. "Intel's new 7nm-xtreme manufacturing process (actually it's just 10nm+)" or whatever.
But Amazon really did screw up here.

The attackers were able to announce more specific prefixes than Amazon was announcing itself. It was like Amazon said "give me all phone calls for the 415 area code," and the attackers said "give me all calls for 415-555-xxxx." In internet routing, the most specific always wins (down to the minimum prefix size of /24 most networks filter on).

A commonly accepted mitigation for BGP hijacking is to announce the /24's of your important assets as well as the covering prefixes. An attackers announcement of the same /24 will at worst capture _some_ of the traffic, rather than being seen as a more specific and capturing _all_ the traffic.
Also, you can save the MEW webpage locally and use it.
My main smart component is several hundred lines long at this point. The methods in the component are largely event handlers used to manipulate the component's state object. The methods are passed down into the hierarchy of "dumb" components via props, and are called when actions occur in those components (e.g. onClick some element). The methods are conceptually group-able into 4 distinct areas of data manipulation. However, the catch is that many of the event handler methods need to modify other pieces of the state object too. So, for example, I have a number of methods related to polygon state management. I'd like to move these into a <Polygons /> smart component, but when updating a polygon, I also, in some cases, need to update data for another potentially extractable smart component <Toolbar />. A state management library would allow me to move/group data management logic into smart components that would also still have access to other parts of the state tree.
How to handle your prospects after a service outage
And why shouldn't it be independent of React? While Redux and React-Redux were developed together, the Redux core is 100% pure plain vanilla JS, and the fact that bindings exist for a whole bunch of other frameworks shows that it works fine that way.

Now, Dan and Andrew have suggested that in order to have React-Redux work properly with the upcoming async React rendering, we should possibly consider reimplementing the Redux store logic to use React component state as the basis. In other words, you'd probably do something like `import {createStore} from "react-redux"`. I'm not keen on that idea myself, and am hopeful we can find an approach that will allow use of a separate standard Redux store and still get the benefits of async React rendering down the road.
E-waste recycler sentenced to prison for distributing computer restore disks
Vitalik acknowledges your point:

"... people are not experts at property valuation, and would have to spend a significant amount of time and mental effort figuring out what self-assessed value to put for their house, and they would complain much more if they accidentally put a value that’s too low and suddenly find that their house is gone."

The solution: users would choose an AI to generate real time valuations.

In the property/personal home context, I think this is a bad idea, because if the AI gets it wrong, and you're forced to sell your house, that is bad. However, this idea could work very well in other types of property markets (this was all discussed in the article).
Well, you could send a gay person to play games and do massage to programmers who are least productive. I'm sure they will become enough motivated not to fail the next deadline.
I hate when news organizations don’t offer a text version of a story. Video and audio segements are soooo slowwwwwzzzzzz.
A couple of days ago I've decided to not finish Seveneves after having been disappointed by REAMDE already. Are there any recent book releases anyone can recommend to people who love Cryptonomicon, Anathem and Snow Crash but aren't really into REAMDE and Seveneves?
> Many researchers are now arguing that we should, more generally, move away from using statistics to make all-or-none decisions and instead use them for "estimation". In other words, instead of asking whether an effect is null or not, we should ask how big the effect is likely to be given the data.

I couldn’t agree more with this statement, and even moreso in a business setting than in research. It’s just so easy to get caught up in statistical significance and lose perspective on practical significance. I’ve found confidence intervals most informative and easy to understand.
They don't, in practice, because what you repay is linked to what you earn.
I don't think inflation is (necessarily) a problem. I do think that some people benefit immensely from being "close to the source" of money creation; and especially when times get tough, those with access to this fountain benefit at the peril of the masses who are using the currency.

There are cryptos with inflation built in, probably in whatever most ideal form you or anyone thinks is correct.

Or, I might say: You have a narrow view of bitcoin if you think stopping inflation is the problem that it's solving.
Just wanted to say thank you for the heads up. I've been taking a react course on udacity where redux is super baked in so im not being exposed to many things like apollo-link and graphQL, I learned a lot from your post :)
Compliance, integrations, archiving, reliability, staff, electricity, dividends -- banks and intermediaries are for-profit businesses. Somobody needs to pay for that.

Crypto transfer costs too -- miners do bankers job.
They do look like people about to kiss. If would look less that way if they would be further from each other. Their shoulders are almost touching. Also, people rarely silently stare at each other at non-kissing occasions.
> Debugging hardware code written in Erlang sounds... challenging.

Depending on which part of the hardware code you need to debug, Erlang could make it easier; once you get the erlang shell running, you have hot code loading, some pretty extensive debug hooks, and nice bitmatching syntax. If the hardware code you need to debug is in the chain of getting to an erlang shell (getting the system running to the point where you can have a serial terminal and boot an OS), I don't think Erlang makes much of a difference -- projects big enough to run Nerves are likely going to run a full OS kernel, and Nerves is using a Linux kernel, once you can boot a Linux kernel, you've probably done a lot of the hard work.
Don’t ignore the fact that internet opened up the arena for many more musicians.