skysight-inc/HackerNews huggingface dataset:
It’s rationalised xenophobia. And quite a common rationalisation of the outside world being unclean or diseased. Why do you think unconnected tribes kill those who approach them? One reason is that it’s still in their cultural memory that the tribes who associated with the outside world died of influenza.

I know the ADF are auxiliaries, but they’re still there because the police is out in force.

In a few weeks Australia will have vaccinated most of its populace, but it’s genuinely an open question if they’ll stop their lock downs.
So to encourage merchants using Dip and Tap instead of swipe, brick and mortar cc processor companies said they no longer would cover fraud from cloned swipes. Sounds fine right? Except their own payment terminals after 2 or 3 dips/taps not working just go “fine just use swipe” -_-
It's an opinion piece in the culture section of the Free Beacon - what kind of article were you expecting (beyond 'bunch of anecdata').

FWIW I found it a hugely entertaining, and spectacularly well written piece.

As to your concern about the un-cited hypothetical tweet, a) on my reading of the article it was very much NOT ascribing much evidence to this phenomenon, and b) your favourite search engine will quickly reveal your answers if you ask for 'Laura Mulvey male gaze'.
That assumes the underlaying cause is known… and fixable.
I don't mean to get off topic, but I'm surprised the intern - presuming they're are a CS major or similar - didn't already know both. These tools are simply a reflection of data structures. Are such things no longer part of 100 or 200 level CS?
Wonder how much they make with ransom ware VS the Cia with drugs
North Korea’s Mysterious Cryptocurrency Ambitions
Author here.

Unfortunately, building on the oldest common ancestor will still not save you from ABI breaks. An example is [1]. If the size of `intmax_t` changes between that oldest ancestor and the machines you are running on, get ready for pain.

[1]: https://thephd.dev/intmax_t-hell-c++-c
SELECT p.ProductName
FROM Product AS p
JOIN ProductCategory pc ON (p.CategoryID = pc.CategoryID AND pc.CategoryName = "Dairy Products")

JOIN ProductCategory pc1 ON (p.CategoryID = pc1.CategoryID)
JOIN ProductCategory pc2 ON (pc1.ParentID = pc2.CategoryID AND pc2.CategoryName = "Dairy Products")

JOIN ProductCategory pc3 ON (p.CategoryID = pc3.CategoryID)
JOIN ProductCategory pc4 ON (pc3.ParentID = pc4.CategoryID)
JOIN ProductCategory pc5 ON (pc4.ParentID = pc5.CategoryID AND pc5.CategoryName = "Dairy Products");

-----------------------------------------------

MATCH (p:Product)-[:CATEGORY]->(l:ProductCategory)-[:PARENT*0..]->(:ProductCategory {name:"Dairy Products"})
RETURN p.name
Out of curiosity, why do you say that no mainstream examples are a good representation of the relational model?
Now I’m going to watch that. Thanks!
I never knew and could never imagine this abominable thing is required by law.
> But that sleight-of-hand hides the fact that many (perhaps even most) security fixes do not break the ABI or API; they are completely contained to the implementation (one obvious exception would be if the security issue was caused by bad API design, but even then often there are ways to fix it without breaking the ABI).

Right you are. I was also perplexed when I read that non sequitur. The author's reference to DLL Hell also suggests there's some confusion in his analysis of the underlying problem, given that DLL Hell is very specific to windows and at best is only orthogonally related to ABI. The author's references to API changes make even less sense, and definitely cast doubt over his insight into the issue.
Quote: "A lossless compression algorithm that can actually reduce the size of at least one input file must also necessarily expand the size of at least one other possible input file. This is a direct application of the pigeonhole principle. A compression algorithm that claims to never increase the size of any input, while at the same time reducing the size of at least some inputs (it's not the trivial do-nothing compression that, by definition, preserves the length of the input), is called paradoxical compression."

This paradoxical compression, as stated above is incomplete. You can achieve all input files to be compressed without having to expand any other file but you would expand time instead. Let me explain it: - Any set of data can be expressed using mathematical functions/algorithms that can be saved as one file, very small in data compared with original data, but to do so you'll need to invest a lot of time to find those functions/algorithms. One practical example would be a mission to Alpha Centauri which might want to have Earth's internet on board but no physical space for all that data. Let's say it takes 10 years to prepare the mission which in that case you'd also use this 10 years to compress, for argument sake, Google's big index, (or NSA Utah center if you like that one) and you'll have on board, on a single thumb stick, Internet version from 10 years before launch.

