MurphyA/hacker-news huggingface dataset:
by nachocoll | 2026-03-10 09:09:48+00:00
The security angle is one of the most underappreciated risks in vibe coding. When developers don't understand the code that gets generated, they can't assess whether it's introducing vulnerabilities — hallucinated packages, insecure patterns, broken auth — and your finding that a "crazy amount" of AI-generated repos have severe structural flaws matches what a lot of teams are discovering in production.

This connects directly to a core principle from the Agile Vibe Coding Manifesto (https://agilevibecoding.org): "Automation must remain verifiable — their outputs remain understandable, reviewable, and verifiable by humans." The problem with pure vibe coding isn't just that AI makes mistakes; it's that the workflow removes the verification step entirely.

An automated security reviewer is a great practical response to this. Happy to test it on a project if you're still looking for early feedback.
by estsauver | 2026-03-10 09:10:43+00:00
They're certainly welcome to do whatever they're like, and for a microkernel based OS it might make sense--I think there's probably pretty "Meh" output from a lot of LLMs.

I think part of the battle is actually just getting people to identify which LLM made it to understand if someones contribution is good or not. A javascript project with contributions from Opus 4.6 will probably be pretty good, but if someone is using Mistral small via the chat app, it's probably just a waste of time.
by egorfine | 2026-03-10 09:11:03+00:00
It's not a legal requirement in my country. Thus they are volunteering to go extra mile in the implementation of the repressive laws.

I think they should resist as much as possible. Yes it was a legal requirement to gas the Jews and it was illegal to hide them.

Who do we cheer now? Those who abided to the law or those who broke it?
by rmykhajliw | 2026-03-10 09:11:24+00:00
The main issue is games. Drivers and overall performance under Linux for win games run under Wine is pretty low. The good stuff they became runnable but framerate of 12 fps is nothing for my razor laptop with rtx in Cossacs 3.

Now my setup is MacBook for work, and special game laptop Razer Blade especially for games with win11 removed defender/firewall and tons on useless stuff. Personally for me win7 will be enough but I just cannot install it on my laptop due to lack to drivers.
by petargyurov | 2026-03-10 09:12:52+00:00
It's easy but it's not cheap. Well, price is relative but capturing video is certainly cheaper.

Also, I am not sure how heavy LIDAR units are, but remember that the heavier the payload the more the flight time is reduced. Some drones can only have a single payload, so if you also want to capture (high-res) video/imgs you need to fly again.

It all depends on the use-case.
Show HN: Draft2final – CLI converts Markdown into manuscript and screenplay PDFs
by cosmiciron | 2026-03-10 09:13:09+00:00
I got tired of the last-mile problem in writing: I write in Markdown, but submitting a novel manuscript or screenplay means either wrestling with Word/InDesign, installing a multi-GB LaTeX stack, or accepting output that looks like a printed webpage — and gets rejected.

So I built a small CLI that knows what specific publication formats are supposed to look like and just renders them correctly.

draft2final story.md --as manuscript
draft2final script.md --as screenplay

The manuscript format handles the actual spec: Courier/TNR at 12pt, 1-inch margins, running headers with word count, ~250 words/page, proper title page, widow/orphan control. The screenplay format handles scene headings, action blocks, character cues, parentheticals, MORE/CONT'D, and dual-dialogue — using blockquote syntax so the source file stays clean Markdown.

Some implementation details that might interest people here:

The binary is 4MB. I wanted it installable in one command with no system dependencies — no LaTeX, no Pandoc, no headless Chrome. The font situation was the hardest part: proper manuscript formatting needs specific fonts, and some formats need CJK support, which means potentially large font files. I solved this with JIT font downloading — the CLI ships tiny and only pulls what it needs at render time.

A 30-page document renders in under 0.5s.

It handles right-to-left scripts and mixed Arabic/Latin/CJK text, which most converters either break or require manual configuration for.

It's open source. Each format is a self-contained TypeScript module, so adding new input or output formats is relatively straightforward — I'd like to eventually support APA, Chicago, and stage play formats, and contributions are welcome. That said, I'd especially like feedback from anyone who knows the manuscript or screenplay specs well — I'm sure there are edge cases I haven't hit yet.

Docs + syntax guide: https://draft2final.app/guide

npm install -g draft2final
by ptnpzwqd | 2026-03-10 09:13:16+00:00
I think this is a reasonable decision (although maybe increasingly insufficient).

It doesn't really matter what your stance on AI is, the problem is the increased review burden on OSS maintainers.

In the past, the code itself was a sort of proof of effort - you would need to invest some time and effort on your PRs, otherwise they would be easily dismissed at a glance. That is no longer the case, as LLMs can quickly generate PRs that might look superficially correct. Effort can still have been out into those PRs, but there is no way to tell without spending time reviewing in more detail.

Policies like this help decrease that review burden, by outright rejecting what can be identified as LLM-generated code at a glance. That is probably a fair bit today, but it might get harder over time, though, so I suspect eventually we will see a shift towards more trust-based models, where you cannot submit PRs if you haven't been approved in advance somehow.

Even if we assume LLMs would consistently generate good enough quality code, code submitted by someone untrusted would still need detailed review for many reasons - so even in that case it would like be faster for the maintainers to just use the tools themselves, rather than reviewing someone else's use of the same tools.
by riobard | 2026-03-10 09:14:11+00:00
Seamless WiFi roaming is mostly a client decision. The best you can do on AP is to:

a) optimize signal strength for coverage (stronger signals aren't always better in multi-AP deployment);

b) provide hints via 802.11k/v/r to help clients make, hopefully, better decisions;

