MurphyA/hacker-news huggingface dataset:
by mastazi | 2025-11-23 01:18:11+00:00
I am Italian, that was one of the proudest moment in our history.

The Achille Lauro episode was an example of Italy choosing what's best for the region rather than what's best for the people across the Atlantic. Hundreds of hostages' lives were saved by the actions of the Italian Government that day.

For context, in the post WW2 era, hundreds of Italian civilians were killed in accidents caused by US military operations in Italy, and our spineless leaders did nothing. In many cases they actively helped covering up the truth. Two of many examples:

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

https://en.wikipedia.org/wiki/1998_Cavalese_cable_car_crash
by tejohnso | 2025-11-23 01:18:36+00:00
The average person probably won't notice or care otherwise this would be a much more publicized issue. The average person also doesn't care that their refrigerator and television phone home, their calls and data are slurped up by the NSA, and their location can be tracked through their cell phone and vehicle movements.

However, just because the average person doesn't notice and doesn't care, it doesn't mean that their life can't be ruined at some point because of these things. You never know when you're suddenly going to be targeted for something you may or may not have done.
by IlikeKitties | 2025-11-23 01:20:52+00:00
The violation of rights already began with the investigation for what anyone in good faith would consider satire. Even being investigated for this means having to defend oneself, perhaps hire an attorney, in case of this defendant having to have a gofundme equivalent to pay for it. Would you like to go to court for every post you do online? I cannot fathom how you cannot see that this is obviously designed to intimidate students criticizing the Bundeswehr or being violated by a medical examination as a draft preperation.

Young people have to shut up and take it and if they don't, hope your pocketmoney covers attorneys fees!

Just read the context of what happened here, it's easy to find. They did shit like using their mass suriveillance tech to find the phone this OBVIOUS SATIRE was posted from[0]

[0]https://perspektive-online.net/2025/10/anzeige-wegen-meme-es...
by trueno | 2025-11-23 01:20:55+00:00
As the downcycle lingers on everyone’s doorsteps a lot of non profits that do incredible work are losing funding as the investors back out from commitments they confidently put forward when things were going well. It quickly shutters the non profits. It makes me sad tbh.

Can’t say this is the same thing that happens at Mozilla but you are very right in that a lot of nonprofits seem to be lead by those bring the same operational decision making experience and solutions that you see in publicly traded companies. There are plenty of non-profits that are indistinguishable from public companies in how the board is composed of an inner circle of wealthy unsavory people.
by wpasc | 2025-11-23 01:21:04+00:00
im surprised this is earning such downvotes. idk about the "opinionated" vm perspective but I think it needing its own engine oe not is at least something worth considering. firefox has been my go-to alt browser for years as my backup to chrome. it was what I would use to "test again in another browser" but as time has gone by, more and more stuff just doesn't work on firefox :(
by PunchyHamster | 2025-11-23 01:21:23+00:00
If they just use 3rd party APIs/models, and AI bubble pops, the amount of users of AI in FF will not change.

The upstream might earn less, and some upstreams might fail, but once they have code switching to competition or local isn't a big deal.

That being said

"This could've been a plugin" - actual AI vendors can absolutely just outcompete FF, nobody gonna change to FF to have slightly better AI integration - and if Google decides to do same they will eat Mozilla lunch yet again
by left-struck | 2025-11-23 01:21:50+00:00
I think about this sometimes as I do a lot of things attempt to protect my privacy and keep control of what I’m paying attention to (ie not doom scrolling / shorts, carefully controlling notifications). So I make a lot of sacrifices including my time in order to maintain control over my technology.

I think it’s not possible for me to say if my life is really better, because it’s the whole road not taken thing. It’s not possible to know and so it’s not worth agonising over, but I’m choosing to live according to my values at least, and that seems valuable.
by zahlman | 2025-11-23 01:22:24+00:00
For that matter,

> The full path specification in `go build` was redundant given the context of how Go modules are structured. Simplifying the instructions improves clarity and reduces confusion for new users or contributors.