Edit: Since some people have problems understanding this extreme compression, I am trying to clarify this further. This method is unique to that set of data. And it can be applied to only that data, only one time and that's it. Not a general set of algorithms so you can compress anything else. It will fail if not applied to that data. It is not a classic compression, it is more, if you like the term, a data generator. It will run a program that at the end of its run will generate that Internet version you started with 10 years ago. But to do that you'll need to research how to do that data generating, hence the extreme time it takes to achieve. In practice I'll envision a lot of people getting their slice of data and do one function. And the program will run those functions one after another, generating the data.
A Deepness in the Sky is terrifying.
Mainstream media disagrees. In fact, cropping context is their main technique :-)
Perhaps Gonzo has been industrialized: “when the going gets weird, the weird turn pro.”
I think describing the notion of going without any, including life saving, medication as “abstinence from modern comforts” is uncharitable and unempathetic towards both the quality of life medicine can provide and the difficulties of being pregnant.
­>That's what you're doing by discounting what was a fairly popular political opinion of the time.

Yes, the US in the 1950s had a fairly high amount of absolutely insane but fairly popular political opinions. For example numerous generals were advocating massive nuclear strikes on North Korea and the dissemination of radioactive material on the border with China. That doesn't even begin to excuse anyone.

>None of that matters if you get hit with a Soviet first strike.

>The main goal wasn't to take out the conventional war machine, but the Soviet Nuclear capabilities. Counter force vs counter value.

The USSR had no ability to deal a debilitating first strike to the US.

>And this was before "Spheres of Influence" was accepted as a realistic possibility on either side, when the admitted Soviet policy was that communism had to be spread worldwide, even if it came to instigating war. So a first strike wasn't just thought possible, but expected.

This is nothing less than complete historical revisionism. By the 1920's the dogma of "socialism in one country" was official Soviet policy under Stalin. Anyone that disagreed that socialism only had to be realized in the USSR was contradicting the party line and subject to be purged at any moment. To be sure, the USSR still supported communist parties around the world, but it explicitly eschewed the invasion of countries to install communism, instead it would only be done if it was necessary to protect Soviet socialism.

The idea that communism had to be instigated by war around the world was Trotsky and co doctrine of "permanent revolution". Notably, the first was exiled and assassinated. This doctrine while in the early days relatively popular in the Party never came close to being the official position of the party.

See : https://en.wikipedia.org/wiki/Socialism_in_one_country
> the discussion gets filled with negativity and even, seemingly unprovoked, outright hostility toward the idea

"the discussion gets filled with negativity and even, seemingly unprovoked, outright hostility toward the IMPLEMENTATION" - here, I fixed it for you :)

If you will read any longer comments about crypto here, then most of them will approve THE IDEA of crypto, and half will admit that they were early supporters of it. But not now.
You can always ship it to the Internet Archive if she doesn't and you can't find a way to maintain an independent copy. Maybe by then you can set up some kind of organization like IA for the replication value.
It is a nice way to introduce people to the wonders of bookmarklet.

I think what you are doing can be implemented entirely in client side javascript. You seems to be doing some server side templating at least, which feels like unnecessary and can become a bottleneck.
Well, I hope that most people can agree that the USA and China both have huge corruption problems, but in different forms.
We watch too much porn and too much sports – and it’s weakening us
New Batteries Make Everything Better
Hardly. The religious ritual is just bury in the ground. I'm not sure it even involved even coffins originally.
I remember reading that blog post at the time and being flabbergasted.

If I remember the details correctly HBO wanted to do a cut similar to the Netflix one and Simon (and maybe others?) Went back through the entire series and meticulously edited the shots to still have the same meaning / context.

The result by the way is incredible. The Wire is one of my favorite shows of all time anyway, but the fact that you can watch it today in such high quality is a real delight.
That's pretty much what I mean by a solid foundation... Built on sand.
I don't think you could expect this to do any better, though. Apparently this algorithm uses DEFLATE under the hood
Anybody who claims to "know how the economy works" definitely does not know how the economy works.

It's pretty sad that one economist pointing this out is a big deal.

It's the result of echo chambers like HN.
"Make it look dated" is just not a good argument.

There is no good argument. Cropping out huge amounts of the actual material is not justifiable. End of story.
How would you have told the story of Bridgerton without sex scenes?
Actual answer: Because the code management system is built with certain merge restrictions:

- A PR can be merged with 50 or more code reviews and approvals if it has 0 rejections

- If there are any rejections, the requirement is a little more intense, at 60 or more code reviews and approvals

- Once per year, one PR can be merged per year with 50 code-review approvals and any number of rejections.

- The company has 100 developers and at least 41 will reject every single PR summited for review

- It takes agreement of 50 developers to change the merge rules, and there are 48 or fewer who want to do so

This is why there are so many unrelated changes in one PR. It's probably the only one they will be able to merge this year.
And was kind of fixed with application manifests, on XP.
So your reference is something else you wrote?

I'd love to see some other references if have any.

It's a bold claim (from the linked article) to say that:

