MurphyA/hacker-news huggingface dataset:
by Quarrel | 2026-03-06 16:04:52+00:00
Why?

It seems like there are two options:

a) The "founder" of the code disappears in to the ether, and it is the equivalent of "version X only";

b) The "founder" stays involved, and if GPL 3 is updated, they can choose.

only b is worth speaking of. In b, isn't having someone in a position to make a choice much better than no one? What is the boogie monster that is the worry? The FSF puts out the 4.0 version, with a special "except for boramalper" clause, that lets you specifically monetise the hell out of it while keeping it closed source? I would not lose much sleep over that.

Stallman is a nutcase, in an endearing way (ok, maybe you have to have moved in the right circles). But he has put in place a system that needed just such a nutcase, who established clear black lines that could not be crossed, and who was also writing enough amazingly meaningful code that we needed to take his license seriously, that could then establish the institutions and governance to make it all live beyond him.
by prh8 | 2026-03-06 16:04:53+00:00
For readers not in Washington, there is currently legislation being worked on that is essentially a millionaire's tax, (simplified as) 10% income tax on income over 1 million dollars, inflation adjusted.

There are a few very angry, emotional, and vocal opponents of this in most corners of the internet, although very few of them actually make a million dollars and there are many million+ income people supporting this.

Demographically, there are over 3 million households in WA, and only 20k of them would be affected.
by squidleon | 2026-03-06 16:05:19+00:00
Outlands is impressive from a technical standpoint, they've put an insane amount of work into it and the player count speaks for itself. I played there for a while.

Personally though, I feel they've overengineered it a bit. So many custom systems layered on top that it starts to feel more like WoW with UO graphics than actual UO. The original charm was in the simplicity
you, a sword, and a world that didn't care about your feelings. But that's just my taste, and clearly thousands of players disagree with me, so what do I know.
And yes, the fact that official UO is still running in 2026 is both beautiful and insane
by Chris559 | 2026-03-06 16:05:30+00:00
Just took a closer look and this is really impressive. The terminal-style workflow and fast navigation make it feel much closer to professional tools than most platforms for individual investors. I especially like how easy it is to scan multiple companies and see key fundamentals quickly without jumping between pages.

One feature that could be interesting later is saved screeners with alerts so users can get notified when companies match specific criteria. Overall, very promising direction.
by nothrabannosir | 2026-03-06 16:05:32+00:00
Which actual law should send them to jail?

The law is constantly applied to Trump and his administration. The judicial branch keeps reining him in: National guard, ice, tariffs—-literally TFA for Pete’s sake.

Parent post isn’t about any specific law, it’s about wanting to see a result and working backwards from there: my political opponents should go to jail.

Guess what will happen? The administration after that will send your politicians to jail. And the bananificiation of the US will be complete.

If you genuinely want Trump to go to jail , get Congress to create actual laws that he’d be breaking, with actual clear unmistakable language about its consequences. Raise the votes in the midterms. SCOTUS will enforce it: they have done so, every time, when Congress is clear and decisive. They have indicated as much!

The judicial branch is the only one left doing its job. The law applies. You don’t like how it looks, and you’re not alone, but it applies.
by persedes | 2026-03-06 16:05:51+00:00
Agreed, I think it also acts as a hiring filter to scan for candidates that have been exposed to this kind of language and can speak it fluently. The bigger the cooperation, the more widespread that is though, don't see it as often in mid sized companies. Was looking into a director role at a large org and there were lots of very new words thrown at me very quickly.
by hoopyKt | 2026-03-06 16:05:54+00:00
You're ignoring the part where the maintainer demonstrated that version 7 isn't a relicense of LGPL work but a complete rewrite based on public domain research and algorithms. That stack overflow article is irrelevant to this situation, and again, versions 6 and before have not been "taken over" they still exist exactly as they did a week ago and are still available to anyone that wants them in full license compliance. LGPL requires the source be made available, not that the source's distribution channels never be used for something else.
by sn0wflak3s | 2026-03-06 16:06:16+00:00
I get this. I don't think either of you is wrong. There's a real loss in not writing something from scratch and feeling it come together under your hands. I'm not dismissing that.