c) forcefully drop and disassociate clients when signal is weak enough.

But if the client has bad WiFi implementation, there's nothing much you could do.

OpenWRT currently supports 802.11k/v/r, but optimizing coverage by adjusting signal strength and channels is left for experienced users to deal with manually. There is the are where some commercial offerings will do, but the result greatly varies. AFAIK there's no ideal system anyway coz physics is hard.
by prohobo | 2026-03-10 09:14:13+00:00
Court orders are different from psyops. The Bhattacharya thing, and the entire narrative around that stuff was essentially a psyop. Geo-restricting a Turkish politician because the authoritarian govt arrested him and gave a court order to restrict his account is - first of all - what all social media platforms must adhere to legally, and second of all is currently being contested by X in court.
by knorker | 2026-03-10 09:14:46+00:00
How is being late acceptable?

Let's say you have a job interview. You're 5min late, so they either don't hire you, or the receptionist says the interviewer is now not available. Are you now due the salary, because you being this late 5min cost you a lot of money?

If you in a private contract reject the terms of paying $5 per minute late, well then the other party now knows you plan to be late a lot, so they'll be glad if you take your business elsewhere.

Keeping people from being able to go home after their workday, effectively forced overtime, is incredibly disrespectful. And even if "it's not your fault", you are the only one that could have prevented it. So incentives should be in place that you don't. $5 per minute sounds fair.

If you force me to stay late for a full hour you'd BETTER pay me triple digits. But in this case the $300 for an hour may have to be shared among several people.
by bob1029 | 2026-03-10 09:15:04+00:00
I think the wafer scale compute is a massive deal. It's already being leveraged for models you can use right now and the reception on HN has been negligible. The entire model lives in SRAM. This is orders of magnitude faster than HBM/DRAM. I can't imagine they couldn't eventually break even using hardware like this in production.
by kakacik | 2026-03-10 09:16:00+00:00
Where I live, gourmet high quality burger joints definitely, and massively overwhelm McDonalds in number (Geneva, Switzerland). Even if I count in burger king. Shows that sometimes people pay for the quality even if they don't desperately need it. And its trivial to make better burgers than mcd, heck I can surpass them trivially at home with every ingredient, they are really the lowest level of quality, taste, looks, or (lack of) healthy components. You don't need Michelin * for that, far from it. Plus food is often cold outside of peak hours, something that never happened to me in proper restaurant.

