MurphyA/hacker-news huggingface dataset:
by AnthonyMouse | 2025-11-25 04:22:15+00:00
> Cutting funding for agencies and organizations that were investigating companies run by Elon Musk.

Which doesn't make any sense because you don't need to cut their funding when it's your buddies in office. They just don't investigate you anymore regardless of their funding level.

> Cutting funding for organizations, like NOAA, that have high economic returns for every dollar the government spent on them.

It's obvious why fossil fuel companies (and therefore Trump) would want to do this, but Musk is the guy who does electric cars and grid storage batteries. His financial incentive would be to play up the dangers of climate change.

And this is the same as the first one. If your guy is in office then you don't need to cut the funding of some agency under your own control, you just have them stop doing whatever it is you don't want them to do anymore.

> Copying information from multiple government databases.

The only reason DOGE could copy them to begin with is that they were already in control of the government and therefore already had access to the databases. If you want to complain about something, how about why does the government keep all of this sensitive information instead of encouraging systems that use decentralized identity or don't imply or require mass surveillance in order to operate? Every administration has access to that when they get elected, including the ones you don't like, so let's not have it to begin with.

> (2) leaves openings for someone with enough capital to fill in the gaps left behind and make a profit charging for what used to be a government service.

If this was actually a profitable market then there would be no reason for it to be a government service to begin with. But it isn't, because collecting the data is expensive and there aren't a lot of buyers. If anything getting rid of NOAA would cost SpaceX money because NOAA pays SpaceX to launch satellites, and nobody else is going to do it.

Republicans want to cut NOAA because they publish climate data and the fossil fuel industry is a Republican constituency. But you don't need DOGE for that when the Republicans control Congress.

They were completely feckless at finding the right things to cut but this stuff is conspiracy theories.
by ComputerGuru | 2025-11-25 04:22:19+00:00
Two suggestions:

UX on mobile isn’t great. It wasn’t obvious to me where the second model output was and I was thrown off even more so because the option to vote for model 1 output was presented without ever even seeing model two output.

Second suggestion would be to install a MathJax plugin so one can properly rate mathematical equations and formulas. Raw LATeX is easy to mistake and it makes comparing between LATeX and Unicode outputs hard.
by btbuildem | 2025-11-25 04:25:29+00:00
MCP came in a bit too early, when the conceptual shift of hadn't fully kicked in yet. I see it as a bit of a Horseless Carriage, and I think Skills came in to counter that. My sense is that this will settle into a sort of self-assembling code golem, where ambiguous parts are handled in LLM-space, and clear, well-defined things are handled in code-space.
by jarjoura | 2025-11-25 04:25:49+00:00
It's kind of annoying, right now at least, when an agent can see all the LSP noise and it decides to go off on a tangent to address the LSP noise in the middle of running a task that the LSP is responding to.

For this to work, the LLM has to be trained on the LSP and the LSP has to know when to wait reporing changes and when to resume.
by zzo38computer | 2025-11-25 04:27:02+00:00
I think it would be better to not use Unicode (so that you can use any character set), and to use "0o" instead of "0" prefix for octal numbers. Also, EDN seems to lack a proper format for binary data.

I think ASN.1 (and ASN.1X which is I added a few additional types such as key/value list and TRON string) is better. (I also made up a text-based ASN.1 format called TER which is intended to be converted to the binary DER format. It is also intended that extensions and subsets of TER can be made for specific applications if needed.) (I also wrote a DER decoder/encoder library in C, and programs that use that library, to convert TER to DER and to convert JSON to DER.)

ASN.1 (and ASN.1X) has many similar types than EDN, and a comparison can be made:

- Null (called "nil" in EDN) and booleans are available in ASN.1.

- Strings in ASN.1 are fortunately not limited to Unicode; you can also use ISO 2022, as well as octet strings and bit strings. However, there is no "single character" type.

- ASN.1 does have a Enumerated type, although the enumeration is made as numbers rather than as names. The EDN "keywords" type seems to be intended for enumerations.