The explanation doesn't seem quite right. The module mentioned in that command was moved to the project root, in such a way that the command no longer needs to specify a path. So the full path specification wasn't redundant; the updated version of it, became redundant.

And all of this was done in a single commit. Better (disclaimer, I have no experience using Go. Actual Go developers probably don't even need to be told this much):

Use github.com/arpxspace/smartcommit namespace `go.mod` is updated with an explicit package namespace, and import statements adjusted to match.

and then:

Rename main module `cmd/smartcommit.go` is moved to `main.go`, and the README adjusted to match. (Using this name allows omitting the main module path from the build command.)

and then:

Simplify prose in README.md

(No explanation required for the last one.)

There's no need to justify that your changes are "in accordance with best practices", tell a story about "ongoing efforts" (unless you actually have other recent commits that you want to group together like that conceptually), etc. Commit messages are for other developers. Another developer who reads, in effect, "this change was made in the hopes that YOU will have an easier time contributing to the project"... is going to feel patronized.

But making fine-grained commits with short messages will help in the long run. No amount of prose in commit messages can actually organize the commits. Meanwhile, the AI's summary completely ignored a change I would recommend splitting out into a separate (third) commit.
by Retric | 2025-11-23 01:24:33+00:00
It doesn’t matter if New Mexico’s state government recuperates its revenue it matters if New Mexico’s citizens are better off. As such federal, state, and local levels are worth considering not just state taxes, including changes in other outlays such as healthcare subsidies. Effective tax rates on marginal income often exceed 50% for American families even ignoring the income stream from daycare workers and facilities etc. US Government spending being 40.5% of GDP those kinds of marginal tax rates should be expected.

Now as a low population state implementing this at the state level means most of that federal savings/revenue helps people outside of the state, but that’s the issue with implementing such programs at the state level rather than an issue with the type of program itself.
by NooneAtAll3 | 2025-11-23 01:25:13+00:00
that was addressed

> Aux was excited about the project. He’d done his Master’s thesis on AI recreations of loved ones when that was just taking off. He was disappointed that the enthusiasm that followed their first-gen rollouts faded pretty quickly. His take was that one of the problems with their designs was that they’d actually been overfitted to physical reality, rather than people’s emotional one. “People don’t want to see their loved ones as they actually were; they want to see them as they prefer to remember them. There’s a surprisingly high delta between those two things,” he said.

> The illusion that these digital ghosts were workable replacements for their loved ones quickly evaporated. By the early 2030s, they’d been demoted to another type of deepfake, rather than a compelling memorial.
by jcranmer | 2025-11-23 01:26:43+00:00
AIUI, the AI-based translation models are based on the same transformer-oriented neural nets that LLMs are based on, just not quite writ as large. In other words, it's not entirely inaccurate to call these models LLMs.

While there's a lot of other AI technologies that aren't LLMs, automatic translation is probably the closest technology phylogenitically speaking.
by nativeit | 2025-11-23 01:27:07+00:00
As near as I can tell, it’s always been owned by Cliqz, who produced some privacy-focused browsers (named Dawn or Lumen) and a search engine (Tailcat) that was ultimately purchased by Brave. The whole thing is majority owned by a German media group, Hubert Burda Media, and while its missions towards increased privacy seem to be sincere, I don’t know if I’d trust them implicitly.

All that said, the main project looks to be open sourced under a GPL3 license, so distrust and verify: https://github.com/ghostery
by ivanmontillam | 2025-11-23 01:29:05+00:00
It's already problematic to have Chromium dominating/near-monopolizing, and add salt to the wound letting Gecko die this way.

Chromium is so prevalent as an engine, that most developers don't test their code on Firefox and just tell everyone to use Chrome/Chromium when they run into issues.

This has the unintentional side-effect of strong-arming the W3C into compliance with the engine and not the other way around. Why do we bother with the W3C then? if they are powerless and Chromium can do as they please?
by logankilpatrick | 2025-11-23 01:29:38+00:00
We made the bet 2 years ago to build AI Studio on top of the Google Cloud infra. One of the real challenges is that Google is extremely global, we support devs in hundreds of countries with dozens of different billing methods and the like. I wish the problem space was simple but on the first day I joined Google we kicked off the efforts to make sure we could bring billing into AI Studio, so January cannot come soon enough : )
by layer8 | 2025-11-23 01:29:42+00:00
This $1900 bug bounty is quite an outlier, you generally won’t find one per month. An additional challenge is that it’s hard to predict how much work something will take, or whether there are any showstoppers. Also, if you don’t live in the same country as the client, it will be more difficult to get legal assurance that you’ll receive your money (or for the client that they won’t lose their money).
by int_19h | 2025-11-23 01:29:51+00:00
It prevents you from mutating via the reference that you obtain from `satisfies` without casting its type, yes (or rather more precisely, you can mutate it, but only to the one allowed value).

