skysight-inc/HackerNews huggingface dataset:
The xz backdoor had nothing to do with SSH (protocol) or OpenSSH. A Debian version of OpenSSH became potentially vulnerable because of a package maintainer decision to patch OpenSSH.

One could make an argument that no one should be using packages from (Debian) package maintainers. The origin of the xz backdoor in relation to SSH was a Debian package maintainer patching OpenSSH in an effort to support systemd.

Recall Debian's OpenSSL patch:

https://freedom-to-tinker.com/2013/09/20/software-transparen...

FWIW, the xz backdoor had zero potential effect on people using OpenSSH compiled from source without patches. (I do this b/c I prefer static binaries and dislike package managers.) The worst potential risk of the xz backdoor, IMO, was libarchive's use of xz project. After the backdoor was announced, I re-compiled libarchive without xz support:

configure --without-lzma
Anything you could do? What do you mean by that? Did you mean you "couldn't do"?
This is what happens when Trump "drains the swamp" and appoints dipshit leaders to critical infrastructure.
I'm very uneasy about us collectively seeking longer lifespans. Earth is already supporting more people than is sustainable. Living longer robs someone else of an opportunity to live, or a shorter life. Over many generations we may be able to lower our birthrate to compensate, but I worry about happens in the meantime.
In short, we practice passive consent. Consent could be either active or passive when recording calls.

Sources:

1.) https://www.bluedothq.com/blog/call-recording-laws#:~:text=S....

2.) https://www.avoma.com/blog/call-recording-laws

Here, the audio cue can be labeled as the AI voice itself as there is no regulation surrounding what exactly the audio cue should be.

So the recording is the default but I encourage you to always inform people and ask if that is okay before you ask Mitra to call them.

Mitra never makes calls to someone unless you specifically ask it to.
I’m guessing they meant population being smaller.
It's a culture issue. The culture of the teams they are.. Offshoring ownership of these projects to.

A lot goes into company and team culture, but I'm sure a lot here are familiar with the dynamics of outsourced development; offshore or not. Blame seeking, blame shifting, CYA, etc.. "by design"..

It's all on full display in Microsofts Azure GitHub repos.
In some ways, this mutual acceptance defines both of them as realpolitik opportunists. I think we should judge them on their deeds, not on inherent contradictory states of their postures. Musk is a media tart. He does things for the clicks. Vance likewise. Their financial acumen is however variable. There usually is a belief in some upside.

Musk will fund the republican campaign. Vance may have a titular position but without massive change will only verbally affect legislative outcomes, other people enact it and decide them. He gets to make noise as much as the leash around the VP role permits.

His heartbeat-away function is different and his posture would change accordingly.

If Musk puts a battery factory or car assembly plant in ex coal economy seats and has jobs, watch Vance backpedalling.
The original approval for VIPER was $433M. So at one time they thought that VIPER was worth $433M. Now they need $100M+ to finish it. If it was worth $433M at one point, surely it's worth at least $100M now?
> Nadella has created a trillion dollars of value

You mean that he happened to be CEO during a period when market value increased due to a number of factors beyond his control or influence.
> This control is not a sign of anticompetitive conduct, quite the opposite.

Then how is Apple afraid that it cannot compete with the alternatives?
MS Teams: Announcing that Firefox isn’t supported and you need to use Chrome or Edge, but if you hit ‘back’ at the right time everything works fine.

Sketchy online stores: “Sale ends in <time counting down>” but the time is just a random duration generated in JavaScript.

Autodesk: “Auto-renew Fusion 360 or you’ll lose your SPECIAL PRICING!” The ‘special pricing’ is full price. Their web store has a 25%-off sale on.
Oh cool, Snek and the Snekboard. Snekboard is one of the few controller boards that supports 4 motors. Pet peeve is needing 2 boards to run 4 motors. Snekboard was awesome. And it was one of the few boards 5 years ago that came with the things needed to adapt it to Lego. It is a great example that had everything you needed, not another dozen libraries to load.

