skysight-inc/HackerNews huggingface dataset:
That is not a new theory, the fake alien invasion has been going around for the last 2 years, and its roots are probably the Watchmen graphic novel, then later cowboy vs aliens.
The forum link on the site is broken. Assume everything is on their Slack channel now.

The link:

https://forum.apisyouwonthate.com/
My favorite is Expert C Programming: Deep C Secrets by Peter van der Linden. I started it as soon as I encountered C at university and could only get through about a chapter at a time. By third year when the assignments in C got hard I was in a great position, partly for this book. Even crazier is I enjoyed it.
+1 for the file interface
You forgot, they're nowhere as easy to remember as v4. If you're used to remembering phone numbers; important v4 IP's aren't that hard to mentally internalize.

Screw DNS. Screw the recommendation to stay away from IP's. If it's important enough to be on the network, it's important enough to have a static IP.
>Is there some discussion on the paper there?

Not yet, And likely not since they are video codec enthusiast. I just happen to submit the same thing on Doom9 a moment before this appeared on HN so I was wondering.
Lots of talk why you don’t really need to have compound documents anymore, but no real arguments why compound documents are bad. If your server and client architectures are somewhat sane adding a compound on-load resource is cheap and I don’t see many downsides. Maybe even pack them into your initial HTML.
> I would argue at this point in collective awareness of public communications, using a form of "sorry if I did any harm" regardless of specific words used is an explicit decision by the writer to not accept full culpability.

Based on my experience with the general public, with academics, and with industry folks, the criteria for what constitutes a sincere apology is not known by the majority. Furthermore, many of those who have heard the criteria do not accept it as a gold standard, and disagree with it (even those who are not being looked to for an apology).

The recipient can always choose to accept or not an apology. However, I find it quite distasteful to attribute intentions to someone simply because they did not follow a recipe (even if the choice not to was intentional).
That was the thing I notice as well. I guess it is some sort of Resume -Driven Development?
This is the part I'm personally most interested in. Research generally has pretty strict ethical regulations about consent. I'm wondering if this would qualify as a violation of any of their university's or the conference's rules.
London was never Gaelic. The populations living in Southern England would have spoken Brythonic languages, not Goidelic.

And at any rate... it's pretty obvious he was referring to Wuxi today. I don't think anybody's about to have an issue referring to the Sparta of today as insignificant, its historical significance being whatever it might be.
This article disagrees.

https://grammarist.com/usage/entitled-titled/
This is especially true since HTTP/2 uses TCP, and TCP is designed to interpret flaky wifi or cellular connections as congestion and become unusably slow. It's a fairly common situation in which you don't want to pay for additional round trips.
It seems like a nitpick to me, since the rest of the apology uses the proper choices of words, though. "The method used was inappropriate", "we made a mistake", etc.

The apology is also specific about what they did wrong despite their intentions. It really is a good apology after reading past the first six words.
4 years later and Id argue graphql is the clear market winner. Whether or not you really need it is debatable but its fashionable. Schema driven development and types have also been adopted along side that system so they sort of fit well together, too.
That's how security is tested. TSA undergoes undercover testing.

https://abcnews.go.com/US/tsa-fails-tests-latest-undercover-...
C-a is "go to beginning of line" in emacs-bindings for bash, which I use quite often...

There's no way to please everyone :-)
That’s responding to comments on HN. This apology wasn’t on HN.
Isn't that implying a more convoluted conspiracy?

Of course they could implement shadow-dislikes to prevent the dislikes from tabulating, but that requires more steps being taken.