> Black Widow was fully created with motion capture ("pre-visualization") before a script was even written
That's only true because the electric motors don't have a gearbox but the gas engines do.
Alexis King had a talk about Hackett, a sadly abandoned, metaprogrammable haskell: https://youtu.be/5QQdI3P7MdY
It's not really the same issue though, with The Wire they had access to original master footage that had a wider view, so the 16:9 versions didn't crop into the 4:3 footage, it just added footage on the sides of the image.

https://i.imgur.com/SK1sPD9.jpg
I'd contest your points 2 and 3 from a business application perspective.

Relational DB's resemble ledgers from a business perspective. Most business apps and nearly all financial apps think in terms of ledgers of transactions. Go one to two degrees of separation from a financial transaction in any web app these days and the users of that system will want to line up other activity/transactions in the app with the financial ledger. Then they want to ask questions and have reports on things like: how many users for that customer? how many purchases this month for that customer? what did they purchase? etc.

I think its historical and historical also implies the vast majority of systems aren't likely to change if there is some-other-tech that may be easier to work with. Its a safer decision to pick well known tech because you'll know the trade-offs, support issues, hiring parameters, etc. from the history of all that came before you. To reverse that point - picking some esoteric language/db solution increases the risk of a product/project failing, not because of the technology but all the other factors that surround that technology.
Spot on. The film can also be cleaned, restabilized, and restored using certain chemical agents but it's a risky procedure so most of the remastering is done post-process digitally after importing it using better scanners like you mentioned.

Film grains will always set a limit for how much resolution we extract from old film but it's really high. Current methods yield 4K to 8K from 35mm film but odds are with better interpolation technology that understands the interaction of light with the random spacing of the film grains, we could probably get something on the verge of 16K. No one has 16K TVs though, so it's a rather pointless exercise right now.

Still makes me curious, how much information is actually lost versus just computationally/physically obscured..
The "Simpsons" on FXX is unwatchable. It's cropped/blown up to 16:9 and it looks like they took a scan meant for HD resolution and blew that up, so everything looks jaggy and blurry.
For another striking example of this, see the original Star Trek series. It now looks 10x better than it ever did when originally shown on TV.
> That seems to be the Go and Rust default approach

I think Go tried to go fully static but ran into problems as most mainstream OSes except for Linux do not provide a stable system call interface, so applications have to link at least one dynamic library. The Linux system call interface is stable, but expects a C style stack layout and that also bit the Go devs. multiple times. So you can probably go fully static if you are only targeting Linux.
There exist a few products targeted at enterprises that attempt to detect suspicious patterns of encrypting files at the OS and/or backup level and flag that if it happens.

I wouldn't describe that as the "best" defense though, it's an "earlier warning system" but not early enough to prevent damage. You've already been hacked, the criminals have already exfiltrated all the data they can, have already installed whatever backdoors they are going to, and have even already started preventing you from accessing some of your own data. (That doesn't mean earlier warning doesn't help, and it's probably worthwhile, but it's a component in a broader last line of defense system that you never want to use in the first place).

The best defense is not getting hacked in the first place, and not letting malware spread when you do. If you are a big enough target that the "detect ransomware" solutions are remotely affordable you should hire some experts on this topic, but think about things like good phishing training, good firewalls, good software engineering, keeping everything entirely up to date, and so on and so forth.

Backups help (a lot!) but are not the cure all that people like to pretend they are. Apart from all the other damage hackers do apart from deleting things, hackers do attempt to delete backups too, and sometimes they succeed.

(Disclaimer: I use to work on one of these products)
Nevertheless, I've read some people in Africa have already evolved to become immune.
Related discussion: https://news.ycombinator.com/item?id=28735314
It’s a show about horny confused teenagers being married off to each other in some alternative history. Sex scenes couldn’t be more relevant to this show.
which ironically really hurt their ARM adoption. Apple devs already know the rules are going to change on them whenever apple feels like it, so people aren't as stubborn about it. Of course I don't think that strategy would have worked for microsoft to begin with
> Black Widow was fully created with motion capture ("pre-visualization") before a script was even written.

That sounds very unlikely and I'd need a better citation. And pre-visualization doesn't really mean what they seem to be using it to mean here.

Edit: It seems like this is you trying to promote your Hollywood startup, rather than an accurate assessment of how things are currently done in Hollywood.
> > The entire concept of “need” and what is “helpful” is ideological

> How so?

Because both are meaningful only in the context of a particular value system.

> Is it objectively good

No, “good” is inherently relative to a value system; “objectively good” is an oxymoron. That's the point.
One of my favorite images from the book is a fleeting mention of a star system that has been completely taken over by the sinister ancient AI (that is capable of leaping into the material world). Just a glimpse of enormous struts connecting the planets ...
This is the best rebuttal to my thesis. Thanks.

There is a tension between art and commercial art. Beethoven should have never written that battle symphony.