Thanks for the memory trip!
> When they get things right it’s because they are lucky.

This is transparently wrong. It gets so many things right in a response that the few things it gets wrong are tremendously frustrating. I think people underestimate how much correct "knowledge about the world" is expressed in a typical chat gpt response and focus only on the parts that are incorrect.

If it were wrong about _everything_ at rates no better than chance, we wouldn't even be having this conversation because nobody would be using them.
> Clearly, no-one should ever _use_ this

…without validating the results. Otherwise why should we ever use LLMs for anything?
Trust as a term is a bit overloaded. For software teams, I find “trust” can often be a shared lingo, shared mental model, and shared expectations. The first two can be easier if the two sides both use the same programming language and internal libraries. The latter can be hard, especially if the two sides have different Product Managers.

The OP alludes to ‘what trust is’ mentioning the ‘Dario simulator’ issue. Trouble arises when ‘the Dario’ holds a vision that might conflict with the team or the outside world.
Then state the obvious for me please because I don't think it is. I don't see how, in a multi-ethnic nation, making the neutral use of a name (in the case the use is actually positive) exclusionary to specific ethnicities is progress. It seems like a regression in our culture that we are having tribal quibbles over immaterial usage of language.
I'm running one of these now, interestingly enough. Apparently something's broken in OpenJDK if you build with the new Xcode. So I'm bisecting on all the files (choosing either the old or new compiler) trying to see which one is breaking things.
They won't know you're American until you open your mouth. There is such a wide variety of phenotypes in SPB that people will just assume you are a Russian. Russians these days mostly have friendly excited reactions to foreigners speaking English in public.
I am not sure this site is web scale. The cats page probably needs its own microservice, backed by Kafka and DynamoDB. I mean, it's simple.
At risk of derailing the conversation, I finished Cryptonomicon earlier this year and really enjoyed it. Any recommendations for similar books?
You can use this for any codebase of sufficient complexity where you want to identify which change is causing the effect you're observing.
Azure DevOps is totally down too, to the extent that I can't even git push to a remote hosted there (get a 503 response).

Something very critical has fallen over.

Edit: I don't think this is for everyone though - maybe only if your ADO instance happens to be hosted in US Central?
How to master multi-tenant data management?
Props on them for fixing this. Spent all day tracing down why my deploys were failing; turns out it was way way way upstream of my code, into the latest node docker container facepalm
Yeah, right. I will make one generalization though. I've rarely ever had a problem on purely technical points, either I acknowledge I'm wrong or we agree we've been arguing at cross purposes and it's resolved. Even one 'sticky' discussion that involved the controversial sugar substitute aspartame and the correctness of the Wiki entry was largely resolved when we agreed we were arguing at cross purposes. (As you likely know discussions about aspartame can get very heated).

From my experience, the point you're making almost always arises from controversial topics or ones that are or can be construed as political. For example, I remember when HN deleted a thread on veganism. Discussion started out civilized but eventually went ary after an extremist made statements that no reasonable person would have considered correct. Backlash followed from multiple posters and HN ended what was no longer a discussion but a heated argument.
There's a brief scene in Heavens River, book 4 of the Bobiverse series, where some characters spend some time with the equivalent of alien dolphins. The "dolphins" have a very limited language that main consists of names and one word inquiries and warnings.

For example, the local replicant who they know introduces his fellows. The dolphin speech is essentially "who? Marvin! Marvin friends?"

Which is basically "Who are the strangers? Oh it's Marvin! Marvin, are these your friends?"

I imagine most animal languages are at this level. And nothing wrong with that. For their lifestyles, many intelligent animals with a language like this are served perfectly well. Personal identifiers to call out friendly individuals, names for threats, maybe even general welcomes for fellow groups like elephants and whales that generally live in family groups and occasionally meet up for mating or due to resource constraints like grazing and seasonal water construction.
There's only one, but: https://en.wikipedia.org/wiki/Ellipsis#In_writing
Taiwan does not need to start a nuclear program. Taiwan has previously completed everything except final assembly of a nuke, so they have the capability in principle. There are a number of countries that have never built nukes but that are believed to possess all of necessary components to rapidly assemble nukes should they feel it necessary, it is a gray area in nuclear non-proliferation. For international accounting purposes, a disassembled warhead sitting on a shelf somewhere doesn't count as a nuke, they only count systems.

