skysight-inc/HackerNews huggingface dataset:
Example: accept the terms or we’ll submit these pictures as evidence.

For your specific hypothetical, it depends. First, are those pictures relevant to the litigation between the parties? Second, would the threatening party be allowed to submit those pictures as evidence regardless of what the victim decided? If the answer to both of those is yes, then threatening to introduce the pictures as evidence in court would generally not be blackmail.

However, AMI and Bezos aren't currently engaged in litigation since no lawsuit has yet been filed. The legal system is not yet involved in this matter, so your criticism of the legal system as it applies in your comment is unfounded.

And if these threats are legal, then the legal system is broken.

This comes down to the contents of the pictures themselves. If they are private pictures of himself or his GF, then generally the burden is on AMI to show that the pictures are somehow relevant to the public interest. This is an extremely high bar for them to clear, since they need to show that the nude photos are (1) relevant to the public interest in Bezos' divorce, and (2) that the public's interest in seeing the photos overrides Bezos' and Sanchez's interests in keeping their private photos private. (Note: this is just a very simplified layman's overview. An in-depth discussion would be the length of a law-review article.)
I was at LBNL while the element 118 crisis happened. While ultimately it was figured out using VMS timestamps, well kept lab notebooks helped clear a lot of people from potential guilt.

Considering how bad the replication crisis is, if our society ever gets its shit together, many of these people should actually be convicted of fraud or at least removed from positions where they could commit further frauds.
And I assume that’s why the author has put 4 references to that claim
Hi, I'm a Redux maintainer.

I wouldn't call it a _significant_ performance hit. There's a measurable difference in our artificial stress tests benchmarks, and some users have reported slowdowns in specific scenarios (especially when large forms are connected to Redux).

I recently posted a roadmap issue with our plans for addressing the perf issues, and moving towards the ability to ship a hooks-based API for React-Redux:

https://github.com/reduxjs/react-redux/issues/1177

I've specifically spent the last week experimenting with reworking the internals of `connect` to come up with an alternative implementation that relies on direct store subscriptions again, and as of a couple days ago, I seem to have come up with something that is actually _faster_ than both v6 _and_ v5 in our benchmarks:

https://github.com/reduxjs/react-redux/issues/1177#issuecomm...

Still needs more investigating and testing, but this approach looks very promising.
Founder and CEO of Daily Dress Me, Nina Vir talking about fashion and tech
Extreme rainfall reactivates waterfall – Atacama Desert
According to the page, it was Amazon that made the original claim, so they would have the necessary sample size.

But there's no guarantee that it will apply for all pages.
I have debt - a mortgage. But it's only 2%. Surely it makes more sense to invest in the stock market (~7% over a long period) than pay that off.
> Many would happily join a volunteer endeavor to clean up our country's case database and build a great UI on top of it which encourages public interest in the judicial system.

What would be the value of that? What problem is that trying to solve that is worth giving up $140 million a year in revenue that’s currently coming almost entirely out of the pockets of lawyers and law firms?

> The data is in fact out there
It is not. There is no complete, real-time, or normalized open case data out there, and LexisNexis and Westlaw's products are not priced to be accessible to individual citizens.

I’m not sure what you mean by “normalized” in this context, but Lexis and Westlaw do a ton of additional analysis on top of public cases at their own expense. That information isn’t in PACER. To generate it you’re talking about even more expense. And while the existing databases are not updated in real time, they’re quite complete for federal cases, which is all that PACER covers. And I’ve never seen an interesting application of that data beyond simply allowing you to read the cases.
Blackmail communicated through a lawyer is still blackmail, and moreover makes a lawyer a party to blackmail.

AMI's lawyers are on very shaky ground here and there's a realistic chance they end this decade disbarred.
The spirit of the idea is that Google will see the 304 status and move onto the next page more quickly than if it received a 200 status and reconciled that version of the page with the version that was previously crawled.
That's a great example and a great product. We could all strive to make a product as good as Jiffy.
Works very well for me.

dieulot, is there a small bug with the allowQueryString check?

const allowQueryString = 'instantAllowQueryString' in document.body.dataset

I think should be:

const allowQueryString = 'instantallowquerystring' in document.body.dataset

If I have:

<body data-instantAllowQueryString="foo">

then

'instantAllowQueryString' in document.body.dataset === false

and

'instantallowquerystring' in document.body.dataset === true

because html data attributes get converted to lowercase by the browser (I think).
I really hate it how these websites try to limit the amount of context that can be shown horizontally. If I wanted to see less stuff in a line I would just resize my browser, while if I am using a phone I won't be seeing long lines anyway.
"but it looks fine on my $4000 MacBook with my perfect 25-year old eyes"
I'm not sure why you feel this relates to Redux, tbh.

The Redux core is tiny and very stable. There were a couple technically "breaking" changes within the first couple months after it hit 1.0 in July 2015, and it stayed on 3.x until the middle of last year. The bump to 4.x was primarily due to updated TypeScript typings.

React-Redux has also been very stable, especially in terms of public API. We've reworked the internals a couple times to address various aspects of interacting with React, but the public API has been basically unchanged since the start of 2016.

I wrote a post on "The History and Implementation of React-Redux" that explains what React-Redux does, how it's evolved over time, and why the various changes were made:

https://blog.isquaredsoftware.com/2018/11/react-redux-histor...
More precisely, in order to decide whether it is a good idea, one should assess (i) how difficult it is to give an explanation of why some procedure works and (ii) how difficult it is to learn how to apply the procedure without understanding why it works.

Well, teaching basic math at a commuter college years ago, it felt like the issue of "teaching procedure" to "teaching understanding" was complex. The course I was teaching was close to the end of the math requirements for a significant percentage of the students. I was very attracted to teaching ideas but this group of students essentially had the attitude that they wanted a procedure to memorize rather than an explanation, not matter how complex the procedure. It had a certain logic - mathematical explanation would have touched a world they were happy to and committed to leaving forever soon after this. They'd suffered through this world up this point and thinking about it was more painful than simply acting.

Which is to say, I don't think there any easy answer for how to teach math. The failure of American "new math" years ago is something of a lesson in the push-pull of concepts versus concreteness as they can become ideologies in society at large.
There is a slew of case studies that support this line of thinking. Page speed impacts user retention and conversions.

See: https://developers.google.com/web/fundamentals/performance/w...
This should be implemented at the browser level, not in a webpage.
Say it with me

NAT Is Not A Firewall
That's a really good example. Thank you.
"The academic culture in China is such that cheating and lying is widespread"

This statement doesn't "blame the culture". In this sentence, culture means "a set of behaviors". The sentence doesn't speculate about why that (speculated) culture exists, and it certainly isn't saying "Chinese culture promotes cheating". Actually, all it's really saying is, "Cheating and lying is widespread in academia in China". That statement is totally compatible with what you wrote.

When having these discussions, it helps to interpret other people's perspectives charitably. Communication is hard. We don't need to make it harder by assuming that everyone who says something that could be interpreted as racism is actually a racist. Plus, I've found that if I interpret other perspectives charitably, I almost always end up closer to understanding what the other person actually meant.
It should be clear in HN of all places that what the product is named and what it does at a technical level is not the same thing. Technically, PACER is a view into the ECFS database, and it’s not set up for the sort of wide-spread public access you’re talking about. One could build such a system, but now you’re talking about building that system at substantial cost, while undercutting your PACER revenue. And I’m not clear what the public benefit is that justifies that.

I think in a common law system like ours, opinions must be available to the public as a matter of political morality. I don’t think that same moral justification extends to the other filings in cases, which don’t have the force of law. I think you need some utilitarian justification for incurring the cost of making these more widely available, and I don’t see a compelling one.
Meltdown IIRC didn’t affect AMD processors, but Spectre was pretty much across the board.
Thanks, I noticed this a while back and I have been intending to rename it .. writing a language/interpreter is the easy part, coming up with a name is the tricky bit ... suggestions welcome.
Yeah, but this way the banks will just start splitting into the smaller ones, and the one’s which get caught will be later on hired by the one which didn’t.
I never liked this essay because it attacked a problem from the wrong perspective. Uniformity of reference is a desirable goal (I'm a Lisp programmer, how could I say otherwise? :-) but should not become a fetish. Not all names have equivalent semantics.

In the case of email, the "unix" approach described requires a lot of knowledge on the part of the user: hence foovax!kremvax!ourgateway!mymachine!you requires a hell of a lot of network connectivity knowledge! While saying "mit.edu will know what to do with this MIT address or else will let me know" is much easier and meets the "cloud" promise of the original 1970s TCP papers, even if the latter was talking solely about routing. The baroque (and transitional) email addresses described are actually appropriate: "I know some extra routing info and though I can't do it, SU-CSLI.ARPA can" (amusingly I used to use that very machine!)

And the same is true of the filesystem naming; while I agree that the VMS naming architecture was a bit baroque, the (optional) explicit version info was available to everyone, as if you could refer to a particular git revision from any program.
Yes, I can't see how anyone could think this is sane in any sense. Brb putting my kids in my GitHub profile picture.
Teach testing first
While a number of F-list celebrities like Paris Hilton deliberately released their sex tapes, the sex tapes of actresses and other celebrities released without their consent generally resulted in pretty heft settlements for the women, and in a few cases prison sentences for the distributors. (See e.g., Erin Andrews.)
I'm a Redux maintainer. I'd specifically encourage folks to take a look at our new Redux Starter Kit package [0]. It includes several utilities that add good opinionated defaults around the small Redux core to simplify common use cases, including store setup, defining reducers, immutable update logic, and even creating entire "slices" of state without writing any action creators or action types by hand.

Long-term, I want this to be the standard way that most people use Redux.

[0] https://redux-starter-kit.js.org
Perhaps you meant less than negligible? Or simply negligible? But not more.
Liabilities are liabilities. If you got hit by a truck tomorrow, you'd still be on the hook for your mortgage, but your earning ability will have diminished. If the stock market tanks tomorrow, you're still on the hook for your mortgage and there goes your investments.
Clusterfuzz: All your bug are belong to us
such that even if 4 fail, one grows 10x over 5 years

This seems really hard. Sounds like you're asking for some kind of coupling; a set of five stocks such that if any four of them go to zero, one of them will definitely multiply by ten. If anyone here could do that reliably, they wouldn't be here.

Whatever you end up investing in, don't forget to do it inside a taxfree ISA.
> Finally, efforts to police the literature need to be valued as highly as the publication of original data.

I don't think even the author would agree with this if it were about anyone other than them.
Qoa – Minimal interactive command-line prompts
https://www.theregister.co.uk/2006/09/22/ibm_power7_opteron/
People I know in big pharma companies have told me they first try to reproduce promising academic results before they invest a lot of money in further research, and that 70%+ of the time they fail to reproduce the results. This came up in conversation years ago when the "reproducibility crisis" first became a hot topic.

Other acquaintances of mine, who are in academia, did not find these results surprising at all. In fact, one added the observation that even when the experimental results can be duplicated, the conclusions of the study are probably still not valid because alternative, more mundane explanations are often overlooked, and the peer review process these days doesn't apply sufficient scrutiny or skepticism toward this.

I don't have any anecdotes on US vs. Japanese research.
What matters is whether AMI actually has the undisputed right to publish them, i.e., such as if the pictures are a clear matter of the public interest. If, however, AMI's actions could be tortious (or criminal), then threatening to publish can be blackmail depending on what they specifically threaten and the quid pro quo. If AMI's actions would be tortious, then threatening to publish is blackmail regardless of what they specifically threaten or the quid pro quo.
Vulnerable isn't broken
Oh great, another crypto shill looking to recruit new bagholders.
This. Although, with no more info to go on from the OP, my suggestion is: take flying lessons. It helped me a lot.
Buying Bitcoin as an "investment" is like buying baseball cards or Beanie Babies as an "investment".
I'd be curious how many of these actually provide real time guarantees the way QNX or VxWorks does. I think quite a few of them may simply be "embedded OS" rather than RTOS.
Sure, I get it. Perhaps I phrased my response poorly.

This comment:

> What needs to die is the belief that you can rely on just software (i.e. memory safety) for isolation between trusted and untrusted code

is an argument that doubting if statements should be acceptable, and that the assumption that only B has architecturally visible side effects when A is true is not sound. I disagree strongly with that.

You should be able to rely on software checks for some things. Going forward, the solution is not to rewrite software to not depend on software mechanisms (e.g. bounds checks) for protection (unclear what would be used instead...) but to fix the hardware so these software mechanisms work.

What needs to "die" is not "belief that you can rely on just software," but hardware that violates fundamental guarantees.

It sounds like we agree on this, I just wanted to make my point clear since I see now that my original comment was not clear.

FWIW, this is essentially the argument Torvalds made when Intel tried to add feature flags for non-broken speculation.
Thanks.

I will highly recommend reading this textbook along with RM Murray's "A Mathematical Introduction to Robotic Manipulation" [1]. Both of these textbooks provide very intuitive and clear cut explaination of principles behing robotic motion and planning.

I would also highly recommend completing a 5-course specialization on Coursera [2] by the same name as the first textbook. The course is conducted by the author, he uses plenty of great visualization to explain the concepts clearly and the course follows the textbook.

1. https://www.cds.caltech.edu/~murray/books/MLS/pdf/mls94-comp...

2. https://www.coursera.org/specializations/modernrobotics
Composer was a game changer. Instead of a monolithic framework you just compose your app with the dependencies it needs.

composer require guzzlehttp/guzzle

Now you have GuzzleHttp available to your app. This way you include only what is needed.
Uppercase is converted to added dashes. `document.body.dataset.instantAllowQueryString` corresponds to `data-instant-allow-query-string`.
I don't think the opinion expressed in that comment is as obvious or valueless as you say.

The article successfully manipulated me to only consider the heart-warming side of the situation, even though I have a disability myself (albeit a milder one, visual impairment with no impact on life expectancy). As I was growing up, the need to be independent was repeatedly emphasized to me. If the commenter's complementary opinion wasn't obvious to me, I expect it would be even less obvious to many readers.

Now, consider the negative consequences of a widely read article like this one for future people with that kind of disability. Will their parents or other involved adults even think about encouraging them to pursue a job or independence? I think not. That's why a comment like the one I pointed out here needs broader exposure.
react-easy-state for smaller projects, apollo for bigger ones.
This is true. Almost all algorithms that you might realistically need have been implemented, maybe not for your language, platform or architecture. Programming then boils down to taking it from one context and translating it to another.
I do not understand your distinction between prefect and fetch. You either have the data, and you need to notify other cores that you do or you don't.

Not notifying other CPUs seems pointless because before committing you would have to do a round-trip to the other core to verify whether the data is still valid making the prefetching pointless.
Git-history: Quickly browse the history of any GitHub file
The obvious wrong about Pacer is when a person doesn't have the financial means and wants to pursue by pro se.

The law was constructed in the interest of the public and self representation was deemed reasonable for justice to be always administered when a wrong has been committed and a person wants to seek a verdict.

Well if you're a person who has low finances and in a situation where no lawyer will take your case by interest or financial reasons. You can still file a lawsuit and have the filing fees waived. The problem will be how much it costs to print copies for yourself, the number of defendants and the judge (court). People underestimate how much is needed to print if you're unable to electronically file. Lawyers have access to the online filing system but pro se doesn't necessarily (depending on the state) and has to file in paper with mailing everything out.

Further more, the defendants may be a corporate entity with expensive lawyers on retainers, who have full access to every previous court verdict (similar to the situation) on PACER. They likely have a local database of the downloaded documents and where they can do advance searches. On the other hand the pro se is restricted by PACER in fear of the financial bill when searching and viewing documents to find something similar to his/her own situation.
> Just look at how the opinion about stretching changed

What happened with stretching? Did we formerly not like stretching, or did we formerly like it but no longer?
Reminds me of this optimization by Netflix: https://medium.com/dev-channel/a-netflix-web-performance-cas...

The talk (https://www.youtube.com/watch?v=V8oTJ8OZ5S0) was one of the most watchable performance optimization talks I've seen.

TLDR - they used a combination of the link prefetch technique, which works for HTML but is not fully supported by all browsers, as well as XHR prefetching, which will work for prefetching Javascript and CSS.
I’m on mobile so I can’t investigate further. Here’s a helpful link. 1.4 billion gallons in 2017 with most making it to Brazil and Canada.

https://www.eia.gov/todayinenergy/detail.php?id=35972
Nice idea for HTTP/1.x, however, isn't this what HTTP/2.0 [1] is meant to achieve by pushing components at the user?

1: https://en.wikipedia.org/wiki/HTTP/2_Server_Push
Live demo on my website @ https://sysadmincasts.com/

Temporary added it in-line for testing. I was already in the sub 100ms level but this just puts it over the top! Also updated all admin add/edit/delete/toggle/logout links with "data-no-instant". Pretty easy. Open developer preview and watch the network tab. Pretty neat to watch it prefetch! Thanks for creating this!

ps. Working on adding the license comment. I strip comments at the template parse level (working on that now).

pps. I was using https://developers.google.com/speed/pagespeed/insights/ to debug page speed before. Then working down the list of its suggestions. Scoring 98/100 on mobile and 100/100 on desktop. I ended up inlining some css, most images are converted to base64 and inlined (no extra http calls), heavy cache of db results on the backend, wrote the CMS in Go, using a CDN (with content cache), all to get to sub 100ms page loads. Pretty hilarious when you think about it but it works pretty well.
That's just semantics.

I was responding to this:

> No, increasing tips in the jar increases their pay proportionally.

For the tips that make up the margin between the tipped minimum wage and the standard minimum wage, their pay does not increase proportionally.
Except that we have vector spaces with scalars that are not the reals all the time. For instance, consider this excerpt from the article:

"Or perhaps they wouldn’t like A because the scalar field [the complex numbers] is the same as the set of vectors (unless, that is, they thought that the obvious scalars were the real numbers)."

In this case, while there is an an acknowledgement that you could take the reals as your scalars, it is regarded as the secondary of the "natural" choices.

Or, in my example, example, there is no way to view Q as a vector space over R, but it is clearly a vector space. There is an entire field of algebra (field theory), that relies on the fact that, for example, Q(sqrt(2)) is a 2 dimensional vectorspace over Q.
Long-term stock market returns are 9-10%. 7% is after inflation but that's acting on your mortgage as well. Mortgages are indeed cheap leverage for your savings portfolio as you're basically using as collateral a probably somewhat oversized asset, since most people could easily live in a smaller/simpler house if an unforeseen event happens. It's still a higher risk investment of course.