I have immense respect for the senior engineers who came before me. They built the systems and the thinking that everything I do now sits on top of. I learned from people. Not from AI. The engineers who reviewed my terrible pull requests, the ones who sat with me and explained why my approach was wrong. That's irreplaceable. The article is about where I think things are going, not about what everyone should enjoy.
by rodchalski | 2026-03-06 16:06:27+00:00
The SQL injection analogy is instructive but the framing matters. SQL injection got fixed not by teaching databases to recognize hostile SQL — it got fixed by parameterized queries, which took the trust boundary out of the data path entirely. The fix wasn't smarter parsing; it was structural separation.

The same category of fix exists for agent security today, without waiting for models to get better at detecting injection. Assume the LLM will be compromised — it's processing untrusted input. The constraint lives at the tool call boundary: before execution, a deterministic policy evaluates whether this specific action (npm install, bash, git push) is permitted in this context. The model's intent doesn't matter. The policy doesn't ask 'does this look malicious?' — it enforces what's allowed, period. Fail-closed.

The Cline config tells the full story. allowed_non_write_users='*' combined with unrestricted Bash is not a model safety failure. It's an authorization architecture failure. The agent was configured to allow arbitrary code execution triggered by any GitHub account. Prompt injection just exercised what was already permitted.

Enforcement has to live outside the context window. Anything inside it — system prompt rules, safety instructions, 'don't run npm install from untrusted repos' — becomes part of the attack surface the moment injection succeeds. The fix isn't better prompting. It's deterministic enforcement at the execution boundary, independent of whatever the model was convinced to do.
by mannanj | 2026-03-06 16:06:27+00:00
The person I responded to was condescending himself and clearly was emotionally dumping on someone else. I don't condone non-consensual aggression, abuse, and emotional labor that inexperienced left-brained engineers seem to think is a healthy norm. no troll intent here, seriously just hoping to share some empathy and suggest "Go do some emotional processing and stop dumping that on internet strangers and expecting them to do your emotional work for you"

I don't have intent to troll and engage in any aggression, it's not my interest. You can check my post history to see I have a long history in this community of non-troll engagement.

You can say what you want though, and I will still say I don't consent to doing your emotional labor for you.
by reactordev | 2026-03-06 16:06:29+00:00
Being a legendary blacksmith was the whole point. Where crafting was the end game state for crafters. The gear produced was max durability, max dmg, max armor rating. The furniture for your castle had to come from someone, somewhere.

The whole point of the game was to live in this fantasy world, not beat it. There were no quests. No antagonist. Just good and evil and everyone in between. For once I wish a studio would take this to heart and build something like that again. Minecraft exploded due to this sandbox nature. However, you still got to give players a shovel and a bucket.
by blacksmith_tb | 2026-03-06 16:06:47+00:00
I don't get the impression Anthropic tried to walk anything back, they just balked when they were informed that the DoD wasn't willing to abide by their terms to refrain from using Claude for surveillance or straight up selecting targets to kill. But you're right that means Anthropic's hands are not exactly clean, just less bloody than OpenAI's or xAI's
by mbbutler | 2026-03-06 16:07:12+00:00
Two use-cases recently where Claude sucked for me:

1. Performance-critical code to featurize byte slices for use in a ML model. Claude kept trying to take multiple passes over the slice when the featurization can obviously be done in one. After I finally got it to do the featurization in one pass it was double-counting some bytes but not others (double counting all of them would have been fine since the feature vector gets normalized). Overall it was just very frustrating because this should have been straight-forward and instead it was dogshit.