Also, mcd ain't at the end much cheaper, just marginally, the choice of drinks is pathetic, usually no beer. The main reason folks go there because its easier/faster than getting table in real restaurant. But also the environment in mcd is absolute soulless cheap fugly shit. (there are kids corners to be fair, but they are often disgustingly dirty).

Its a very good analogy at the end IMHO, maybe just not tilting the way you intended, at least not here.
by leptons | 2026-03-10 09:16:29+00:00
>You seem afraid of non-hetero sexuality at every turn.

You don't know me well enough to form that opinion, and you're completely, absolutely wrong.

All I did was state that this "solution" isn't quite as clear-cut as it seems, and that it will likely backfire. I'm not sure what kind of dysfunction happened in your head for you to arrive at "afraid of non-hetero sexuality"??? Maybe don't imagine things that simply are not there.
by threatofrain | 2026-03-10 09:16:43+00:00
If AR/VR took off then something along the lines of liquid glass would be the only option for the entire design space. Early on there's going to be a lot of embedding of app context into the AR/VR setting to get a jump-start on content. But if people are going to be walking around with rectangular panes around their head, it's better that part of the app chrome is transparent.

Is this compromising readability? Yes, but now there's another kind of perception problem, and it's whether you can see what's literally in front of your eyes in physical space.
by Ametrin | 2026-03-10 09:16:54+00:00
Working on PDFBolt (https://pdfbolt.com) - a PDF generation API. You send HTML, a URL, or a Handlebars template with JSON data, get a PDF back. Uses Playwright underneath so modern CSS just works.

Lately been deep in PDF/X print production - PDF/X-1a and PDF/X-4 with ICC color profiles and CMYK conversion. Had to build 11 color space converters on top of PDFBox 3.0. Also shipped an AI template generator where you describe what you need and it creates a Handlebars template with sample data, plus expanded the gallery to 38 pre-built ones.

Right now template management lives in the dashboard - edits auto-create drafts, you can compare any two versions as rendered PDFs and roll back if something breaks. Working on an API so coding agents can create and version templates programmatically.
by eviks | 2026-03-10 09:17:01+00:00
You can't do that because the design of the whole system is dumb - instead of matching by unique (within the app) universal (=across apps) menu item id like "quit" that's hardcoded into the framework, you must match by menu item displayed name "quit Safari", which is different for every "quit MyNewShinyApp"

PS: and sometimes the name string is also dynamic "Navigate to the latest folder named XYZ", so you can't match at all!
by ffsm8 | 2026-03-10 09:18:33+00:00
There is nothing in the TOS last time I checked forbidding it's use with Claude code. It's only forbidden to utilize it in the running of the business.

So getting Claude code subscriptions for developers should be permissable and not be against anything... However, if you created a rest endpoint to eg run a preconfigured prompt as part of your platform, that'd be against it

But I'm neither a lawyer nor work for anthropic
by nachocoll | 2026-03-10 09:18:45+00:00
iOS is an interesting domain for vibe coding because the SwiftUI/UIKit conventions are well-represented in training data, but the edge cases — App Store submission requirements, entitlements, push notification provisioning — tend to be where AI-generated code breaks down badly. The "last 10%" problem.

What's your experience with the parts where the AI generated code you couldn't review or understand? That's often where the real costs show up — not in the initial working prototype but in the maintenance cycle months later.

This tension between fast generation and long-term maintainability is central to the Agile Vibe Coding Manifesto (https://agilevibecoding.org), which tries to formalize how Agile teams should approach AI-assisted development. Its ninth principle: "Generated systems remain readable, maintainable, and evolvable by humans, regardless of how they were produced." On native mobile especially, that's harder than it sounds.

Would love to hear what worked and what didn't.
by gadders | 2026-03-10 09:19:05+00:00
I used to work for Lotus, supporting 1-2-3.

Mucking around with autoexec.bat, config.sys, emm386 etc to get 1-2-3 to load was fun. Lots of TSRs using up memory. The amount of times I had to tell people to create a "clean config" by commenting out most of autoexec.bat...

We also had to post people floppy disks with the correct printer driver on. No downloads in those days.

"What would a piece of software have to do today to make you cheer and applaud upon seeing a demo?"

I was at LotusSphere when Lotus Notes 4 was announced and demo-ed. That got a standing ovation.
by akhrail1996 | 2026-03-10 09:19:12+00:00
The comparison with Qwen/Kimi by "comparable architecture size" is doing a lot of heavy lifting. Parameter count doesn't tell you much when the models aren't in the same league quality-wise.

I wonder if a better proxy would be comparing by capability level rather than size. The cost to go from "good" to "frontier" is probably exponential, not linear - so estimating Anthropic's real cost from what it takes to serve Qwen 397B seems off.
by rcxdude | 2026-03-10 09:21:12+00:00
3 and 4 are what that argument is based on, I believe. 3) on the basis that the output is not _reproduced_, and 4) on similar grounds that output that's just not at all the same as the input data isn't affecting the market for the original image (I think this is the more debatable one, but in general the existing cases have struggled at the early stages because the plaintiffs have not been able to actually point to output that is a copy of their part of the input, and this does actually matter).
by turleydesigns | 2026-03-10 09:21:17+00:00
Complexity-based routing is underrated as a cost strategy. The real win is making it invisible to the rest of your codebase, if swapping models requires any code change beyond a config, adoption dies in code review. I've been working on something similar as an npm package: one-liner install, OpenAI-compatible API, routes to cheaper models automatically. Happy to compare notes if you're still iterating on the classifier approach. Curious how you're handling token-count vs. semantic complexity as signals.
by throwaway2037 | 2026-03-10 09:21:28+00:00
> any content submitted that is clearly labelled as LLM-generated (including issues, merge requests, and merge request descriptions) will be immediately closed