However, the object can still be mutated via other references to it. TypeScript is full of holes like this in the type system - the problem is that they are trying to bolt types and immutability onto a hot mess that is JS data model while preserving backwards compatibility.
by ramraj07 | 2025-11-23 01:30:24+00:00
Vehement disagree. We implemented our own context editing features 4 months back. Claude released a very similar featureset we had all along last month. We were still glad we did it because (A) it took me half a day to do that work (B) our solution is still more powerful for our use case (C) our solution works on other models as well.

It all comes down to trying to predict what will be your vendors' roadmap (or if youre savvy, get a peek into it) and whether the feature you want to create is fundamental to your applications behavior (I doubt encryption is unless youre a storage company).
by jm4 | 2025-11-23 01:30:32+00:00
What language do you put that list in? Would you still want to show it to every visitor when you know most of them speak a particular language?

I use to do some work in this area. The first question is difficult and the second is no. We had the best results when we used various methods to detect the preferred language and then put up a language selector with a welcome message in that language. After they made a selection, it would stick on return visits.
by spankalee | 2025-11-23 01:31:01+00:00
We don't have to deal in hypotheticals - we have a concrete example here. There's a method, array.flat() that does a thing that we can correctly describe in TypeScript's type system.

You say you would reject those correct types, but for what alternative?

It's hugely beneficial to library users to automatically get correctly type return values from functions without having to do error-prone casts. I would always take on the burden of correct types on the library side to improve the dev experience and reduce the risk of bugs on the library-consumption side.
by gpm | 2025-11-23 01:31:21+00:00
The baseload talking point has never made sense but storage doesn't make it make less sense. Baseload here is definitionally power sources that can't economically follow the demand curve. They carry the exact same problem that intermittent power sources like solar do, in that you need dispatchable power sources to augment them so that they can actually meet demand, the only difference is that the cause of this is that generation stays constant while load varies instead of both generation and load varying.

Baseload is not, and has never been, a feature. It's just a drawback that can be handled so long as only some of your power comes from such sources.

Batteries augment base load power sources the exact same way they augment intermittent ones, they take power from them when there is excess and give power back when there isn't making them effectively dispatachable power.
by zahlman | 2025-11-23 01:32:11+00:00
I'm with Ish on this one.

> The first few characters of a commit message tell you immediately the type of change you should expect.

1. Why do I care about this particular classification of "type" of change?

2. "The first few characters" of the message aren't actually what I necessarily see first, anyway.

> If you're looking for a bug fix, for example, you can safely ignore any other type of commit.

1. If I'm looking for a bug fix, I'm using tools like git blame and git bisect.

2. How often do bugs actually get fixed by a single commit, that has that bug fix as their sole purpose, and which is recognized as a bug fix at the time of writing? I'm guessing it's much lower than one would naively expect.