2. Performance-critical code that iterates over lines of text and possibly applies transformations, similar to sed. Claude kept trying to allocate new Strings inside of the hot-loop for lines that were not transformed. When I told it to use Cow<'a, str> instead so that the untransformed lines, which make up the majority of processed lines, would not need a new allocation, Claude completely fucked up the named lifetimes. Importantly, my CLAUDE.md already tells Claude to use copy-on-write types to reduce allocations whenever possible. The agent just ignored it, which is _the_ issue with LLMs: they're non-deterministic and any guidance you provide is ultimately just a suggestion.
by clocksmith | 2026-03-06 16:07:13+00:00
Proof that you are a genius:

```lean

inductive HumanNeed where
| retailArithmetic
| genericLinkedInPost

inductive IndustrySolution where
| commodityALU
| frontierAutocomplete

def optimal : Need → IndustrySolution
| .retailArithmetic => .commodityALU
| .genericLinkedInPost => .frontierAutocomplete

def latency : IndustrySolution → Nat
| .commodityALU => 1
| .frontierAutocomplete => 248000

theorem superbowl_ads_have_not_improved_superdope_adds :
latency (optimal .retailArithmetic) < latency .frontierAutocomplete := by
decide

```
by HEmanZ | 2026-03-06 16:07:14+00:00
“ Most of the attraction of living there historically was its extremely business-friendly environment.”

How old are you? What propaganda told you this? In my generation (young millennial/genz) the attraction of living in Seattle, which pulled me and almost a dozen professional friends at this point has been:

- high quality urban living in a temperate environment. Including access to great parks, waterfront, bikeability in the city

- access to great outdoors and regional amenities like skiing, ocean fishing, hiking, wine country

- liberal policies and general friendly society (it’s friendlier here than the east coast)

- no state income tax (we’re all very high tax bracket)

- a high enough income population that you can find a plethora of high-end products and services that cluster around high income earners (only a few us cities have this stronger than Seattle I feel)
by rodchalski | 2026-03-06 16:07:37+00:00
The proxy approach is right — enforcement survives prompt injection because the policy engine isn't inside the LLM context. Most guardrails fail the moment you ask the agent to ignore them.

One architecture question: if an orchestrator spawns sub-agents with their own MCP connections, does each get a separate Kvlar instance? Is there a way to express policy hierarchies — parent constraints propagating to child agents? This gets relevant quickly in multi-agent pipelines where sub-agents have overlapping tool access and you don't want the parent's full permission scope implicitly inherited.

Fail-closed on no rule match is the right default. Most systems ship the opposite and discover why that's wrong in production.

Filesystem coverage would be high-value to add next. Agents reading ~/.env, ~/.ssh/config, ~/.aws/credentials — that's where unintended exfiltration typically happens. Not always "DROP TABLE", sometimes just reading the wrong file at the wrong time.
by andsoitis | 2026-03-06 16:07:44+00:00
I’m not sure it is unexpected. Jobs dwindle when there’s uncertainty.

And we have a lot of economic, political, and geopolitical uncertainty.

So, if anything, I would be surprised if we don’t see this level of job reduction consistently for at least the rest of the year.

What is less clear to me is whether it will accelerate or whether it will continue for a few years.
by jajuuka | 2026-03-06 16:07:48+00:00
Whoever thought it was a good idea to have a full size address area AND a full size vertical bar at the same time needs to find their way to the door. On desktops and large laptops it's not a major problem, but smaller displays it's wasting so much space.

This design feels very generic though. Doesn't really stand out from any other modern browser.
by hellojesus | 2026-03-06 16:07:50+00:00
I think most people here are extrapolating the intent behind this law, the triviality with which it can be bypassed by minor account holders, and what that means for the future. Once this law is in effect, it will be ineffectual. Minors that current don't know what VMs are, what live booting is, what keyloggers are, etc. will learn immediately once blog posts start circulating about bypass mechanisms. Parents will then go back to the legislature and say the law as-written sucks, and they will demand better laws, but the only way to get better is to force all devices to authenticate with the isp with a gov-issued id/token to prove the account is not a minor. But the only way to prevent even further workarounds like the OS lying is to force hardware based remote attlestation. And that means the death of general computing and the death of any anonymity.
Show HN: Codaholiq, AI automations for GitHub repositories
by NeuroFunky | 2026-03-06 16:08:16+00:00
Hi HN,