Consider the ratio of views to likes/dislikes. Compare that ratio to other videos. It seems about par for the course. Also note that these videos have comments disabled.
What it means to be a science-literate citizen in a digital world
Europe is not a single country where all education systems work the same.
IANAL, but the claim that this research was exempt under 45 CFR 46.104(d)(2) seems suspect to me. (i) doesn't seem to apply because Linux kernel developers are required to go by their real names for licensing reasons (cf. the rules regarding Signed-off-by). (ii) seems dubious given that the authors themselves argue that they need reviewer consent to release information about the authors' malicious patches. Note in particular that both exemption categories are concerned with what information the researchers have ("information ... recorded" in (i), "any disclosure ... would not" in (ii)), not what they publish, so the idea that they need consent to publish this information seems to imply that they needed consent to collect it.
The only mitigating factor is that unlike the US the UK also massively underfunds prosecutions

https://thesecretbarrister.com/
Why do people assume that an Artificial Intelligence will want to do all the crappy human jobs?
Looks equivalent to python -m trace --trace, which is part of standard installation.
They are looking out for their own skin. NY and CA are bleeding people with money. People who pay those state taxes but soon won't.

I never thought I'd move for tax reasons. I am moving to TX this year.
Hair animation and rendering in the Nalu demo (2004)
That's my impression, too. I once did some research on toms for some audio code.

Toms are pretty tonal, as far as drums go, yet, as far as I could tell from my research there's no standard tuning for them. That would make sense if pop musicians all tuned their toms according to the music they were playing, but to the extent that they do, the tunings I read about were mostly flakey (ie: ungrounded in music theory)
This is correct, but any luxury spending is still better than non-luxury for the same amount. Private jets are probably the worst, and even them are much better per dollar spent than non-luxury equivalent: cost of fuel makes a much smaller fraction of trip costs than with airlines.
I mean, there’s all kinds of terrible unethical research.

What makes you think this isn’t research?
IPv6 on an internal network is trivial. It is supported by both Windows and MacOS (and Linux) out of the box.

If your ISP doesn't provide it, get one that does. They should allocate you a /56 by default per connection, if not something larger like a /48 if you have multiple locations.

Subnet the /48 for each connection, subnet each /56 into /64 subnets. reserve one of the /56's for site-to-site if needed.

Done.
This is a good point. Seems like there is reason to be optimistic. I certainly think it's possible for the US to be carbon neutral by 2050 - but ya'll better start banning gas cars sooner rather than later (seeing as modern cars will last 20-30 years).
I've gotten value from HTTP responses in the 300s, 400s, and 500s being handled appropriately by various tools without having to write special RPC logic for those cases. What am I missing?
To begin with, investment money were stolen from the largest Ukrainian bank via fake loans and investments. Hence the laundering. But instead of fake car wash sessions there were "for show" acquisitions: invest own money, quickly siphone them out of the business, sometimes but not necessarily making profit if lucky.
yeah - you shift the risk from the retailer onto the consumer.
Usually these deals will have some kind of faux-insurance arrangement baked in where the consumer will never have to pay more than something like $300/MWh
The title doesn’t match the article. It’s not about why toms descend in tone (typically - unless you are Jimmy Chamberlain and a handful of others). It’s about why toms have variable lengths.
So let that one entity be your browser vendor?

Also, the article says this product is primarily for enterprise customers, who need other features like sync across team and team access management.
The Ethics of Not Disclosing Vulnerabilities
Of Flying Cars and the Declining Rate of Profit (David Graeber, 2012)
The university should shoulder a huge degree of responsibility. They hired these "researchers". The apology should be coming from those who sponsored and funded the effort. Who cares about any "apology" these "researchers" cobbled together?
Maybe the sounds are too short to disturb the user’s perception of tonality?

Sure some people have the absolute ear (ability to tell a note from the sound), but those are rare and rarely enjoy music with drums.
Really? I unequivocally think it was unethical research, and thus a mistake.

But what’s the appropriate proportional response?

I honestly have a hard time thinking firing a bunch of people over this would be a good outcome for anyone.

What’s the end goal? I feel like already there’s been enough action to deter this kind of sneaky research in the future.

But at some point you’re just going to scare away the ethical researchers too.
> English might not be their first language (based on their name)