Note the word "clearly". Weirdly, as a native English speaker this term makes the policy less strict. What about submarine LLM submissions?

I have no beef with Redox OS. I wish them well. This feels like the newest form of OSS virtue signaling.
by gbro3n | 2026-03-10 09:21:31+00:00
For anyone still watching this thread, I have reworked the UI to move the task board to the editor pane from the side bar, and have worked to improve the agents tracking of the core instruction set and current task reference in a way that allows working on parallel threads.

https://github.com/appsoftwareltd/vscode-agent-kanban
by sehansen | 2026-03-10 09:21:42+00:00
Gas turbines do 16% of nameplate capacity per minute without catching a sweat. 5% per minute isn't particularly extreme.

---

Let me quote page 10 of your source "In brief, most of the modern light water nuclear reactors are capable (by design) to operate in a load following mode, i.e. to change their power level once or twice per day in the range of 100% to 50% (or even lower) of the rated power, with a ramp rate of up to 5% (or even more) of rated power per minute". Your own source defines "load following" as changing the targeted power level once or twice per day.

Again on page 14 (about how the French currently run their nuclear plants): "The nuclear power plants operating in the load following mode follow a variable load programme
with one or two power changes per period of 24 h". Weirdly enough this is contradicted by table 2.1 on page 20 where they do four changes per day.

---

> Oh look. What's limited is an actual emergency ramp up of 5% per second or power drops of 20% per minute.

If you look at table 2.4 on the same page it states that it (the Russian VVER-1200) can do the 5% per second/20% per minute emergency change 20 000 times over the lifetime of the reactor. The 10% per minute change can also only be done 20 000 times over the lifetime of the reactor. Table 2.2 on page 21 helpfully calculates that 15 000 cycles is once per day for 40 years, so the VVER-1200 only can do a bit more than one >5% change per day (outside of emergencies) assuming a similar 40 year lifespan. And that was the point of my footnote: that nuclear plants technically can go faster than 5% but not up and down on a minute-by-minute basis.
by bonesss | 2026-03-10 09:22:48+00:00
Any sufficiently advanced LLM-slop will be indistinguishable from regular human-slop. But that’s what they are after.

This heuristic lets the project flag problematic slop with minimal investment avoiding the cost issues with reviewing low-quality low-effort high-volume contributions, which should be near ideal.

