skysight-inc/HackerNews huggingface dataset:
Here's the paper ...

Examination of the Long‐Term Subsurface Warming Observed at the Apollo 15 and 17 Sites Utilizing the Newly Restored Heat Flow Experiment Data From 1975 to 1977

> The Apollo heat flow experiment (HFE) was conducted at landing sites 15 and 17. On Apollo 15, surface and subsurface temperatures were monitored from July 1971 to January 1977. On Apollo 17, monitoring took place from December 1972 to September 1977. The investigators involved in the HFE examined and archived only data from the time of deployment to December 1974. The present authors recovered and restored major portions of the previously unarchived HFE data from January 1975 through September 1977. The HFE investigators noted that temperature of the regolith well below the reach of insolation cycles (~1 m) rose gradually through December 1974 at both sites. The restored data showed that the subsurface warming continued until the end of observations in 1977. Simultaneously, the thermal gradient decreased, because the warming was more pronounced at shallower depths. The present study has examined potential causes for the warming. Recently acquired images of the Lunar Reconnaissance Orbiter Camera over the two landing sites show that the regolith on the paths of the astronauts turned darker, lowering the albedo. We suggest that, as a result of the astronauts' activities, solar heat intake by the regolith increased slightly on average, and that resulted in the observed warming. Simple analytical heat conduction models with constant regolith thermal properties can show that an abrupt increase in surface temperature of 1.6 to 3.5 K at the time of probe deployment best duplicates the magnitude and the timing of the observed subsurface warmings at both Apollo sites.

https://agupubs.onlinelibrary.wiley.com/doi/abs/10.1029/2018...
Trade-offs in ethics and effectiveness can be a subject of discussion, but it's hardly an "emotional outburst" to want to prevent swimmers from being eaten. Slippery-slope arguments seem to make sense when we're locked into one way of modeling the behavior of our fellow humans, but they're usually wrong anyway.
A 3-person team cannot manage 100+ repos with 100+ micro services. Sounds like a big impedance mismatch.
Just for fun, we ingest comments from Hacker News, so I made a quick search to find out who's been posting about Gravwell the most:

https://i.imgur.com/1il6PuJ.png

How embarrassing, it's me! :)
Two colossal wastes of money is not a good reason for a third colossal waste of money.
To stretch the tub metaphor to include latency, you have to imagine someone turning the faucet off and on (or plugging and unplugging the drain) depending on how full the tub is.. and, with memory, there may be one spigot (the bandwidth), but a tremendous number of valve knobs (addresses), such that the someone has to decide the correct knob to turn before the tub empties out completely. If the wrong valve is opened, no water comes out (the wrong data is loaded into cache, which is the same as no data being loaded), so merely guessing is no good.
Decker 330-Watt 1-Cup Coffee Maker
This might come off as being snide, but I'm genuinely curious: was their solution really just having all the services in one repository? That doesn't seem like a problem with microservices at all but more of a devops problem. To be clear, I'm not arguing for microservices, I'm just trying to understand if this was really a problem with splitting off multiple repos. Maybe I'm just really dense and someone can set me straight.