This is a pretty weak assumption. Someone's name (and physical appearance) don't give you an accurate information about anything.
The Nart Sagas, very old stories from the people of the northwest Caucasus (non-Indo-European speaking, arguably not "western civilization") have a very old story that is almost 1:1 with the prometheus story. It's possible that Greek traders on the black sea may have borrowed it from them. Or maybe it could go back even further, to the Maykop culture and its relationship with the nearby people who spoke Proto-Indo-European...

http://johncolarusso.net/pdf/Prometheus_among_the_Circassian...
Actually, I wasn't even aware that there is HN Algolia API :-)

From quick look, it seems the Algolia API offers a Search API which I don't think you can implement using the official API.

However, the official API seems to have a big advantage that it tells you which were the items that were updated recently - i.e. scores, comments, stories, etc. Using this you can implement real-time updates of the screen by fetching only the modified items. I believe using the Algolia API you would need to fetch everything over and over.

But other than that, the two APIs are similar. I guess the official one is more low-level than the other. The main difference is that you need to fetch the children one-by-one while with Algolia you seem to get this in one call.
ESL here. How correct is it to use ’any harm’ to mean ‘all harm’.
What about the risk to the reputation of anyone who approves these patches? Or of intentinally buggy patches making it into the wild and being exploited?
I have almost never encountered GraphQL in production, including when inspecting other sites. I think it's still a pretty small niche and mostly used on newer projects.
A Dead Game Clock
> Consent is only relevant when there is some risk to the subject

Says who? I don't think that's true according to IRB standards in the US. Nor is it true for websites who A/B test according to the GDPR
I wrote my own print debugging tracer. It’s now my goto for debugging most things.

https://github.com/elonvolo/logitall
An introduction to Kernel Exploitation Part 1: pwning.systems
It was a 2003 model, we kept 17 years. Oil and filter and fluids and engine mounts and that nasty judder which developed. We never got out the door under $300.
That a 404, 301, and 500 being generated by the API vs the web server are very different events and it’s hard to think of where “various tools” handling them the same is the right choice? What examples do you have where it’s the right choice?
And what happens if one sends gold over snailmail to a random address? You need to finish your analogy.
I guess I have to get the chart now.

https://i.imgur.com/3vYLQmm.png

The real world is more complicated than an old chart but it's definitely worth keeping in mind.

And supercomputers have been very helpful recently to design balanced tokamaks!
Dynamic Programming vs. Divide-and-Conquer (2018)
Solar shingles have been on the market from several companies for many years. They have never really taken off since they are a lot more expensive and have worse performance than regular solar panels.
New World Order? Locking down populations, forcing people to stay at home for extended periods of time, forcing them to take "medications" etc? Next step would be state enforced use of digital currencies, taking the control to next level.

Conspiracy theories, of course.
HTTP and REST are never reliably supported by clients. For example, many JavaScript clients will throw exceptions for 4xx and 5xx errors, even though handling 4xx errors in the client application is very reasonable.

Other clients only treat 5xx as a throwable exception, and some don't throw unless the request fails to hit the HTTP server.

Because of these issues, your best bet is to just wrap your HTTP API in a native client library. You certainly can't target a generic HTTP or REST wrapper.
Locus of Control
TSA agents are informed that there are tests as part of their job. See this comment for another example of informed consent in security testing

https://news.ycombinator.com/item?id=26929797
Is the author somehow implicitly assuming that APIs are only to be used between microservices in the same data center or something?

As far as I can see, the argument is "http2 removes handshake overhead and therefore you don't need to combine multiple things in a single response anymore".

If my request takes a second to go around the world and back, how does http2 help me? It's very weird to me to read an article about API design, written in an expert tone, that does not address this.
Science Shows Why Simplifying Is Hard and Complicating Is Easy
Resources like this are one of the things I miss most from the early internet. Most of the equivalents these days are just giant ads, machine generated, or both.
Mapped Types in TypeScript
> What about the risk to the reputation of anyone who approves these patches?