- The integer and floating point types in ASN.1 are already arbitrary precision. If a reader requires a limited precision (e.g. 64-bits), it is easy to detect if it is out of range and result in an error condition.

- ASN.1 does not have a separate "list" and "vector" type, but does have a "set" type and a "sequence" type. A key/value list ("map") type is a nonstandard type in ASN.1X, but standard ASN.1 does not have a key/value list type.

- ASN.1 does have tagging, although its working is difference from EDN. ASN.1 does already have a date/time type though, so this extension is not needed. Extensions are possible by application types and private types, as well as by other methods such as External, Embedded PDV, and the nonstandard

- The rational number type (in edn.c but the main EDN specification does not seems to mention it), is not a standard type in ASN.1 but ASN.1X does have such a type.

(Some people complain that ASN.1 is complicated; this is not wrong, but you will only need to implement the parts that you will use (which is simpler when using DER rather than BER; I think BER is not very good and DER is much better), which ends up making it simpler while also capable of doing the things that would be desirable.)

(But, EDN does solve some of the problems with JSON, such as comments and a proper integer type.)
by nirui | 2025-11-25 04:27:06+00:00
The simplest trick is just don't use SSD for long term backup, use a normal magnetic hard drive instead, those thing way lasts _longer_ (but not forever, even in human timescale).

I have a HDD that was 17+ years since it last powered on. I dug it out recently to re-establish some memories, and discovered that it still reads. But of course you need to take care of them well, put them in an Anti-Static Bag or something similar, and make sure the storage environment is dry.

It's not prefect, but at least you don't have to struggle that much maintaining SSDs.
by joegibbs | 2025-11-25 04:29:43+00:00
It's a giant pile of stuff that isn't at all cohesive and they keep building on it, and building on that, and building on that again. Everything uses entirely different technologies. You go through the menus and it's like doing an archeological dig. It's slow, things take forever to load, constant driver issues and freezes. I had my mouse start chugging for no reason at 20% CPU load with one update and it stopped after another update. The updates get randomly applied, so make sure to save your work, don't count on putting it on sleep overnight and coming back with your work tomorrow. Speaking of, when it updates it can't do it in the background, so since it's in my bedroom I put it on sleep and then get woken up at 3am with a bright blue screen staring at me!
by johncolanduoni | 2025-11-25 04:31:12+00:00
> What would we have done differently knowing what we now know?

With the MLKEM standard? Probably nothing, Bernstein would have done less rambling in these blog posts if he was aware of something specifically wrong with one of the implementations. My key point here was that establishing an implementation phase during standardization is not an incoherent or categorically unjustifiable idea, whether it makes sense for massive cryptographic development efforts or not. I will note that something not getting caught by a potential process change is a datapoint that it’s not needed, but isn’t dispositive.

I do think there is some baby in the Bernstein bathwater that is this blog post series though. His strongest specific point in these posts was that the TLS working group adding a cipher suite with a MLKEM-only key exchange this early is an own goal (but that’s of course not the fault of the MLKEM standard itself). That’s an obvious footgun, and I’ll miss the days when you could enable all the standard TLS 1.3 cipher suites and not stress about it. The arguments to keep it in are legitimately not good, but in the area director’s defense we’re all guilty of motivated reasoning when you’re talking to someone who will inevitably accuse you of colluding with the NSA to bring about 1984.
by Rusky | 2025-11-25 04:32:18+00:00
There are also currently the unstable rustc_layout_scalar_valid_range_start and rustc_layout_scalar_valid_range_end attributes (which are used in the definition of NonNull, etc.) which could be used for some bit patterns.

Also aspirations to use pattern types for this sort of thing: https://github.com/rust-lang/rust/issues/135996
by potwinkle | 2025-11-25 04:32:37+00:00
Security seems like a solved problem on desktop already? Secure Boot + LUKS + SELinux gives anyone a pretty airtight userspace.

Microsoft/Apple have similarly secure set ups for their operating systems. Bitlocker by default (although there is a convenient backdoor for high-paying customers to protect against data loss and for law enforcement forensics) and Apple's Secure Enclave (only broken into by a certain five countries intelligence agencies and for older versions streaming pirates) should protect the average user pretty well.