Invasions are unavoidably telegraphed months ahead of time, which is more than enough time to assemble a nuke if you have already have the components.
I've never heard of this. Can you provide links to any scientific data to corroborate this theory?
Dam, the angry backlash mindset shows up like clockwork, complete with my favorite triad of its hallmarks - vague references to "philosophers", invocation of numbers with the specific intent of saying buckwild unquantifiable shit, and the combination of personal attacks frothing with derision while simultaneously accusing me of thinking with "mindless emotions" for, I'm pretty sure, using language you've pattern-matched as overly compassionate toward things you don't respect

Anyway, I'm trying to get into less pointless arguments with people who open by demonstrating themselves unamenable to reason this week. Shoo, fly
Telekom Security: Revocation delay for TLS certificates
It’s used incorrectly. Hallucination has (or used to have) a very specific meaning in machine learning. All hallucinations are errors but not all errors are hallucinations.
This is not what hallucination means in the pre-LLM machine learning literature.
I found this inspector useful, too: https://mlynoteka.mlyn.org/mp4parser/
FusionAuth Simple Themes Walkthrough [video]
I don't understand "why" he must understand how software development works.

Is he making unrealistic requests?

Does he think you are wasting your whole day in notepad instead of doing real work?

When you tell him about a new cool rebase trick in git, he only stares without understanding a word?

Anyway, a book is too long. My recommendation is to try to find some nice post in the old blog of Joel Spolsky https://www.joelonsoftware.com/
It’s also something that LLMs generate really well. So you can build reasonably complex scripts with little knowledge of bash.
In the context of LLMs, that is truth, as anyone would understand it. Humans are also sensitive to recurring or consistent input in our training data.
The article doesn't seem to address the main reason I learn not to trust some people: They aren't trustworthy.

At my last job I was on a project with two other developers, two data scientists, and a project manager. At the outset of the project I mostly trusted people to do their jobs. I'd only worked closely with one of the developers, but I'd had enough incidental contact to have a good opinion of everyone else. We divided the work up and made a decent plan early on. Then things fell apart.

One of the developers had a single 3-point spike story open for the whole quarter. He made one boilerplate PR and left no comments in any other PR. He regularly missed meetings and didn't add to any discussions. He talked a big game and never delivered.

One of the data scientists took six months to make an extremely simple model. He made the only PR for it on the last day of the quarter before he got switched to another project. He wouldn't answer any questions whatsoever about how the model worked. It was inefficient and not ready for use. I had to rewrite the model.

The project manager never wrote anything except titles in Jira tickets. He repeatedly didn't follow up on questions, even when we had a clear issue needing feedback from the customer, whom only he could talk to. He was completely oblivious to the lack of progress above, despite never seeing a demo from those people.

Luckily, the other developer and the other data scientist were capable and accomplished part of what was needed. The project was still a disaster because we had the software equipment of a car without wheels. I spent half a year begging my manager to move me to another project when I realized it was going this way.

I love to trust people. It's how I work. I tell you what I'm going to accomplish and I do it, every time. I expect the same from others. I don't care about performance as much as I care about doing what you say you will. There isn't a model to build trust with untrustworthy people.
Functions as a Service (FaaS) serverless platforms that run on Kubernetes
> Over many generations we may be able to lower our birthrate to compensate

Already on it, boss!
Depends on how much you want to spend, though some low price units often hit well above their weight, it seems.

It also depends where you stand ethically - for example, Hikvision often makes great stuff, but they also literally built a camera with an AI built-in that identifies Uyghur people and triggers an alarm if it does.