This is a risk, but it's exposing vulnerabilities is always preferable to leaving them in place.

> Or of intentinally buggy patches making it into the wild and being exploited?

There was no real risk of this. They specifically did not allow it to make its way into real releases.

If they had allowed it into actual releases, I would have a serious problem with that.
Discover Zero Day Exploits
A tom has a surprisingly long decay, so I think it's more a matter of the pitch not being entirely constant (neither between hits nor over the span of a single hit).

That being so, it would make sense to avoid hitting a tom with a low frequency note in unison with, say, a bass guitar playing the same note. That could result in two bassy notes sounding off a semitone apart... yuck.

Whatever sense my theory makes, I didn't read much about it being a consideration. I read about tunings, for example, that just pitched each drum up by exactly 3 or 4 or 5 semitones... seemed weird to me.
> Just as guitarists have cut back on amp power and now focus on tone

As much as I would like to think that this is true, all the concerts I went to prior to Covid had WAAAAAY too much freakin' bass. These were bands with vocal and guitar gods and the bass was cranked up to like 9000 such that you could barely make out the vocals and guitars if the bass was playing.

The best audio at a concert I had was the one where the house amplification system died, and band had to play with their on-stage amplification and nothing else. The sound from the band was amazing--the vocals were clear, the guitar parts were articulated, and the bass and drums were reasonable.

Funny how the bass levels are something reasonable when the bass player has to stand in front of the bass amplifier.

To be fair, I'm being a touch uncharitable. Most of the fault lies with the person running the sound mixing board. It seems most sound mixers are so used to dance, pop and rap that they can't conceive of the idea that something other than bass and drums exists in music. It also doesn't help that modern solid-state amplifiers can drive amazingly low frequencies and really high amplitudes that the old tube amplifiers with transformers simply couldn't deal with.
Pro Audio Forum Gearslutz Will Rebrand as Gearspace Following Name Controversy
The U.S. is increasingly alone, broke, and overweight
Many target formats do not support data sit subtitle streams, should de original contain then. So when using map 0, best then explicitly exclude those if you don’t care for them via -0:d? and -0:s? as we found out the hard way at Transloadit
Well, it is all contingent on someone getting high temperature superconductors to work on an industrial reliability level. If they manage, we will have power producing fusion (though probably not economically viable).

It is a big if, though.

Fusion has always been 20 years away, as it was always contingent on some science panning out, but the universe has not been in our favour so far. It is 20 years away, with some decent but <50% probability.
> Says who?

Me and common sense. I don't believe consent is relevant when there is no risk of harm to the subject. IRBs and the GDPR are overly aggressive on this point, probably as a reaction to real and important violations of privacy. But the idea that A/B testing the color of your CTA button on a landing page requires informed consent is absurd.
All new Renault models will rate drivers based on collected data
The relevant part, at the end of the article:

> Finally, de Meo said that Renault in collaboration with insurance companies will develop the “Safety Score”, a system that through sensors will collect data on the driver’s driving behavior in order to rate him, with the drivers with the highest score being those who are more careful. So they will be asked to pay cheaper premiums. There will also be a system, the “Safety Coach” which in collaboration with the “Safety Score” will encourage safer driving.
That's a problem I've noticed in two areas: programming resources and travel.

They tend to dump all the information and just state the facts. Very few make specific recommendations and the reasoning behind it.
Quick! Someone make a curated list of curated lists of lists!
There isn’t much difference and both are really correct. The problem with ‘any’ as raised here is the ambiguity. It could be taken to mean ‘any harm, if it occurred’ or ‘any single bit of harm that did occur’. So in this sense ‘all harm’ would be safer and less ambiguous.
And there's something to be said for batching -- if instead of requesting each resource individually, you ask for all of them simultaneously, the backend can see that context and fetch that data more efficiently.