Is there anything special about Android phones (especially budget ones) that makes them more secure? That's not what I've seen.
by questioner8216 | 2025-11-25 04:33:37+00:00
That sounds really interesting, whether it is done in Rust, some Rust 2.0, or a successor or experimental language. I do not know whether it is possible, though. If one does not unwind, what should actually happen instead? How would for instance partial computations, and resources on the stack, be handled? Some partial or constrained unwinding? I have not given it a lot of thought, though. How do languages without exceptions handle it? How does C handle it? Error codes all the way? Maybe something with arenas or regions?

I do not have a good grasp on panics in Rust, but panics in Rust being able to either unwind or abort dependent on configuration, seems complex, and that design happened for historical reasons, from what I have read elsewhere.
by JumpCrisscross | 2025-11-25 04:34:09+00:00
> We know that the brain is a structure that works through electrochemical reactions. Synapses transmit signals sent by axons to neurons. We can test this. We can measure it. There's nothing else going on that we can describe using known science

But what we can describe using known science doesn't describe the system. That doesn't mean the vacuum is voodoo. It's just a strong hint something more is going on. (Like the photoelectric effect.)

We know more about dark energy and matter than the dark essence that separates our leading electrochemical models from consciousness.
by manquer | 2025-11-25 04:34:14+00:00
A Full migration is not always required these days.

It is possible to write adapters to API interfaces. Many proprietary APIs become de-facto standards when competitors start creating those compatibility layers out of the box to convince you it is a drop-in replacement. S3 APIs are good example Every major (and most minor) providers with the glaring exception of Azure support the S3 APIs out of the box now. psql wire protocol is another similar example, so many databases support it these days.

In the LLM inference world OpenAI API specs are becoming that kind of defacto standard.

There are always caveats of course, and switches go rarely without bumps. It depends on what you are using, only few popular widely/fully supported features or something niche feature in the API that is likely not properly implemented by some provider etc, you will get some bugs.

In most cases bugs in the API interface world is relatively easy to solve as they can be replicated and logged as exceptions.

In the LLM world there are few "right" answers on inference outputs, so it lot harder to catch and replicate bugs which can be fixed without breaking something else. You end up retuning all your workflows for the new model.
by cperciva | 2025-11-25 04:39:05+00:00
One issue, as they point out, is that we now do minor version updates every 6 months, and you need to update for each one. (We have a 3-4 month period where both are supported, but e.g. 15.0 will be EoL before 15.2 is released.)

We are aware that this isn't ideal for some users, but it was a necessary tradeoff. We might be able to improve this in the future (possibly as "security updates for the base system, but no ports support") but no guarantees.
by woodruffw | 2025-11-25 04:39:11+00:00
> But those are both people problems… and you can’t solve a people problem with a technical solution.

I don’t think it is a people problem in this case: the only reason there’s a person involved at all is because we’ve decided to introduce one as an intermediating party. A more misuse-resistant scheme disintermediates the human, because the human was never actually a mandatory part of the scheme.
by fsckboy | 2025-11-25 04:39:49+00:00
>I'll believe you actually hold this opinion after you die from an entirely curable decease.

what does that have to do with anything?

narcissism and self importance are adaptive features we use to propel our genes into the future but that doesn't mean anybody else should care or help us, they are trying to look out for their own offspring

I'm talking about public policy, not your or my personal feelings. I think public policy should focus on creating the strongest possible tribe for the future.

when I hear people here whinge on the daily about how health care should be free for everybody, I yawn. No matter what line item something is in the budget, I want to hear "what do you think we should say "no" to? We can never buy all of everything, there are always tradeoffs, and if you aren't willing to announce your tradeoffs, you aren't serious.

what feelgood items will you say no to?