The Hook Up does reviews heavily focused on image quality, and setup/installation, both physically and network/software wise. He often covers a wide range of price points instead of just focusing on cheap stuff or expensive stuff, and does image tests in daylight, nighttime, stationary, moving, license plate and person, etc. Even does edge-of-the-lens tests to find cameras that have crappy lenses.

The current 'hotness' would be low-light color cameras; sensors have gotten good enough that some ambient light will do, and the color helps with IDing people's clothing, and cars. Potentially license plates, too.

Most current review:
https://www.youtube.com/watch?v=a3G_2zVu3cU

He's also done probably one of the most technically competent reviews of LED light bulbs I've seen in ages.
> Since this is 1983, he's obviously talking about IBM PCs[1] and DOS[2]

More likely, he was talking about CP/M, Commodore's C64 or earlier systems, Apple II, or mainframe/midrange terminal systems including Unix since

> it was not until 1984 that IBM PC and clones became the dominant computers [1].

[1]: https://en.m.wikipedia.org/wiki/Influence_of_the_IBM_PC_on_t...
Typed Clojure is interesting. However, until two months ago, it was practically unusable for most Clojure projects because of the lack of type inference in higher-order functions. This has changed, but there's another huge problem: nobody maintains type declarations for widely used libraries. If you look at alternatives to TypeScript, such as ReScript, you will find similar issues.

I still use Clojure, but I am fully aware of the kind of bugs to expect down the road. Typed Clojure would work if I could maintain types for each library I use, but that is simply too much effort on my part.

As for clojure.spec, I already addressed this in my post, but I will state the following.

Schema, Malli, and Spec are not substitutes for a type system. Each of these libraries explicitly state so. You still need to enable instrumentation and run erroneous code violating some contract. Most Clojure programmers have the habit of enabling instrumentation in dev and disabling it in production because validation is an expensive operation. I personally use Malli for data validation and coercion, but it does not make refactoring any easier, nor does it help autocomplete and other development-related tooling.

(Someone will probably link a malli document demonstrating clj-kondo linter generation, but even that is not a substitute. At best it detects arity errors and primitive type mismatches, not the shape of data in a map).
I'm not sure whether your statue is meant as an analogy for the universe as a whole, or life on earth, or what. But whatever specific thing you have in mind, it's obviously false that "only after centuries of forced re-education" that people began to think ... well, anything, actually. Because then what motivated the "forced re-education" in the first place?
A solid 70% of pop up ads in 1999 were for X-10 systems.
Thanks! It will keep improving it!
But it's literally referred to as "secondary memory" in ye olde literature (where "primary memory" is the RAM... I wonder why the CPU cache never got a place though).
You'd be surprised actually. Once you factor in network costs, running your own on AWS is only ~50% cheaper than paying for SaaS.

Factor in the opportunity cost you pay by having to have a person manage a self-hosted CI/CD cluster rather than outsourcing it, and SaaS CI/CD is around 3x better value than self-hosted.

Happy to share more detailed numbers if people are curious...
Snowcrash?
REAMDE was also good.
I came to the same conclusion in business. Is what you're doing 100% pure pain? Good. It means you're providing value.
If you're a computer nerd, yes, definitely.

There are plenty of people I wouldn't recommend it to, though.
> I'm not "formally" trained in software engineering and am primarily self-taught

Welcome to the club and I wouldn't be too worried about it (but definitely read and learn what others have figured out).

Software design and development is still an unsolved problem. The industry has not collectively found a foundational set of standard practices that apply across the board other than some of the most basic (e.g. organization is good).

You can tell that it's not solved by the relentless flow of industry trends that become the new "best practice" until some years later when we figure out "well, that approach has these pros and these cons and tends to fit with these types of problems, but definitely not a silver bullet, let's try the next thing"