I kept finding myself writing scripts or manually running prompts to do things like PR reviews, documentation generation, or issue triage on my GitHub repositories.

After doing this enough times, I decided to build a small platform to automate these workflows.

I recently open sourced it:

https://github.com/Njuelle/Codaholiq

Codaholiq lets you run AI-powered workflows triggered by GitHub events.

You connect a repository and define automations that run when certain events occur, such as:

- pull request opened
- push to a branch
- issue created
- cron schedule
- manual trigger

Each automation defines:

- a trigger
- an AI provider or model (Claude Code, Codex, Gemini, etc.)
- a prompt template
- optional conditions on the GitHub event payload

When the event happens, Codaholiq renders the prompt using variables from the event context and dispatches a GitHub Actions workflow that runs the AI task.

The platform also tracks executions with:

- real-time log streaming
- token usage and cost tracking
- execution history

One design goal was self-hosting, so the entire platform can run locally or on your own infrastructure.

The architecture is intentionally simple:

- GitHub webhooks trigger automations
- jobs are queued using Redis and BullMQ
- the NestJS backend processes the queue and dispatches workflows to GitHub Actions
- AI models are called through providers
- logs and token usage are streamed back to the UI

The full platform can run with Docker using Postgres and Redis.

Example automation:

An automation could trigger when a pull request is opened.
It sends the PR diff to an AI model asking for a code review, then runs the task through a GitHub Actions workflow.

Some possible use cases:

- automated PR reviews
- generating documentation from diffs
- code refactoring suggestions
- issue triage
- automatic changelog generation

It's still early, but the core pieces are working.

One thing I'm unsure about is whether this project makes more sense as:

- a self-hosted automation tool
- or a hosted version that simplifies setup and management

I'm curious how teams here would prefer to run something like this.

Any feedback is very welcome.
by marcosdumay | 2026-03-06 16:08:23+00:00
Mass deportation means economic contraction, and if done quickly it means economic disruption and loss of domestic wealth.

Indiscriminate tariffs means deindustrialization, unpredictable tariffs means stagnation (inability to grow).

Blatant corruption means stagnation.

Aggressive international relations means disruption of any market that touches the rest of the world (with loss of wealth). Active war means the same thing as mass deportation and non-productive spending, so more contraction.

Trump has an incredible ability to hit all the targets.
by bitwize | 2026-03-06 16:08:24+00:00
> So long as their productivity was on par with the rest of the team there was no issue.

Emphasis added. And anyway, for most software dev in most shops it wasn't true; most development takes place in whatever IDE the group/organization standardized on for the task, to make sure everyone gets proper tooling and to make collaboration and information sharing easier. Think of all the Java enterprise software developed by legions of drones in the 2000s and 2010s. They all used Eclipse, because Eclipse is what they were given.

It's only with the emergence of whiny, persnickety Unix devs who refused to leave the comforting embrace of their editor of choice that shops in the internet/dotcom/startup tradition embraced a "use whatever tools you want" philosophy. They had uncharacteristically enormous leverage over the tech stack being deployed in such businesses and could force employers to make that concession. And anyway, what some of them could do with vi blew the boss's mind.

It is true that we don't have a whole lot of hard data from large organizations that show AI productivity improvements. But absence of evidence is not evidence of absence. Turns out, most large organizations just haven't adopted AI in the amount and ways that could make a big impact.

But we have enough anecdata from competent developers to suggest that the productivity gains are huge. So big, AI not only lets you do your normal tasks many times faster, it puts projects within reach that you would not have countenanced before because they were too complex or tedious to be worth the payoff.