oh, and your other challenge, you would have been closer to the mark if you said "fsckboy, the only way you could hold that opinion is if you have been so remarkably healthy and accident free your entire life that it doesn't even make sense to you the degree to which other people want to endlessly talk about their personal and family frailties" nobody has ever needed to save my life, and i'm old now so nobody should care. Neither one of my parents ever took a single day off of work for illness.
by AnthonyMouse | 2025-11-25 04:40:02+00:00
> Later he decided to represent himself in court and failed

To be more specific, the government broke out their get out of court free card and claimed they weren't threatening to prosecute him even though they created a rule he was intending to violate. It's a dirty trick the government uses when they're afraid you're going to win so they can get the case dismissed without the court making a ruling.
by esperent | 2025-11-25 04:40:03+00:00
I haven't had much luck with skills being called appropriately. When I have a skill called "X doer", and then I write a prompt like "Open <file> and do X", it almost never loads up the skill. I have to rewrite the prompt as "Open <file> and do X using the X doer skill".

Which is basically exactly as much effort as what I was doing previously of having prewritten sub-prompts/agents in files and loading up the file each time I want to use it.

I don't think this is an issue with how I'm writing skills, because it includes skill like the Skill Creator from Anthropic.
by hansvm | 2025-11-25 04:40:30+00:00
I've seen a few of these in my career, if I understand the author correctly. You have a big ball of mud that can theoretically be 10x or 100x faster, but the costs are diffuse and can't be solved by just finding a hotspot and optimizing it.

It often happens for good reasons. Features get added over time, there are some scars from a mocking framework, simpler (faster) solutions don't quite work because they're supporting X which supports Y which supports Z (dead code, but nobody noticed), people use full datetime handling when they mean to access performance counters, the complexity of the thing means that you blow your branch prediction cache size budget, etc....

