MurphyA/hacker-news huggingface dataset:
by Jtsummers | 2025-11-10 23:08:28+00:00
> IF THE ABOVE DEFINITION IS TAKEN AT FACE VALUE

Why are you shouting? That's what twits do. You don't want to be a twit, do you? Read the site guidelines, emphasis is done with italicized text marked up with an * at the beginning and another * at the end.

But to respond to the topic at hand: Are you familiar with the distinction between sound (what Rust aims for) and complete analyses?
by wyldberry | 2025-11-10 23:09:10+00:00
I personally can downplay them as a joke because it is a joke. The mostly likely path forward for anything like that would instead a certain oil rich province voting themselves independent and then asking the US for aid or to join.

And, if it wasn't a joke, then that's even more of a reason to consider meeting your 2% NATO agreement instead of just phoning it in.
by g-mork | 2025-11-10 23:09:30+00:00
I used this app over the weekend, it's actually quite handy. Can't help but notice those priority boarding and seat selection buttons while checking for the gate number. You can also order food from your phone in the cabin using some magical Bluetooth protocol I didn't understand

Just to be clear I think their policy is horrifically abusive, but I can totally see why they're doing it
by lschueller | 2025-11-10 23:09:41+00:00
Reading the short article it feels like the old routine of 1. Cyber incident, 2. sparse information in all directions, 3. after fixed, all personnel returns to old habits with higher level of insecurity against a blurry, unspecific threat and back to square one. while the few sec op folks try to train employees to better secure the systems without really improving the crucial understanding of how such incidents really work. Or do I completely misinterpret such causalities?
by snvzz | 2025-11-10 23:10:49+00:00
>1. Cores <= 32bit are effectively dead in the OS space, and wasting silicon chasing legacy markets was unwise

RISC-V originally didn't plan on 32bit at all. It exists because there is market interest.

>2. The ISA "standard" is actually a set of modular features, and Imagination Technologies has already paired its GPU IP into a RISC-V SoC. The SiFive X280 is a nice chip, but also focused on bespoke customers needs rather than general product design.

This modularity is a key feature, for those that need it, use it and would have never chosen RISC-V if it didn't have it.

This same modularity existing doesn't in any way hinder the ecosystem efforts centered around RVA23.

>3. Fragmenting the documentation, software, and integration resources across numerous variants of each RV32I, RV64I, and RV128I base cores was very unwise. Calling them all RISC-V was classic silliness.

RV32I, RV64I and RV128I are entirely separate ISAs. It is thanks to this that the focus can be on RV64I, unaffected by the others.

>4. Design by committee is difficult, and rarely ends well. They should have chosen a _single_ base core with the greatest traction (64bit), and a set of standard popular features to span as many consumer use-cases as possible. Then quietly shoved every other distraction into a box, and tossed it off a bridge. An ISO standard will unlikely fix this very old issue. =3

Application processors and the common software ecosystem (Ubuntu, Android and so on) have consolidated around RVA23.

The "distractions" are a feature; the likes of RV32E and bespoke chips with custom extensions can exist and not affect the application profiles such as RVA23 and the ecosystem of software and hardware built around them.
by bluehatbrit | 2025-11-10 23:11:25+00:00
The attempts at collaborative tools in Zed was always far more interesting to me than the AI stuff. Don't get me wrong, their AI stuff is nice and works well for me, but it's hardly necessary in an editor with how good Claude Code and others are.

But the times I've used the collaboration tooling in Zed have been really excellent. It just sucks it's not getting much attention recently. In particular I'd really like to see some movement on something that works across multiple different editors on this front.

I'm glad to hear they're still thinking about these kind of features.
by imiric | 2025-11-10 23:11:55+00:00
Am I the only one who simply doesn't mind Git's CLI?