Much like banning pornography on an artistic photo site, the perfect application on the borderline of the rule is far less important than filtering power “I know it when I see it” provides to the standard case. Plus, smut peddlers aren’t likely to set an OpenClaw bot-agent swarm loose arguing the point with you for days then posting blogs and medium articles attacking you personally for “discrimination”.
by lyu07282 | 2026-03-10 09:24:17+00:00
What this doesn't mention is the "cost" to the public: the inevitable bailouts after it all comes crashing down again, the massive subsidies that Datacenters get from tax payers, the fresh water they consume, the electricity price hikes for everyone else, the noise, air and water pollution and the massive health impact on the surrounding population of every datacenter. The jobs that it destroys and the innocent people it kills through use of the technology in military targeting and autonomous weapons usage.
by martin_renaud | 2026-03-10 09:24:17+00:00
Great question. Qcut is intentionally free for quick edits and runs locally in the browser to remove friction — no installs, no accounts.

Our main business is actually the B2B side: we're building AI infrastructure for live events (Edit on the Spot) that automatically segments recordings and generates clips at scale.

There are other browser editors like Kapwing, Clipchamp, and Canva Video, but many require accounts or run heavier workflows. We wanted something you can open and use instantly.
by BlackFly | 2026-03-10 09:24:22+00:00
It is enforceable, I think you mean to say that it cannot be prevented since people can attempt to hide their usage? Most rules and laws are like that, you proscribe some behavior but that doesn't prevent people from doing it. Therefore you typically need to also define punishments:

> This policy is not open to discussion, any content submitted that is clearly labelled as LLM-generated (including issues, merge requests, and merge request descriptions) will be immediately closed, and any attempt to bypass this policy will result in a ban from the project.
by wongarsu | 2026-03-10 09:24:44+00:00
GPT 4 was rumoured/leaked to be 1.8T. Claude 3.5 Sonnet was supposedly 175B, so around 0.5T-1T seems reasonable for Opus 3.5. Maybe a step up to 1-3T for Opus 4.0

Since then inference pricing for new models has come down a lot, despite increasing pressure to be profitable. Opus 4.6 costs 1/3rd what Opus 4.0 (and 3.5) costs, and GPT 5.4 1/4th what o1 costs. You could take that as indication that inference costs have also come done by at least that degree.

My guess would have been that current frontier models like Opus are in the realm of 1T params with 32B active
by baroudi | 2026-03-10 09:25:24+00:00
Introducing more colors (or effects) without a way to abstract over them will cause a lot of issues. It is already painful to work with async, one have to either accept a lot of code duplication or to perform some obscure black magic with the macro system.

Also, the language is already inelegant with each monad having its own syntactic sugar (result, option and async).
by nachocoll | 2026-03-10 09:26:21+00:00
The "no PhD required, grandma-approved" framing is a really honest description of what vibe coding enables at its best: domain experts building useful tools for real people, without needing to be software engineers first.

The BSL-1.1 license choice is interesting too — shows you're thinking about sustainability and intent, not just shipping fast. That kind of explicit decision-making is actually what separates vibe coding projects that survive from ones that collapse: when the human behind the project is thinking about architecture, maintainability, and accountability.

Somewhat related: the Agile Vibe Coding Manifesto (https://agilevibecoding.org) is trying to formalize exactly these principles — that customer value and human accountability still drive everything even when AI is writing most of the code. Your project is a good example of vibe coding done with intention.

Good luck with Skales — the accessibility angle (no Docker, no CLI) is genuinely underserved.
by mschild | 2026-03-10 09:26:34+00:00
Surprisingly, I haven't heard of Uruky yet, even though I'm actively looking for EU replacements to a lot of international companies.

I have subscribed for a month and will give it a try.

One feedback already though. Some of the German translations are...not great.
For example, on the landing page under the "Not another AI tool". In English you write "We find it hard to do in a sensible, responsible, and respectful way."
In the German translation its "Es fällt uns schwer, vernünftig, verantwortungsvoll und respektvoll zu handeln."

The German translation makes it sound like you (as in you as a company and person) have a hard time being respectful, not the actual AI implementation.