In something truly RESTful (with HATEOAS and media types and all that jazz), the links between resources are only discoverable dynamically, and the client traverses that resource graph interactively. As the article explains, that works a lot better when you aren't scared of the per-request network overhead. But it still fundamentally limits the amount of context provided to the server on each interaction, preventing the server from optimizing for each request beyond guessing and pre-fetching what it thinks a client will need. (And the pre-fetched data has to live somewhere, meaning you've just created a cache and all its concomitant issues.)

Taking GraphQL as an alternative, the resource graph is statically known -- you can effectively fetch the schema just once. You can then traverse through many resource relationships and fetch many disparate units of data in a single request, and the backend can see that structure and decide how to efficiently gather all of that data.

Even besides the interaction context, doing REST properly (instead of a faux-REST actually-RPC HTTP API) can be pretty challenging. How many REST APIs are founded on media types instead of statically-determined URLs and methods? [0] If you're just doing HTTP RPC, you more-than-likely have a statically defined API schema, but no way to leverage that static knowledge for efficiency. (Instead you get clients coupling to the specific API endpoints instead of to the media types, making it not just static but also rigid.)

Also, HTTP/2 Push (mentioned in the article) seems to be in a weird place right now. [1]

[0] https://roy.gbiv.com/untangled/2008/rest-apis-must-be-hypert...

[1] https://evertpot.com/http-2-push-is-dead/
I use an open source password manager, but in the end, I still "trust a black box". I never looked into the source code in detail, nor would I have the knowledge to find some vulnerabilities that later can be used to expose my passwords. It might not be a black box for you, but for all intents and purposes it is for me.
The reputational damage to the department is staggering.
You can even just point Audacity at ffmpeg and it will use it to allow you to directly open .mp4 files and similar.
One reason is issues with property ownership. In the U.K. a company could do this but if the original customers were to see the house, they’d have no legal means of compelling the new owners to take up the arrangement. At least that’s what I understand.
In Australia, Commonwealth Bank (the largest bank here) is offering a $20000 "Green loan" at 1%.

That does more or less what you're asking for I think?
I'd highlight another aspect of these lists.

Although I don't find them too much useful either, it's good that there is _something_ which is "curated", so when I point a newbie to it, they can start looking around for alternative solutions / implementations / products-projects of a particular topic.

And when I say "newbie", sometimes, surprisingly, that can mean an experienced professional, who just wasn't exposed to that particular topic ever before...

These lists certainly have the risk of being too opinionated, and the reader being mislead into one or the other direction, so definitely have to be taken with a grain of salt.
I was in sane boat until I found a pirated version of a tutorial that took me through creating a house track from scratch. Brilliant fun. Total waste of my time though!
Isn't that handled with layer 2 retransmissions now?
I think it's fantastic that all contribution are included.

So much better than the politics of exclusion that often mean that mere (/s) programmers who implemented something never get acknowledged.
How Facebook encodes videos
What corporations are working to remove that ability?
I’m currently working on a project that sounds similar to this. A single server processes and aggregates steaming data with about 60Gbps of data. Customers want horizontal scalability and lots of buzz words are being suggested. A active-active configuration would be best (in my opinion) as that solves for redundancy and failover. Overall fun and challenging project. Somewhat frustrating at times though because of all the opinions of which technology or architecture would be “better”.
Not correct, at least in this context. "Any harm" means there could be no harm, or some harm, but "all harm" admits there was harm. I.e. "any" is not an admission of doing harm, or an acceptance that it happened.

If you want to apologise, "all harm" admits you caused harm, which seems necessary for an apology. "Any" is a bit like those "I'm sorry if you were offended" non-apologies, though in this case the rest of the message does better than that.
See also FBs very different approach: https://engineering.fb.com/2021/04/05/video-engineering/how-...
Is that surprising?
> But there's a thread every other week on HN discussing why rolling out devices with E-Ink by small companies is extraordinarily difficult.

where?