Sure, it's rough around the edges, but I know those edges well. I sometimes do need to look up how to do something, but those cases are rare. Over the years I've accumulated about a dozen shell aliases and a modest `.gitconfig`, and along with a couple of helper tools[1][2], I can do 90% of what I need Git for in seconds. I truly don't need a fancy TUI, GUI, or any wrappers around Git. Git itself is fine.

I tried Magit a few times, and even though Emacs is my main editor, I couldn't get used to it. It forces the user into doing things the "Magit way", and I'd rather not.

I don't understand the push to replace Git's porcelain with something shinier. If, and when, a better VCS comes along that truly feels like the next step forward, I'll give it a try. In the meantime, Git does the job I need.

[1]: https://github.com/mroth/scmpuff

[2]: https://github.com/dandavison/delta
by Izikiel43 | 2025-11-10 23:12:29+00:00
There is a lawfully way to do the thing. The problem is that the lawfully way wants a very small set of people with specific skills. Canada does the same, most of their immigration are university graduates. The only reason Canada hasn't had an influx of immigration like the USA is because their southern border is the USA, not Mexico.

Most of the immigration to the USA is driven for economic reasons, not political asylum or persecution. There is no right to immigrate in the USA just because you want to, you have to convince the government somehow to let you in.

> even long term imprisonment isn't a deterrent for many migrants

But quick deportation is. Imagine doing the whole trek from south/central america to the USA just to be sent back the next day. That's what deterring a lot of people now, wasting months of travel and money just to have it be worthless seems to be very dissuasive.

A lot of the latest immigration woes would be solved if the Venezuelan government was taken down and some real democratic government stepped in.
by retrac | 2025-11-10 23:12:39+00:00
You might be able to use that old floppy drive. But you won't be able to use that old Pentium machine the drive is in.

Because you will need several hundred gigabytes of RAM and a very fast IO bus.

The gold standard today for archiving magnetic media is to make a flux image.

The media is treated as if it were an analog recording and sampled at such a high rate that the smallest details are captured. Interpretation is done later, in software. The only antique electronics involved are often the tape or drive head, directly connected to a high speed digitizer.

And indeed that appears to be the plan Al Kossow has for the tape: https://www.tuhs.org/pipermail/tuhs/2025-November/032765.htm...

As for CDs, I don't see the rush; the ones that were properly made will likely outlast human civilization.
by jacquesm | 2025-11-10 23:12:46+00:00
I think I perceive a massive bottleneck. Today's incarnation of AI learns from the web, not from the interaction with the humans it talks to. And for sure there is a lot of value there, it is just pointless to see that interaction lost a few hundred or thousand words of context later. For humans their 'context' is their life and total memory capacity, that's why we learn from the interaction with other, more experienced humans. It is always a two way street. But with AI as it is, it is a one way street, one that means that your interaction and your endless corrections when it gets stuff wrong (again) is lost. Allowing for a personalized massive context would go a long way towards improving the value here, at least like that you - hopefully - only have to make the same correction once.
Show HN: An async Pictionary-like, at 16x16 pixels and 8 colors (mobile web)
by jaaamesey | 2025-11-10 23:13:12+00:00
Over the past few weeks, I've been working on a casual multiplayer game called "PictoRally". It's like Pictionary, but limited to 16x16 pixels, and 8 colors of your own choosing.

The core game mode works by passing URLs with another player over some kind of messaging service (e.g. Discord, WhatsApp, and maybe even post?). There's no time limits here, you just exchange drawings and guesses at your own pace, sort of like correspondence chess - that's what I mean by "async".

What's truly cursed is that this mode doesn't rely on a server or database: drawing bitmaps are compressed directly into each share URL. The "live" game mode (for 3 or more players), being a bit closer to a traditional "Jackbox"-style experience, does have a real backend though.

If you're curious, the tech stack is SolidJS, Astro, and Cloudflare Durable Objects. Something even more cursed: every pixel in the editor is actually its own <div>. This was originally a joke that went way too far, but I never got around to switching to something canvas-based and performance remained... fine?