Regarding your specific issue on your new project: just be pragmatic, get it working and learn from your decisions, it's all just a collection of pros and cons and the analysis of pro vs con changes depending on the angle you look at it (e.g. short term vs long term, slow changing environment vs fast changing environment, cost to value ratio, etc., etc., etc.)
Elligator is only tangentially relevant to the hashing problem. If "doesn't have a problematic structure" is understood in a weak sense, then this was already solved by Shallue and van de Woestijne almost a decade prior to the Elligator paper. And if it is understood in the stronger sense of indifferentiability, then Elligator by itself doesn't actually fit the bill, and you need something like the Brier et al. approach or SwiftEC.

The steganography stuff is the only actually novel contribution of the Elligator paper.
I can't agree with this, because it creates a "barrier of entry" for people building new browsers. Old things should deprecate when new things do them better, and deprecated things should phase out.

Otherwise, we're stuck with Chrome Forever. I'd rather not.
Can that only be done in an office?
The “real” Tony Stark to Elon’s Justin Hammer?
This seems insanely cool
Back in the day, people wanted to build a sustainable, long-term business. Now they just want to create profits, and it often happens by dismantling these great decades-old companies brick by brick, until the line don't go up no more. Then you collect your bonus and move on to the next victim. GE and Boeing have been gutted. What valuable company is next?

We live in a time when the incentives are ass-backwards. Your customers should be first, your employees second, and only then, all the way in the back, are your shareholders. When the shareholders are placed first, you find yourself in broken, late-stage capitalism.
Libsql fork has good rust <-> node async, you could look at them for inspiration. Maintained by Turso.
> after the recent xz backdoor, combined with the fact sshd runs as root, we probably shouldn't use SSH for everything

Independent sshd implementations with the potential of having neither issue do exist [1]

And many httpd's run as root as an easy way to bind to :80. Not strictly necessary either.

[1] https://docs.gitlab.com/ee/administration/operations/gitlab_...
How to avoid frustration with software architecture
What you want to do isn't really what the HAMs want you to be doing anyway.

128-1024 Kbps generally means a ridiculously large bandwidth compared to what most HAM channels allow unless you're really close to your recipient and can use a very wide QAM modulation, in which case your equipment is going to be $$. Your best bet is to stick to the ISM bands, which is where WiFi is anyway.
Err... The Japanese constitution is by definition unreadable if you can't read Japanese.

If you can read Japanese though, this is incredibly elegant!
> I'd love to see an alternate timeline where one of these giant companies took their trillions of dollars and said "You know what, fuck you, shareholders! We're going to be pure research now!

If this alternate timeline where giant companies are autonomous creatures were to be, why would there be shareholders?
From the Wikipedia page for "schnapps":
"Schnapps or schnaps is a type of alcoholic beverage that may take several forms, including distilled fruit brandies, ..."
> Whether or not you're comfortable having sex with someone who is HIV+ but claims to have an undetectable viral load is a separate question entirely.

If someone has HIV, they would have to be extremely suicidal to forego taking the medication that would make them undetectable.
One way to avoid this kind of misunderstanding - after you draft such a comment, imagine you were berated by a moderator (or another user, like here https://news.ycombinator.com/item?id=40997406) then write the clarifying response (i.e. the "All I'm saying [...]" in this case). Throw away that first version and post the hypothetical response instead.
A hah, that sounds cool, looking forward to the writeup!
Yes! Currently, I have just made it work so that I can take notes. There are three stages in my timeline:

1. From now until 7/31, it is alpha testing. I will test its basic functions during this stage.
2. Beta testing will start on 8/1. I will keep improving the basic functions and also develop the desktop app version during this stage.
3. When version 1.0.0 is officially launched, I will publish the desktop app.
This is my plan :)
Salesforce mandates October return to office for most, as layoffs continue
They've been bred for that for hundreds of generations.

Go find a wild bison and see how it behaves. I've chased herds of wild bison on many occasions - they are NOT like domestic cows.

Same story for mountain lions and lynx, etc. They are a far cry from cats.

Having our tiny falling down cabin surrounded by wolves in the Yukon at -44 degrees makes you appreciate how far THOSE are from house dogs.
HTML 3.2 is still out there! Just use it.
Issues with VSCode Marketplace as well.
Are self hosted runners down as well?