I've actually had experiences with seemingly this same problem at a previous startup. Once we started spinning off individual repositories for small pieces of business logic stuff started to go downhill as the logistics of communicating and sharing one another's code became more and more complex.
The comment referred to fire ants specifically. These have become introduced to countries outside their homeland. For these regions While fire ants offer no purpose, create large economic costs and other issues including killing people.
I'm still waiting for serverless blockchain to be its own buzzword.
Following the URLs it appears that it sets up a systemd timer to post some system info to pastebin every hour. However the script also appears to have a mistake which I think would cause it to only log to /root/home/*/compromised.txt.

$uploader "$FULL_LOG"

should be

upload "$FULL_LOG"
Rally 1.0.0 Released: Benchmark Elasticsearch Like We Do
Actionable predictions are tricky though because acting on the prediction before the event happens influences the system.

For example, my AI says stock X will go up 10%. My act of buying stock X drives the price up, therefore reinforcing the prediction regardless of it's original accuracy. Or, if I predict stock X will go up 10% before the earnings can and don't tell anybody until after the event is over and don't act on the information, what's the point?
New library website provides digital front door to Harvard resources
Like the world cup finals that was shared some weeks ago?
Man, I've been coding since I was a kid. I have a deep love for technology but the hype age we are living in, is just too much.
Sadly, no. Cells are very complex. Whole multicellular organisms are even more complex. We don't have models nearly good enough to replace laboratory experiments with E. coli, much less good enough to replace medical trials with humans.
They didn't even bother to swap the Taiwanese flag emoji with a custom one of the Chinese Taipei flag:

https://en.wikipedia.org/wiki/Chinese_Taipei
Bike share isn’t working in Pasadena
This debate makes me want to punch myself in the face, right approach for the right problems.
This is why they're taking it slow; they're not worried about knock on issues with our herd immunity. They're worried about ecological collapse.

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

"The "Four Pests" campaign was introduced in 1958 by Mao Zedong, as a hygiene campaign aimed to eradicate the pests responsible for the transmission of pestilence and disease: the mosquitos responsible for malaria; the rodents that spread the plague; the pervasive airborne flies; and the sparrows – specifically the Eurasian tree sparrow – which ate grain seed and fruit.[1]

[...]

By April 1960, Chinese leaders changed their opinion due to the influence of ornithologist Tso-hsin Cheng[2] who pointed out that sparrows ate a large number of insects, as well as grains.[8][9] Rather than being increased, rice yields after the campaign were substantially decreased.[10][9] Mao ordered the end of the campaign against sparrows, replacing them with bed bugs, as the extermination of the former upset the ecological balance, and bugs destroyed crops as a result of the absence of natural predators. By this time, however, it was too late. With no sparrows to eat them, locust populations ballooned, swarming the country and compounding the ecological problems already caused by the Great Leap Forward, including widespread deforestation and misuse of poisons and pesticides.[10] Ecological imbalance is credited with exacerbating the Great Chinese Famine, in which 20–45 million people died of starvation.[11][12][Emphasis added]"
I'm pretty sure that we're very far from that. We can't even simulate relatively simple processes in timely manner.
So? Just reformulate it in a way that allows you to apply the Kakutani fixed point theorem and call it a day. That’s what John Nash did.
Follow up Guardian article:

https://www.theguardian.com/news/2018/jul/10/elon-musk-queri...
What are "bind variables"?

I’m sorry, but bind variables are Database 101. I have a hard time believing your use cases are particularly “myriad” given lack of the very basics.
That's perfectly true, but AWS is a lot more than just servers. You're paying a premium for a reliable, flexible, scalable set of products that aren't easily replicated by a box in a rack.

For businesses with healthy margins, there's a clear tradeoff between cloud costs and opportunity costs. If you've got SLAs to honour and a lot of high-RoI engineering tasks in the queue, throwing a bunch of cloud resources at the problem might make perfect sense.

AWS isn't the solution for every task, but that doesn't make it a bad solution. The obvious parallel would be with Discourse's business model. Their product is completely free and open source, so there's nothing stopping you from running their software on a DO droplet, a colocated server or a Raspberry Pi attached to your home router. They have plenty of customers who are happy to pay $100/$300/POA for a managed deployment.
In a sense we already have that, in the form of the `community` repo: Trusted Users mark a package as safe, adopt it, and it gets packaged up and supported.

Perhaps the answer is a few more TUs to get some of the popular AUR packages adopted and officially supported.
Imho, especially things that are important solutions to common things on the Archwiki but are AUR, indicated with the AUR superscript there.

For example for MTP:
https://wiki.archlinux.org/index.php/Media_Transfer_Protocol
The one that worked most stable for me was simple-mtpfs, but it's AUR.

It happens with other archwiki topics too, I encounter it regularly though can't think of good examples from the top of my head currently. E.g. the btrfs article mentions several AUR utilities though admittedly nothing important I need right now :)

And then some important development tools, like closure-compiler
https://aur.archlinux.org/packages/closure-compiler/
What he's arguing seemed more to be that wage growth is fantastic for CEOs, and that the "jobs numbers euphoria" is basically a ploy to keep everybody complacent.

The in-article link to the article "The Pitchforks Are Coming" (https://www.politico.com/magazine/story/2014/06/the-pitchfor...) makes the great point that if higher wages mean less jobs, then why are there more CEOs than ever?
Is there a public database of linux malware found in the wild that one can study to know what kind of things to look for when reviewing PKGBUILDs and other open source code?

EDIT: s/repository/public database/
It makes sense from a not-wanting-to-get-sued-for-breach-of-contract standpoint.

The contract at IXPs almost universally includes a phrase like "will not engage in fraudulent announcement of routes", but proving that happened to the satisfaction of a non-profit's board of directors is difficult. You really have to have completely collinear anatidae.
Strong suspicion every member of the ecosystem plays a role in sustaining the ecosystem.

Mosquitos are still the deadliest animal as far as humans are concerned, makes me wonder what other populations they are keeping under control....

Ecologist hubris and ignorance of 2nd and 3rd order effects is marching with misplaced confidence towards the death spiral.

*Buys more SpaceX bonds....
I wonder why so much of the business writing suffers from survivorship bias type writing - what wrong lessons are we all drawing every day because of that. The esp dangerous ones are probably the ones that sound right but are wrong.

I am a big fan of startups, those who build and innovate. I even like the strategic advice that VCs/ex-founders give about building a business.

However, any writing of the style: "Facebook, Google, Zynga, Twitter did [x] when they were small -> So you must do [x]" doesn't resonate strongly with me. It has this underlying promise of 'if you did [x] you will become Facebook' - which ignores a vast multitude of other factors that went into making an FB. It is worth thinking much harder about how much of [x] is actually right on a strictly case-by-case basis -- depending on what one is trying to build, the problem one is trying to solve and for who.

Sometimes one has to take a different approach and build several features/product bundles in order to sell.

One approach probably is to find some overriding truths that are close to being immutable: such as,

1) make something people want (I haven't seen a counterexample to this yet)

2) nothing happens until somebody sells something (This puts focus sharply on building what will sell)

3) articulating 'why now' to the best available clarity is important in my view (even if to explain why a bigger scope may be needed now than in the past - e.g. if one has to build an HR system today, they would probably need to build a payroll integration as a feature; this wasn't true before 2013-14)

The problem of course with these that they sound super generic that they cease to be of value after a point.
> Who knows what chaos will be unleashed by tampering with them?

It's a good question. And the same thing could be said about any disease prevention strategy. What if the persistent presence of Polio is necessary for us to survive some future hypothesised outbreak? Imagination is the limit here.

But we certainly do know the chaos that is unleashed everyday by not eradicating viruses that use mosquitoes as a vector.
Hi, do you offer sponsorship? Thanks!
I was sort of with the author until I got to the recommended policy change they want to see from legislators:

"We should abolish all tax advantaged savings accounts. If the $158 billion in savings were then distributed evenly, every household could receive $1,250 per year and companies like Google would no longer pay HR tax specialists to exploit our tax code."

The author appears to literally suggest we just take everyone's 401(k)s and IRAs for the year, give them away, and abolish the whole system. How is this a reasonable policy?
Your twitter followers whom you also follow. I had to read the source to find that out.
Nothing that I know off. Are you thinking specific to Arch Linux or in general?
I've been using pass with a yubikey for the past year and a half and have been very happy with it. The ability to call out to the pass binary in personal scripts is a really handy feature that I didn't realize would be so useful until I started using it.
No, but dice that roll sixes more often are contributing more offspring to the next generation. If the selection pressure keeps up, you will have most dice consistently rolling 6s.
I was actually just looking into gauges and Fathom yesterday and tried to set it up. Fathom seemed a bit too early stage to run it myself so I'm going to wait a bit.

I was pleasantly surprised that when I looked into gauges that the interface looks modern (unlike the screenshots on the start page) so it seems that it changed hands and is actively being developed again. I used it a while ago when it was bought up by Github.
Here's a cool paper on doing so:

https://sci-hub.tw/https://www.researchgate.net/publication/...

They even 3D printed it!
I can't speak to that, aside from pointing out that the authors of the article themselves had to work on the HA aspects of it. It didn't come "for free" with the AWS account.
The simple fact is mongoDB fails to have sufficient durability guarantees for business data when compared to a traditional RDBMS. That is one of the reasons why its so fast in comparison. A power loss event during data writes can and will lead to data loss.

https://www.mongodb.com/blog/post/what-about-durability
Many of the alternates (including linux cli stuff) that are much faster require a re-thinking of attitude, don't work where there are tens to hundreds of people submitting queries, or require different skills. It's tragic to think of all of the computrons and watts wasted with Hadoop-ish stuff (map-reducing without filters, Java itself for most implementations) - but still I wouldn't recommend to most CIOs they replace Hadoop in all or maybe even most cases, even for few-TB data sets and smaller.

Both because of familiarity with querying and the solidity of running a multi-tenant system.

But I do recommend that they switch to MapR [c++ core and a passable central FS for unix-based super fast queries] if they're concerned with efficiency.

[For context, in my day job we do multiple clusters of millions of network traffic summaries/sec and are often replacing Hadoop, or more recently, ELK, as people tried to use them for that use case. All well >>> will fit in ram. We have our own in-house column-store + streaming combo db done in go/c/c++ that started as clustering fastbit.]
They’ve increased their numbers by about 250% over this time last year. Another 40% isn’t that much by comparison.

At the end of Q2 they hit 5,000 Model 3s per week, plus 2,000 S/X. That’s an annualized rate of 350,000.

And yes, they haven’t even built 350,000 cars yet. The acceleration of their manufacturing over the last few months has been amazingly fast.
Malware Found in Arch Linux AUR Package Repository
We Asked Nintendo, Microsoft, and 12 Other Game Devs How They Deal with Crunch
Or we'll come up with a workable technical solution (like meshnet, but something that works) to the fundamental problem of centralization of the internet.
> Once or twice is an accident. "Repeatedly" demonstrates an unwillingness to change.

This assumes that you make the same mistake multiple times. There are so many unwritten social rules (which actually hardly anybody can consciously "put into explicit rules") that there exists a giant "potential" for social blunders without making any mistake twice.
A patent is, first and foremost, a fence. It creates property rights. Do fences increase productivity? Should they? It probably is more productive if your neighbor's dog shits on your lawn, or your clever invention is taken apart and immediately copied by a larger competitor. But is it right?
i looked into it about a year ago, and it would have required a rewrite of the (brittle) installer as well as supporting modules (that seemed to be dependencies of other parts of the system), not just extracting the configs into environment variables (which i did, but that didn't solve the problem). non-trivial, to say the least.
This is a corollary to the /r/HailCorporate mentality, where every discussion about/mention of a brand is astroturfing. Healthy skepticism is encouraged, but there's a point where it becomes FUD, and perhaps in some cases as destructive as any surreptitious marketing.
Create chrome extension with ReactJs using inject page strategy
> and people differ too much in how they perceive and process code.

Yes, for example I love dense code. A 1 line regex is a lot simpler to me than the 50-60 lines of code equivalent.

Yet some programmers find the 1 line regex significantly more difficult even if they know regex.
SF Supes begin review of Central SoMa plan expected to add 8000 homes, 33K jobs
On the other side, is it fair to say 8-bit encryption is NOT secure?
author here :hi:, yes the policy section is a bit wishy washy and short on details. I think you would grandfather in existing accounts, but not allow additional contributions starting at some point in the future.

edit: I've updated the article to add a little more detail to the policy recommendation.
Mongo wins when two things are true
1) Your use cases are get doc, put doc, delete doc. No aggregations, OR you have a very healthy sharding key.
2) You need to go to the 1 terabyte - 100 terabyte scale for a very small cost in humans and machines.

For those of us who have dealt with (or dealt with the human/machine cost of) a TB+ Postgres or MySQL database, Mongo can be a blessing if you data can be organized in a proper NoSQL fashion.

It's true, you can scale RDBMSs into the terabytes range with modest cost with excellent performance. BUT the singular guiding principle to achieve this is integers, integers, integers. In general, RDBMSs start shedding performance the more non-integer columns you have in your relevant tables.

If you have less than 100GB of data, it will never matter what database you choose -- it's all about table structure and queries. MySQL, Postgres, Mongo, etc. Unless you choose sqlite of course :P
> I thought Apple was supposed to be the great government-resistant pro-user-rights stronghold.

Only when they are sure that the government really can't punish them for it, and it gets them good PR. When dealing with a government that will ban the sales of the iPhone in that country, they roll over and make sure they do whatever they need to do to have friendly relations with them.
There is a hi-res version of starry night, if you admire that painting here: https://en.wikipedia.org/wiki/File:Van_Gogh_-_Starry_Night_-...

It is 30,000 × 23,756 pixels (file size: 205.1 MB) .

While incomparable to seeing it up close, a lot of brush details can be seen up close. If there was such as thing as a favorite jpg, for me this is it! :-)
An interesting look into the world of prison email
Why Today's Work Climate Sucks and What We Can Do About It
Everything that paper says is true, but it's also incredibly obvious. It just points out that it's impossible to rule out side-channel attacks at the endpoints. If Eve has powerful enough equipment then she can just read the secret out of Alice's brain before Alice even types it into her computer. I don't think anyone saying or hearing the claim that quantum protocols are "guaranteed by the laws of physics" understands it to mean that the protocol protects against that kind of attack.
May be they're just testing iOS 12 third party password manager integration?
I wanted to use this before going back to Gatsby:

https://themes.gohugo.io/minimo/
What if some helpful antibodies are transmitted via mosquitos? What if this happens cross-species?
>I jumped on the JavaScript hater train and left the station.

As does most of Hacker News with every technology they hate on.
I'm just saying it sounds like legal CYA. Consider [1] defines "you" in the agreement as "The person who applied for this Account and agrees to this Agreement." Further down, section 12 specifies that the account automatically moves to a "in default" state if you "Pass away or become incompetent;"

Considering that "you" needs to be notified when their account goes into default, does "you" automatically become "the estate"? Is "the estate" the one who "applied for this Account and agrees to this Agreement"? Can an estate agree to anything?

Is it possible a deceased person would be able to get off the hook for this kind of debt is the agreement isn't followed to the letter by the creditor?

[1] https://www.paypal.com/us/webapps/mpp/bmlterms#accountAgreem...
Hey - no worries, and I appreciate the forthright (and detailed) response. I Show HN'd something the other day and got beat up a little too, I know how it goes. ;)

I typically use AWS's built-in tools, but I've been looking for something for home, so I'll be checking this out. Thanks.
Bet on the World Cup using output from the same algorithms that got it wrong this time over 20 World Cup events, and you are likely to still come out way ahead. Real-world events have chaotic properties to them, but overall these predictions tend to be quite accurate.

Casinos allow you to bet on games like roulette or blackjack because they have a mathematical expectation - a prediction - that they will come out ahead overall. Would you say that this prediction is wrong because individual players sometimes win a lot of money?

You can’t look to a single event that differs from a prediction and use that as a basis for an argument that the entire model is flawed.
I don’t understand. The US has never played world police in any sort of blanket fashion. It’s always been subject to whims and almost always limited to situations where it serves our interests in some way (or at least the interests of those in power). I don’t see how there would have been any expectation of US intervention in Ukraine given our past behavior.

You immediately followed the Ukraine reference with “The previous administration hardly bolstered the notion that the US would hold up to promises and supposed red lines.” But there were no promises or red lines. Was that intended as a separate point?
Is this the best integration of a CMS with Angular?
No, it's odd to think of the US in those terms and still feels strange. I understand!
Good. This was a flagrant and deliberate violation. To argue Apple is overstepping here is to suggest Apple employees are exempt from the law.