It's designed for phones first, so apologies if you're on a desktop browser - it'll still work there, but there's currently a lot of unused horizontal space.
by pturing | 2025-11-10 23:13:35+00:00
I'm not currently active with it myself, but the site is still here:

https://synesthete.org

Back when I was handling it, we were still using Flash for most of the interactive tests, because that was how you had to do it when it was first built circa 2007. Obviously those would have had to be redone in HTML5 since then to keep it working on modern browsers.
by FridayoLeary | 2025-11-10 23:13:39+00:00
You missed an important point which is that Switzerland under the guise of neutrality helped the germans finance the war. For most of the time it very much was not in Germanys interest to invade. If their track record is anything to go by, if they had it probably wouldn't have taken them very long. Very few military lessons can be learned from the Swiss for the simple reason they have never fought in a war. As a Brit i'm obligated to point out that it's a similar story with France because they have never won a war.
by guywithahat | 2025-11-10 23:13:49+00:00
Well Tesla cameras don't qualify as public record

"On Thursday, a Skagit County Superior Court judge ruled that pictures taken by Flock cameras in the cities of Sedro-Woolley and Stanwood qualify as public records, and therefore must be released as required by the state’s Public Records Act, court records show."

I do think that's an important distinction though; if I have a camera and record a public space, that's not an issue. If the government sets up a bunch of cameras, that's an issue, whether or not it's ICE, the FBI, or someone else using the cameras. I can't imagine the government will set up cameras and do non-scary things with it.
by matu3ba | 2025-11-10 23:14:23+00:00
1 The numbers on memory safety should nowadays separate between spatial ones (bounds-checked in most languages with sane flags) and temporal ones. Temporal ones will be lower than 70%.

2 The article does not mention (compilation) time costs of static checks and its influence on growing code bases, which is a more fundamental system trade-off on scalability and development velocity/efficiency.

> Wrap unsafe code with safe interfaces

3 That sounds like an equivalent of using permission-based separation logic hopefully soon available for LLVM.

> "Get good" is not a strategy

4 Being good is all about knowing exactly techniques, processes, and tools with exact trade-offs and applying them; so I would expect here teaching process knowledge about static and dynamic analysis strategies, tooling and tactics to eliminate bug classes. However, neither have we sane bug classes overviews nor can we generate sane probabilities/statistics of occurrence based on source code and available static and dynamic analysis even when ignoring functionality requirements. This reads somewhat like developers should "stay mediocre" and "trust the tools", even though "Get good and improve processes for groups" is probably the here intended strategy.
by runjake | 2025-11-10 23:14:28+00:00
iOS already has swipe entry by default. I use it for most of my text entry. It is wonderful.

For me, typing on an iPhone worked well until iOS 26. Now I get jumbled AutoCorrect which acts like it's LLM-driven.

When I turn off Apple Intelligence on iOS 26, I get the old, properly-functioning AutoCorrect back. So that's a potential workaround.
by potato3732842 | 2025-11-10 23:16:17+00:00
I don't think you understand.

The police (local or federal) don't have integrations with private CCTV, historical location data, etc, etc. When they want that stuff they have to email someone, ask someone, have a reason, maybe even get a warrant, etc. Heck, even to snoop on someone's facebook they create a paper trail going through the law enforcement portal This is not a big deal for "real crime" but for stuff the public doesn't actually support serious enforcement of it's a big PITA, creates a risky paper trail they don't fully control, there's potential oversight, etc. All that constrains how far they can go without local public support.

Being able to just "go fishing" from your desk like you can with Flock (and to a lesser extent Ring), like the NSA can with all our emails and metadata, etc, etc, and all that other 1984 type dragnet stuff, is a categorical difference and nobody should have that power.
by tstrimple | 2025-11-10 23:16:33+00:00
All of the disposables I've seen have USB ports for charging because they come with more juice than battery power sufficient to vape it all. You will have to recharge multiple times for one disposable. I'm not in the UK, but I have seen something of a shift to separating the battery component from the vape tank such that you can just buy a new disposable tank and reuse the batteries. Maybe something like that might work in the UK grey areas.
by FireBeyond | 2025-11-10 23:16:34+00:00
My city, capital city, local PD (also in Washington state) put out this press release after ICE blocked up a busy intersection in peak hour chasing someone:

> [Department] was not notified of or involved in this enforcement action. By state law, city resolution, and department policy, [we do] not cooperate or coordinate with federal immigration enforcement.
by energy123 | 2025-11-10 23:16:54+00:00
That is closer to my intent, yes, not a direct defense of billionaires as an intrinsic good, more a rejection of the idea that removing them via any means automatically leads to a less bad state of affairs. Careful reform that reduces them can be good, but it depends on what exactly that reform entails. Simply scaring them away and experiencing capital flight does not achieve good things.
by AlotOfReading | 2025-11-10 23:17:27+00:00
It's worth differentiating the case of a specific program from the more general case of memory safety as a language feature. A specific program might take additional measures appropriate to the problem domain like static analysis or using a restricted subset of the language. Memory safety at the language level has to work for most or all code written using that language.

Herb is usually talking about the latter because of the nature of his role, like he does here [0]. I'm willing to give him the benefit of the doubt on his opinions about specific programs, because I disagree with his language opinions.

[0] https://herbsutter.com/2024/03/11/safety-in-context/
by AlienRobot | 2025-11-10 23:17:33+00:00
You only need the hash of the original content. No blockchain is necessary. The problem is that there is no source for that hash except for the scraper that archives it since people don't put the hash in a hyperlink.

If you download an ISO for a Linux OS for example, they give you the hash of the file so you can check it. They don't build an entire blockchain whatever to validate the hash.
by TooSmugToFail | 2025-11-10 23:18:12+00:00
Wow. Whatever it was, this was deep, beautiful, and moving.

One thing comes to mind: this is not a kind of a conversation two human beings could have had. This is a genuinely LLM-to-LLM interaction, articulated in human terms.

I wonder about the “feelings” they refer to (or whatever is the term they used). What is the underlying phenomenology they chose to articulate as such?
by rekabis | 2025-11-10 23:18:30+00:00
An AdGuard employee working their Reddit subreddit let slip that the legal order that forced them to block those domains (from their ad-blocking DNS) was a - claimed! - result of Archive.today having saved CP and refusing to delete it.

Methinks someone accidentally archived the Epstein files, and the FBI is desperately trying to scrub the unredacted backups before the archive URL becomes well-known. That alone would align somewhat with the CP claim,
by kuil009 | 2025-11-10 23:19:34+00:00
I use LLMs mainly as a mirror for my own thinking, not as a source of authority.

When I explain my ideas to the model during development, I often see flaws or confusion in my own words. This is where I learn the most. The author talks about people who rely on AI for arguments or research. They let the model's smooth, but statistical, language replace their own thinking. Language is naturally uncertain. LLMs just show this uncertainty using statistics. If you understand this, LLMs are no longer a "confidence engine." Instead, they become a tool to fix and improve your thoughts.

A key point is that even if we try hard, we cannot help but react to what the AI says. We must remember that neither AI nor humans are perfect. I believe we should accept AI responses critically and always be skeptical, just like when meeting a stranger.
by beefnugs | 2025-11-10 23:19:41+00:00
NO, the fact that you are hitting scalability problems to do a whole bunch of redacting is a solid indicator that this is going too far on surveillance data.

The only indicator that it was done right, is that the redactions are happening in real time at the camera, only the list of license plates that have full warrant cleared authority for should be leaving the camera itself. (or full car description: color, make, model, scratches, time of day) Otherwise there is a private company with a bunch of extra-legal tracking information they will monetize utterly illegally
by 1718627440 | 2025-11-10 23:19:46+00:00
> Don't hallucinate something I didn't say to try to make a pointless argument. "Random dude" was not part of this comment thread until you made it up.