When done well, I think you can get both. Start with the story and then weave in the commercial aspects. Or start with the story and only choose to finance movies that have both art and commercial value. What you can't do is start with the commercial side and then try to hammer in a good story. There have been a few masters that managed to pull that off, but it's rare. Add in committee-management instead of having an artist's eye and it becomes total crap.

It's in nobody's interest to only have arthouse flicks that nobody watches. Happily it's not an either-or decision. Good drama will draw in the commercial part than can then be exploited. Everybody's happy. What I'm seeing now is that majority of films start with a locked-in fanbase and then try to do their best at creating an n+1 episode. That's how they're getting around the quality problem: they make it moot. They know the locked-in fanbase is coming no matter what they produce, and if it's a real stinker? Well hell, all of the press and arguing about how bad it is will just drive up interest for n+2. Not only is that not trying to mix a good story in with a commercial line, that's putting the story quality pretty far down the list. It's noticeable.

ADD: I'd say that in the heyday of arthouse flicks, say 65-80, you had the peak of movies that covered both bases well. Nobody's doing another Midnight Cowboy.
I read the article and didn't have your reaction! Or, I long since, for years, often had your reaction and finally for nearly all media gave up!

Soooo, instead of your reaction I just backed off and decided to regard any and all statements in such media content as, call it, "conjectures that some people want to pass out guessing that maybe some other people will agree".

That is, we get a lot of conjectures! I can like getting some of the conjectures since commonly they are not ones I would think of -- so, maybe there is some value there, e.g., not that the conjectures make any real sense but, say, just that they are maybe (another conjecture!) that some people would entertain in which case we might get some insight into some people! See, if strain enough, bend over backwards and twist self out of shape, discard nearly all sense of rationalism and critical thinking, can find a glimmer of value!!

Then the article mentioned Anya Taylor-Joy: Never heard of her, so did a fast Google search and got caught up. Yup, of the several pictures of her one of them to my eyes did have "almost-alien beauty"; that picture, if only from some lighting, seemed to have the part of her nose between her eyes unusually wide.

Besides, have to give a little value for the rough, guesstimate conjecture:

"(Congrats: You're caught up on the last 30 years or so of the theatrical exhibition business.)"

Maybe some such thing is true, maybe!

Net: It's easy to read such media criticism -- just set aside all rationality directly on the content and look, instead, at the content as maybe some insight into what some people might believe! That is, we should have some good insight into what nonsense some people might believe, that is, we might be learning about the people, not the nonsense! It's not difficult; you can do it, too!
Still seems problematic to use 'life expectancy' at all to me, since the at birth and early years lines are still affected. Wouldn't it be better to show something like 'probability of living another ten years' (at birth/each of x years old)? I'm no statistician.
Sorry, I don't understand, is the pen too thin for your hand or is it for the pen holder?

Wouldn't something like a few cm of a - proper sized - rubber tube/pipe do?

Or one or more layers of heat shrink tube?
Why shouldn't it apply to the HN comment section?
I'll give the dissenting opinion: not every story needs to be a love story, unless the movie is about sex it shouldn't have a sex scene. It was infuriating how "love story" and "sex scene" were mandatory tick boxes on every single movie in the 80s and 90s, regardless of if the plot called for it or not.
Some people use Nix to build Docker images. They say it's very good for that.
I imagine the situation will improve in the future with TVs that have one or two on-board cores for handling trained models (like Apple's newer chips) that can run models trained on editorial pan-and-scans and try to apply it as an alternative to scaling.
A pretty simple solution to this is to call trans women ‘trans women’. Or just ‘men’. Since they’re male.
Author here.

Sure, most security fixes do not break the ABI or API. But it only takes one, and then you have a security issue.

So I can understand your sentiment that it was sleight-of-hand, but I argue that it's not.

Also, we only think that most security updates don't break API or ABI because we have no automatic way of checking. It's all thoughts and prayers. I'm a religious person, but thoughts and prayers are not a good way to do computer security.
Yeah, for protecting against ransomware, the computers you are backing-up must not have permission to write in your backups, and the place you are writing your backups on must not have the same security flaws as them.

Both offline media and well configured S3 can do. Although, I'd personally bet much more on my capacity of configuring a server than S3. Anyway, you can't go wrong with offline. The one thing you can't have is a NAS where your computers directly write the data.
This is incorrect. If you would like to encode every string that's 10 gigabytes long to a string that's at least 1 byte shorter, then you don't have enough strings that are at least 1 byte shorter. There are fewer of them by a factor of about 256, and each one of them can decode to only one 10-gigabyte-long string. This is explained in the article.
> End user of a linker?

I'd argue that if you're not packaging your software or testing your software's dependencies, either you're doing something extremely exotic that lies far outside anyone's happy path or "dylib error" should not even be a keyword in your vocabulary.