So no. Refusing to use AI is just pure bloodymindedness at this point—like insisting on using a keypunch while everyone around you discovers the virtues of CRT terminals and timesharing. There were people like this even in the 1970s when IBM finally came around and made timesharing available in their mainframes. Those people either got up to speed or moved on to a different profession. They couldn't keep working the way they'd been working because the productivity expectations changed with the availability of new technology.
by nkassis | 2026-03-06 16:08:32+00:00
Just understand that you are one of the player groups that Blizzard targets and they found that a significant if not plurality of their player groups were solo players. This is why they've actively changed the product to try to keep that player base subbed between expansion. By their account it seems to work.

I do think Blizzard is big enough they can maintain multiple experiences. One thing that is challenging is a vocal group of players really feel like they need to do everything in the game. It's compulsory (some game design choice did also force that at times). This leads to them not enjoying the content not designed for them. Blizzard has a challenging line to solve.

Classic was the right move, I do agree with your idea of someone making a similar game with the original principles. It probably can't be Blizzard anymore, their have a 0-1M user problem. Anything they make has to cater to everyone or they get flak. So a smaller outfit needs to do it. Challenging in this funding environment.
by jimnotgym | 2026-03-06 16:08:34+00:00
I find it interesting how different companies have a different BS, that marks people as insiders. The insiders like to make the implication that it is the newcomer who is at fault, because they only know the real words for things. Slimey salesey newcomers pick up on it instantly.

Often it is misuse of terms that actually have real meanings that annoy me most
by mrweasel | 2026-03-06 16:08:39+00:00
In a previous job we used Terraform pretty heavily. I never got good at it, because it felt confusing, dangerous, and unnecessarily complicated for our use. More than once we saw that Terraform wanted to delete critical, stateful resources.

I get that the state file is probably some form of optimization, but it seems like a fairly broken concept. A friend of mine still use Terraform daily, and it's probably weekly he encounters Terraform wanting to do stupid shit.

Honestly if I never have to use Terraform ever again, I'd be pretty happy.
by LoganDark | 2026-03-06 16:08:43+00:00
There are some countries where assisted suicide is legal, if you can afford to make it there, and can make the case that it's truly what you want and believe is right for you. But, as you've noted, that doesn't take care of dependents unless they join you... Not that it can matter to you after your end, but in many cases, the emotional weight of what one's loss could do to others can indeed discourage them from going through with it.
by pibaker | 2026-03-06 16:08:50+00:00
I just saw this recent survey about whether or not people view their fellow citizens as morally good. Canada ranks first, with 92% respondents answering affirmatively.

It's not hard to imagine people like these extending their good will to foreigners, even "hostile" ones.

https://www.pewresearch.org/religion/2026/03/05/in-25-countr...

In contrast, "The United States is the only place we surveyed where more adults (ages 18 and older) describe the morality and ethics of others living in the country as bad (53%) than as good (47%)."
by cloverich | 2026-03-06 16:09:00+00:00
Which policies specifically? Certainly not the income tax on million+ income, seems pretty modest. We moved from TX. Property tax rate is low, no income tax sub million in income, schools are great (and almost all new), roads are fine and transit seeing massive investment. They definitely need to fix budget, but there's _ample_ wealth here to deal with it. I think they'll figure it out.

_Oregon_ has bad policies (10% income tax on all, upwards of 14% on high income earners at 400k); schools are in a rough place, their legacy pension system is a disaster. But Washington seems fine imo. TX and such states will always be a draw while their cost of living is low, if you don't mind the heat and general lack of outdoors (relative to PNW). IMO the weather and housing prices are the main tradeoffs between WA and TX.
by ihabselmi84 | 2026-03-06 16:09:22+00:00
}
This looks really interesting — especially the goal of making Bloomberg-style tooling accessible without the $20k/year price tag.

Curious about a few things:

1. What’s the source of the real-time market and options data? That’s usually the hardest (and most expensive) part of building something like this.
2. Are you planning to expose scripting / query capabilities similar to Bloomberg’s BQL or a Python API?
3. How are you thinking about latency vs cost tradeoffs for retail users?

If you can get fundamentals, options chains, macro indicators, and alerts into a fast keyboard-driven interface, that could be incredibly powerful for individual investors and indie quants.

Looking forward to seeing how this evolves