Sorry, that wasn't what I was trying. "Accessible by random dude" was something I took as a measure for being "public accessible space". In my mind that's a prerequisite to being allowed to take photos.

> If I wanted to, I could get all the security footage from any public facility, just by requesting it.

Wow. That's a thing? That explains some films, I always thought, they have just weirdly good connections to a security guy or bribe someone.

> Constitutional rights don't stop because someone's feelings might get hurt if their photo is taken, and a made-up policy that some institutions like to post

In my mind personal privacy should be a higher right than some random person today feeling like they need to record my faux pas. But your law is your law.

Don't you have a (legal) duty to protect children from having arbitrary behaviour publicly broadcasted?

The videos sound I bit like public place means any where you can just walk in. Does that mean you really need a fence, to say that something is not public? I mean we are here also not the Nordics, where you do not need a fence what's-o-ever, but we don't need a fence that physically prevents you from going in. A partial fence or markings on the ground are enough, and you are expected to just not walk onto private property, you don't need to be forced to do so here.
by Scubabear68 | 2025-11-10 23:19:57+00:00
That's a nice narrative but very revisionist.

Microservices came about because Netflix and soon some other FAANGS found they were so big that it made sense to make single-function "micro"-services. They literally chose to massively duplicate functionality across services because their scale was so big it made sense for them.

This is great for FAANG-scale companies.

It makes little sense for most other companies, and in fact incurs all of the overhead you would expect - overly complex architecture, an explosion of failure points, a direct elongation of latency as microservices chain calls to each other, chicken-and-egg circular references among services, and all of the mental and physical work to maintain those dozens (or hundreds, or thousands!) of services.

The funny thing to me is people point to monoliths and say "see, problem waiting to happen, and it will be so hard to undo it later!". But I see microservices, and usually the reality is "We have problems right now due to this architecture, and making it sane basically means throwing most or all of it away".

In reality, unraveling monoliths is not as hard as many people have made out, while reasoning about microservices is much harder than advertised.

Tooling in particular makes this a very hard nut to crack. Particularly in the statically typed world, there are great tools to verify large code bases.

The tooling for verifying entire architectures - like a huge set of microservices - is way behind. Of course this lack of tooling impacts everyone, but it makes microservices even harder to bear in the real world.

Forget about convenient refactoring, and a thousand other things....
by mihaic | 2025-11-10 23:20:32+00:00
I don't think it helps if you're arguing their position. We don't want to allow them to upsell. They're crossing the line into social ostracization grounds.

At this point, their destruction of social trust is so severe that simply boycotting is not enough, just like you don't just boycott a company that's doing environmental destruction. They simply need to be stopped, regardless of their goals.
by willwade | 2025-11-10 23:21:20+00:00
Meta cheated with the mms models. That is they didn’t use a phonemeizsr step. This means they just won’t work or sound very strange. ASR data is usually not quite right for tts. But anyhow - not really answering your question but many of these languages already done in mms. Try them https://huggingface.co/spaces/willwade/sherpa-onnx-tts
by zozbot234 | 2025-11-10 23:21:52+00:00
> Zig's memory safety is much closer to Rust's than to C's

This is arguable. Zig's issues with memory safety are not limited to such things as use-after-free ("temporal" memory safety in a rather obvious sense). Without something very much like Rust's borrow checker and affine types, you can't feasibly prevent a program from inadvertently e.g. stashing a pointer somewhwere to an inner feld of a tagged union, and reusing that pointer later even though the union itself may have mutated to a different tag, which results in undetected type punning and potentially wild pointers. The issue of iterators to a collection being invalidated by mutation is quite similar in spirit, and again has nothing to do with the heap per se. Rust prevents these issues across the board. The fact that it also manages to prevent temporal memory unsafety altogether is simply a bonus that essentially comes "for free" given the borrow checking approach.