3. If I'm looking for a bug fix, I'm looking for the fix for a specific bug, which is probably most recognizable by some bug tracker issue ID. (And if not, it's most searchable that by figuring out an ID and looking that up). So I'm scanning lines for a # symbol and a number, which I would definitely not expect to be at the start of the line.

> Thinking about the type of change you're committing helps you create atomic commits. Anything that is not strictly related should go in a separate commit. Hopefully you already know why you should care about this.

Yes. And I do this by thinking about a verb that naturally belongs at the beginning of the sentence (fragment) describing the commit. "Bugfix", "feature", and "enhancement" aren't actions.

The discipline of organizing commits is orthogonal to the discipline of labeling them.

> A conventional commit message also often includes the change scope.

One that is thoughtfully written by hand will naturally include the scope of the change any time that this concept is meaningful.
by wpm | 2025-11-23 01:33:11+00:00
I’m not sure my drinking glasses are a place I really need “modern” and “new” and “whatever the opposite of functional” is. It’s a glass for drinking liquid out of. There is no innovation. There is no novel design yet to be found. It’s an almost ancient device. It should be functional above all else. They are for drinking water out of, not fucking decor.

And for what it’s worth, if you don’t like the Picardie glasses, they have like a dozen other shapes that might feel “modern” enough.
by JumpCrisscross | 2025-11-23 01:33:47+00:00
> Uranium is far, far energy denser than any fossil fuel, and thus much easier to stockpile

Sure. That doesn't remove stockpiles' inherent disadvantages: finiteness and vulnerability. Relying on uranium stockpiles would immediately put China at a known limit in a war of attrition that wouldn't constrain their adversaries.
by lambdaphagy | 2025-11-23 01:34:44+00:00
Yeah, that's precisely what I'm objecting to-- smuggling in assumptions about the relationship between Sami and other Northern-European populations by using a term that implies that Scandinavians aren't native to Scandinavia, at least as much as any human population is native to anywhere.

In particular it obscures what is fundamental to the conflict, which is state/settled vs non-state/tribal, not one group being native to the land and the other being some sort of outside occupying force.
by ameliaquining | 2025-11-23 01:35:58+00:00
First one flattens a potentially-nested tuple type. E.g., FlatArr<[number, [boolean, string]]> is [number, boolean, string].

Second one gets the element type of a potentially-nested array type. E.g., Flatten<number[][]> is number.

For what it's worth, I've never needed to use either of these, though I've occasionally had other uses for slightly fancy TypeScript type magic.
by crabmusket | 2025-11-23 01:38:46+00:00
Best of luck! A couple of clarifications as I was writing from the train and didn't do a second draft:

By "backwards" I meant to suggest, have the LLM critique a commit message you wrote. Have it point out vague language, weasel words, generalisation and marketing terms.

The wiki article is good advice for writing in general, not limited to LLMs.
by JumpCrisscross | 2025-11-23 01:39:54+00:00
> cost of the fuel has almost nothing to do with the economics of nuclear power

Who said this?

> considering a liquid fueled reactor makes heat in the 900C range and a AP1400 makes heat in the 300C range, they aren't really substitutes for each other

Nobody said this either.

There are more reactor designs in the world than LFTR, PWR and BWR, particularly if we're talking at the demonstration scale like this reactor.
by granzymes | 2025-11-23 01:40:09+00:00
For one, the simple answer is incomplete. It gives the fully unwrapped type of the array but you still need something like

type FlatArray<T extends unknown[]> = Flatten<T[number]>[]

The main difference is that the first, rest logic in the complex version lets you maintain information TypeScript has about the length/positional types of the array. After flattening a 3-tuple of a number, boolean, and string array TypeScript can remember that the first index is a number, the second index is a boolean, and the remaining indices are strings. The second version of the type will give each index the type number | boolean | string.
by dalyons | 2025-11-23 01:40:53+00:00
Yes yes, one of the usual reflexive context free points repeated every time solar comes up. Whatever the actual capacity factor is(5% is not a serious number ), I’m sure chinas energy planners know that, it’s hardly a gotcha. And still they’ve choose to build solar at a volume massively dwarfing nuclear

(Edit: cycomanic explained it much better and more patiently than me)
by charcircuit | 2025-11-23 01:41:53+00:00
It's not based on cryptocurrency, there are just extra features that use it. Unstoppable domains is an optional feature. You don't need to visit them, but it gives value to people by letting them actually own their domain instead of leasing it from ICANN. Viewing ads to earn BAT is an optional feature. As I mentioned ad blocking is built in so you can have it show no ads if you want.
by zahlman | 2025-11-23 01:42:13+00:00
> Probably most commits should be along the lines of "getting a thing working", not essays about the intricacies of character encoding:

I'm not a fan of that commit as a commit, although it would make a great start for a blog post. The explanation of how the issue was tracked down, is not helpful in understanding what the issue is. On the other hand, while the author describes finding (and replacing) a non-ASCII character masquerading as a space, it would have been more interesting to know what character it was.

I agree that explaining the "why" is useful, but in this case I don't think it deserves much more detail than "ensure the file uses only ASCII characters to avoid a text encoding error while running tests in this specific manner". (I guess I can also see the argument for showing the error message for later searches, too....)
by saghm | 2025-11-23 01:42:13+00:00
The "average" player in one of those sports leagues isn't really a celebrity at the level the article is talking about. Charli XCX's last album was nominated for 11 Grammies and won six of them, and it has the 15th highest aggregate rating from Metacritic of all time. If you're comparing to athletes, this is All-Star roster, potential MVP winning-level performance for at least that season. By no means it's every player who hits 50 home runs in a season is going to be set for life financially, but the chances they're going to struggle are a lot lower than some some random utility infielder or middle reliever.
by cycomanic | 2025-11-23 01:43:45+00:00
That doesn't significantly change the argument. Most solar plants have capacity factors of around 20% (5% might apply to home systems, but not commerical), compared to nuclear which has around 80%. So a factor of 4. So numbers change a bit on the previous poster, China just installed 3x more solar in 1 year than all the nuclear under construction, or they essentially installed the same amout of solar in one year as all existing and under construction nuclear combined. And if we look at projections, next year they likely will install twice as much solar...

While China is often put up as the poster child for nuclear power, they are actually a great example of how nuclear is being overtaken by renewables. China's 2019 plan was that by 2035 nuclear would account for ~8% of generated electricity (up from ~5%). Since then percentage dropped to 4.5% (and the drop seems to be accelerating). Unless something dramatically changes nuclear will account for less than 4% (not the planned 8%) of generated electricity by 2035. All that is due to the raise of renewables (largely solar). I suspect we will not see China build close to those projected 200 GW and the percentage to be even lower, just due to the exponential growth in solar.

source: https://en.wikipedia.org/wiki/Nuclear_power_in_China
by sedatk | 2025-11-23 01:44:08+00:00
I basically have two problems with Firefox that prevent me from using it my main browser. One is this 7 year old kerning bug:

https://bugzilla.mozilla.org/show_bug.cgi?id=1445596

The other one is Firefox Sync not storing shortcut bar favicons. Every install, I have to click on every web site one by one to bring back their favicons. It's a 17 year old ticket:

https://bugzilla.mozilla.org/show_bug.cgi?id=428378

Firefox adding crazy features that it may or may not cancel in a few years while ignoring these minor issues frustrates me, and keeps me away from it.
by greggyb | 2025-11-23 01:44:23+00:00
One avenue, couched in specifics of US law, but I presume the ideas have analogs in Germany's legal system:

A battery occurs when a harmful physical contact occurs. Contact with a weapon is pretty much by definition battery.

The use of such a drug in the commission of rape or other violent crimes would then be a very easily proven case. If the substance is present in a victim's body, then battery has occured, basically by definition.

Given that rape and other violent crimes that are committed with the use of such drugs may not leave other physical signs on the body of the victim, then this may be the only physical evidence.

The examination for presence of such a drug in the bloodstream is also much less intrusive than for a typical rape kit exam.

There's nothing binary or black and white in such investigations, so this is an additional avenue to provide evidence to support the prosecution of these violent criminals.