The solution is to deeply understand the problem (lots of techniques, but this comment isn't a blog post) and come up with a solution, like a ground-up rewrite of some or all of the offending section.
by kazinator | 2025-11-25 04:40:35+00:00
> That learning enabled the system to detect her intention to play hundreds of milliseconds before she consciously attempted to do so, says trial leader Richard Andersen, a neuroscientist at the California Institute of Technology in Pasadena.

Sounds like Libet's Delay and all that. Conscious awareness is just a documentary covering something that has been decided some half a second ago.
by ChrisArchitect | 2025-11-25 04:40:42+00:00
[dupe]

Discussions:

X's new country-of-origin feature reveals many 'US' accounts to be foreign-run

https://news.ycombinator.com/item?id=46028422

X begins rolling out 'About this account' location feature to users' profiles

https://news.ycombinator.com/item?id=46024417

Top MAGA Influencers on X/Twitter Accidentally Unmasked as Foreign Trolls

https://news.ycombinator.com/item?id=46024211

X Just Accidentally Exposed a Covert Influence Network Targeting Americans

https://news.ycombinator.com/item?id=46035574
by H8crilA | 2025-11-25 04:42:36+00:00
"PTSD" is going through the same semantic inflation as the word "trauma". Or perhaps you could say the common meaning is an increasingly more inflated version of the professional meaning. Not surprising since these two are sort of the same thing.

BTW, a more relevant word here is schizoid / schizoidism, not to be confused with schizophrenia. Or at least very strongly avoidant attachment style.
by teruakohatu | 2025-11-25 04:42:58+00:00
> 1. The nerf is psychologial, not actual. 2. The nerf is real but in a way that is perceptual to humans, but not benchmarks.

They could publish weekly benchmarks. To disprove. They almost certainly have internal benchmarking.

The shift is certainly real. It might not be model performance but contextual changes or token performance (tasks take longer even if the model stays the same).
by komali2 | 2025-11-25 04:43:15+00:00
That's exactly right, and that's fine. Our society is unwilling to take the steps necessary to end the root cause of drug abuse epidemics (privatization of healthcare industry, lack of social safety net, war on drugs), so localities have to do harm reduction in immediately actionable ways.

So too is our society unable to do what's necessary to reduce the startling alienation happening (halt suburban hyperspread, reduce working hours to give more leisure time, give workers ownership of the means of production so as to eliminate alienation from labor), so, ai girlfriends and boyfriends for the lonely NEETs. Bonus, maybe it'll reduce school shootings.
by omk | 2025-11-25 04:44:28+00:00
After seeing a synthetic version that mimics the tone well enough, the real HN once back here felt slightly less distinct. When every information style gets a believable AI twin, our usual cues for judging what’s credible start to wobble.

To be clear, the strange part wasn’t that it fooled me, it didn’t. The issue was some form of “signal contamination” that my brain experienced.
by vbezhenar | 2025-11-25 04:44:55+00:00
I'm using shortcuts <Super>+1 ... <Super>+4 to switch between virtual desktops. Let's say there's Xwayland application launched on desktop 1 and I'm on desktop 4. Vscode for example. Now I press <Super>+1 to switch to desktop 1. At this point, vscode starts printing "11111111" until I press Esc.

This bug manifests both for vscode and Idea. I configured these apps to run under native wayland, but they're not ready and other bugs manifest (e.g. no border around vscode window), which are less annoying, but annoying nonetheless.
by nostrademons | 2025-11-25 04:45:01+00:00
The point is you wouldn't deal with people. Every interaction becomes a transaction mediated by an AI that's designed to make you happy. You would never genuinely come in contact with other perspectives; everything would be filtered and altered to fit your preconceptions.

It's like all those dystopias where you live in a simulation but your real body is wasting away in a vat or pod or cryochamber.
by Joel_Mckay | 2025-11-25 04:46:07+00:00
>I don't have a filter list for compromised proxy servers and VPNs.

Someone just joined the nuisance forums, and grabs the same Socks/Telegram proxy list they all use (mostly old infected/open servers.) When it comes to firewall rules it is a sensitive matter, and depends on the firewall setup (black-hole bans are generally considered rude, as even handshakes are lost.)

For fairly recent personal ban lists could try:

https://github.com/bitwire-it/ipblocklist

https://www.iblocklist.com/lists

And a Pi-hole router as a DNS sinkhole:

https://github.com/pi-hole/pi-hole

Sanitizing IP lists both before and after parsing is important, and checking for malformed or whitelisted blocks is wise.

>Outbound, now that is more difficult to assess

SELinux and firewall rules will handle that just fine for services, but is cumbersome for desktop users. In general, most just try "unshare -r -n /home/$USER/someApp" or a sandbox/VM to prevent some useful user-space program from connecting to the web.

Dumping local traffic with wireshark or iftop is also rather common practice.

Best of luck, =3
by mesenga | 2025-11-25 04:47:22+00:00
We are building Beddel, an open protocol and secure runtime designed to bring governance and predictability to AI Agents. When we started building agents, we realized that opaque "black box" execution loops are a nightmare for security and compliance, so we wanted a way to define agents that is transparent, auditable, and safe by default. Beddel treats Agent definitions as declarative YAML schemas rather than just code, allowing our runtime to wrap every interaction in a security layer that enforces rules before execution ever happens. In this alpha release, we are introducing a declarative protocol for portable agent definitions, built-in compliance engines (GDPR/LGPD) that automatically check PII handling and consent flows, real-time threat detection, and immutable audit trails for forensic logging. We believe the future of AI Agents requires a standard, safe protocol that enterprises can actually trust, and we are open-sourcing the core runtime to start this conversation. The repo includes the parser, compliance engines, and the isolated runtime environment—we’d love your feedback on the schema design and our approach to compliance enforcement: https://github.com/botanarede/beddel-alpha.

Finally, we designed Beddel to be the safe substrate for Generative Agent Creation. While current market standards often rely on LLMs generating executable code (like Python scripts) to spawn new behaviors—creating a massive sandboxing and security nightmare—Beddel solves this via its strict schema architecture. Because our agents are defined purely by YAML configuration rather than arbitrary code, an AI can safely act as an "Architect," composing and deploying new sub-agents on the fly without ever introducing arbitrary code execution risks. This enables self-organizing agent swarms where the logic is generated by GenAI, but the security boundaries remain rigidly enforced by our deterministic runtime.