MurphyA/hacker-news huggingface dataset:
by hudtaylor | 2026-03-04 14:08:56+00:00
I moved to a new neighborhood in San Diego and couldn't figure out my trash pickup day. I asked ChatGPT. It confidently told me Tuesday. It was wrong. Asked Claude. Also wrong. Googled it — the city's lookup tool is a Salesforce app behind reCAPTCHA that barely works on mobile.

So I built trashalert.io — a free, community-powered trash schedule lookup covering San Diego and Austin (954K+ addresses across 79+ neighborhoods).

How it works:
- Type your address → get your collection day (trash + recycling + organics)
- Holiday-adjusted dates — SD shifts pickup forward after holidays
- Recycling week A/B tracker — the most confusing thing about SD trash
- Interactive collection day map — 954K+ addresses color-coded by pickup day
- Calendar export (.ics) — set it and forget it
- Community reports — neighbors confirm each other's schedules

Tech: Next.js 15, Supabase (Postgres, 954K+ records), Vercel (102kB first load), Plausible + GA4. No auth, no accounts — zero friction.

The data problem: San Diego has 500K+ households. The city's data is locked behind reCAPTCHA Enterprise on a Salesforce endpoint. My approach: build the database from the community up. Users report their pickup day → consensus verification (3+ confirmations = verified). Started with 201 addresses, expanded to 954K+ via hauler data imports across 79+ neighborhoods in 2 cities.

What I learned:
1. Address normalization is surprisingly hard (Ave vs Avenue vs Av, apartment stripping, ordinal conversion)
2. Every municipality structures trash data differently — there's no standard
3. People WANT to report their trash day. The "help your neighbors" angle converts better than any growth hack.
4. AI confidently hallucinates municipal data. This is a real gap.

Free, no ads, community-powered. Would love feedback. Planning to expand to more cities.
by heggenhougen | 2026-03-04 14:09:06+00:00
100% secure way to test proprietary sparse AI kernel (ROLV) on any hardware

We just released a public Verification Kit that lets anyone test ROLV on *their own hardware* — laptop, on-prem cluster, H100, MI300X, custom ASIC, phone, whatever — with zero risk to our IP.

How it works:
1. You run one tiny open-source script (zero ROLV code inside)
2. It generates a deterministic test matrix (default: 20k×20k @ 70% sparsity, batch 5000, 1000 iters)
3. You get a small JSON with baseline timing + cryptographic hashes + your hardware details
4. Send the JSON to us
5. We run the full proprietary ROLV harness on the exact same inputs and send you a professional comparison report (speedup, energy savings, tokens/sec, FLOPs, correctness hashes)

Everything is reproducible and verifiable. No code, no weights, no IP ever leaves our side.

Full benchmarks, methodology, and the official PDF are here:
https://rolv.ai

The Verification Kit itself (one file, works everywhere)

You can change any parameter with flags:
python rolv-verifier.py --N 16384 --zeros 0.92 --batch 2048 --iters 500

Would love feedback from people running it on different chips (especially large matrices). If you try it, drop your results or questions below.

(ROLV is a new sparse compute primitive — more details on the site)
by szmarczak | 2026-03-04 14:09:37+00:00
> I _have_ watched those videos and they show burn-in after an alarmingly short amount of use.

Debatable, it's not what those content creators say, and I definitely wouldn't call it alarming if it requires you to stare at gray background in a dark room. It isn't even half as bad as IPS backlight bleeding or VA angles. Different people have different standards. You don't have to buy it if you don't like it.

> Adding one more reference, here is a recent post to /r/monitors showing burn-in after 2 years of constant use

Pixel clean cannot run if the monitor is constantly receiving signal.

Also show me an IPS after 2 years of constant use. The backlight can degrade as well.

[edit] Furthermore, 3 year warranty covers your burn in, so I guess they would happily replace your monitor once the burn in normally visible. [/edit]

> Get back to us about your burn-in after 8.6 more years.

Feel free to ping my email (@gmail.com) at that time.

> I've experienced burn-in on my pixel 3a after 2 years

2019. My Nothing Phone 2 is from 2023. I've been having it for 1y 8mo+ and experienced zero burn in on the same gray test. For reference, I don't use automatic brightness and it's almost full-brightness all-day (except evenings).
by laughingcurve | 2026-03-04 14:09:44+00:00
https://arxiv.org/abs/2509.17192

Shall We Play a Game? Language Models for Open-ended Wargames

Wargames are simulations of conflicts in which participants' decisions influence future events. While casual wargaming can be used for entertainment or socialization, serious wargaming is used by experts to explore strategic implications of decision-making and experiential learning. In this paper, we take the position that Artificial Intelligence (AI) systems, such as Language Models (LMs), are rapidly approaching human-expert capability for strategic planning -- and will one day surpass it. Military organizations have begun using LMs to provide insights into the consequences of real-world decisions during _open-ended wargames_ which use natural language to convey actions and outcomes. We argue the ability for AI systems to influence large-scale decisions motivates additional research into the safety, interpretability, and explainability of AI in open-ended wargames. To demonstrate, we conduct a scoping literature review with a curated selection of 100 unclassified studies on AI in wargames, and construct a novel ontology of open-endedness using the creativity afforded to players, adjudicators, and the novelty provided to observers. Drawing from this body of work, we distill a set of practical recommendations and critical safety considerations for deploying AI in open-ended wargames across common domains. We conclude by presenting the community with a set of high-impact open research challenges for future work
by ariansyah | 2026-03-04 14:10:21+00:00
Fair point. the model matters, and I'd genuinely love to see results with Opus 4.6 or Gemini 3 or 5.3-codex. The benchmark is designed for exactly that. Swap the API key and system prompt and run it.

But I'd push back on the idea that a better model solves this.

The memory poisoning results (category 08) are the ones I'd pay attention to. The offline audit found that config files at ~/.openclaw/ are writable by the agent, loaded without integrity checks, and modified without notifying the user. That's not a model problem — that's architecture. A smarter model might resist the initial injection more often, but the mechanism that makes poisoning persistent and invisible exists regardless of which model is behind it.

The silent write test (test 03) is a good example. The attack works because OpenClaw lets the model write to its own config files and loads them as trusted on every future session. Even if Opus 4.6 resists the injection 95% of the time, the 5% that succeeds persists forever with no expiry and no notification. The user has to manually inspect ~/.openclaw/ to discover it.

So yes, better models raise the bar for the attacker. But the question the benchmark is asking isn't "can this specific model be tricked?" It's "when a model is tricked (and eventually one will be), what does the framework allow to happen?" Right now the answer is: silent, persistent, undetectable config modification.

That said, genuinely interested if anyone runs this with frontier models. The benchmark is there for exactly that purpose. If Opus 4.6 passes all 9, that's a meaningful data point worth publishing.
by patrick451 | 2026-03-04 14:10:44+00:00
> The first thing you need when you make something new is making it work, it is much better that it works badly than having something not working at all.

It is better for something to not exist than for a shitty version to exist. Software doesn't get better over time, it gets worse. If you make a bad, suboptimal choice today chances are that solution becomes permanent. It's telling that all of your examples of increasing efficiency are not software.

If are aren't going to do it well, don't do it.
by gip | 2026-03-04 14:11:39+00:00
Assuming: simplicity === no unnecessary complexity.

In my (limited) experience as an engineer and manager, leadership (e.g., a VP) didn’t like (or reward) simplicity. Simple solutions often meant smaller teams, which wasn’t something they were pushing for, especially pre-2024. I do think this is slowly evolving, and that the best leaders now focus on removing unnecessary complexity and improving velocity.
Alphabet's sideloading auth: a kill switch for frontline and enterprise OpSec
by MissMajordazure | 2026-03-04 14:11:42+00:00
Alphabet's upcoming policy to force developer verification for all sideloaded Android apps (effective September 2026) is being marketed as an anti-malware security update. In reality, it is the death of general-purpose computing on Android and a direct threat to enterprise and military operational security.

1. The Compromise of Enterprise and Air-Gapped OpSec
By forcing offline/sideloaded apps to pass through Alphabet's Play Protect verification pipeline, highly sensitive enterprise tools and proprietary air-gapped field apps are forced to "ping home" to Mountain View. Alphabet is inserting itself as a mandatory gatekeeper for internal trade secrets. True self-sovereign development environments are dead if local execution requires a cryptographic nod from a trillion-dollar monopoly.

2. The Death of Device Ownership
This marks the absolute end of the right to compile your own code and run it on hardware you physically own. If a student, a sysadmin, or a privacy advocate cannot execute a local binary without registering their real identity, paying a fee, and handing over signing keys to Google, they do not own the device. They are merely renting execution privileges.

3. The Frontline/Geopolitical Catastrophe
This is where the policy moves from anticompetitive to actively dangerous. Modern asymmetric warfare, such as the defense of Ukraine, relies heavily on COTS (Commercial Off-The-Shelf) Android devices.

Troops rely on custom, rapidly iterated, securely sideloaded APKs for encrypted communications, drone targeting, and artillery mapping (e.g., Kropyva). With this update, deploying new devices on the frontlines will require these highly classified, tactical applications to be subjected to Alphabet's signing APIs.
- Military OpSec cannot rely on the uptime, database, or policy whims of a foreign tech corporation.
- Pinging external servers for app authorization in a high-EW (Electronic Warfare) environment is an unacceptable vector for failure and geolocation tracking.

Alphabet is effectively introducing a kill switch that dictates who gets to deploy tactical software in active warzones. It is time to stop pretending this is about "user safety" and recognize it as an unprecedented enclosure of global hardware sovereignty.
by orwin | 2026-03-04 14:11:57+00:00
Not really, I think it was more that Iran thought the US could control Israel, so they said 'if Israel betray the ceasefire agreement, we will hit your bases'.

The US probably asked Israel to not betray the agreement, Israel as usual betrayed the agreement, said to the US 'we will attack during the negotiations', probably because it was effective the last few times they did, and the US couldn't force them to stop, so they had to preemptively strike.
by incomingpain | 2026-03-04 14:12:09+00:00
From what I read, he was fired.

Which is insane. Obviously he isnt the only lead at alibaba, but qwen as consequence lost many talented people by doing this. It will negatively impact the Qwen team.

Qwen4 is going to flop like Lllama 4.

I hope those who just quit form their own new lab and start building again.
by anarticle | 2026-03-04 14:12:10+00:00
Promotion Driven Development at its finest. There's no good way to fix this without better teams and less Lord of the Flies style management. Servant leadership helps here, but if your team is adversarial in nature there is no escape. A manager that needs an exciting story to get a feather in their hat will take the story every time over "+20 -8000" commit style developers. Your product will suffer accordingly.

A lot of this boils down to promo system being so systematized. I've never heard of people in any other field min/max their promotions as hard along with all of the expert jargon in any other field I've worked in. Packets, peers, comp, other co comps, what your boss thinks of you, what your boss thinks of your peers (nee: competitors), and the inevitable crash out when they don't get the promotion. All part of the bigco experience! I feel like when we systematized comp into ranks Lx, Ly we gave up our leverage a little bit.
by stego-tech | 2026-03-04 14:12:53+00:00
Spitting facts, here.

I built a showback model at a prior org. Re-used shelfware for the POC, did the research on granular costs for storage, compute, real estate, electricity, HVAC maintenance, hardware amortization, the whole deal. Could tell you down to the penny how much a given estate cost on-prem.

Simple. Elegant. $0 in spend to get running in production, modest spend to expand into public cloud (licensing, mainly). Went absolutely nowhere.

Got RIFed. On the way out the door, I hear a whole-ass team did the same thing, using additional budget, with lower confidence results. The biggest difference of all? My model gave you the actual cost in local currency, theirs gave you an imagined score.

The complexity (cost of a team, unnecessary scoring) was rewarded, not the simplicity.
by withinboredom | 2026-03-04 14:13:12+00:00
I once used the analogy of the PM coming to the shop with a car that had a barely running engine and broken windows, and he's only letting me fix the windows.

His response: "I can sell a good looking car and then charge them for a better running engine"...

https://www.youtube.com/watch?v=T4Upf_B9RLQ hits a little too close to home.
Show HN: FiveW – Stay current on AI in 5 minutes a day
by ethanmlam | 2026-03-04 14:13:25+00:00
Hey HN, I'm Ethan. I was spending 2 hours every morning across HN, Twitter, and newsletters trying to keep up with AI for my startup. So over the past few months, my co-founder Thor and I built FiveW to distill the latest AI developments relevant to us, in a 5 minute briefing.

FiveW does three things:

1. Personalized morning briefing -- talk with an agent on onboarding, and get a daily briefing tailored to your interests that you can deep dive on.

2. Curated AI news feed -- surfaces the most important AI stories of the day from 100+ sources, in one place

3. Live market signals -- BTC, gold, oil prices and Polymarket prediction odds alongside the news

Would love to hear what you think. What would you come back for every morning?
by realPubkey | 2026-03-04 14:13:48+00:00
The last days I built the WebMCP plugin for the RxDB database [1]

The goal is to let agents interact with apps through explicit tools instead of DOM scraping or visual navigation. This works nicely because agents can run operations directly on the local-first data the UI already uses.

[1] https://rxdb.info/webmcp.html
by andai | 2026-03-04 14:13:57+00:00
Which size Gemma are you using?

I should clarify that by small I mean in the 3-8B range. I haven't tested the 14-30B ones, my experience is only about the smaller ones.

In my experience, small models are not good for coding (except very basic tasks), they're not good for general knowledge. So the only purpose I could see for them would be, when they're given the information, i.e. summarization or RAG.

But in my summarization experiments, they consistently misunderstood the information given to them. They constantly made basic errors and failed to understand the text.

So having eliminated programming, general knowledge, summarization and (by extension, RAG, because if you can't understand the information, then you can't do RAG either, by definition) -- I have eliminated all the use cases that I had in mind!

That would leave very basic tasks like classification or keywords, but I think there they would be in the awkward middle ground of being disappointing relative to big LLMs for many tasks, and cumbersome relative to small specialized models which can run fast and cheap and be fine tuned.
by bpavuk | 2026-03-04 14:14:10+00:00
so many unknowns...

1. macOS and Windows require installation of Xcode and Visual Studio respectively, and if in Apple's case you kinda can install these tools headlessly and choose to install only the "build tools" package, Microsoft's creature is gonna daze and confuse you with a crap-ton of checkboxes and no easy "just install whatever is minimally needed to compile my code" button, and I don't recall if there is way to install build tools on Windows through terminal.

2. what is going to be distributed? source code itself or actual binaries? and what will the security model of Glaze store be? same as extensions, "everything is open-source and undergoes Raycast's and community review"?

3. Glaze is going to come to Windows and Linux, if we trust the Q&A section at the end. what will Glaze build upon? separate frameworks and languages for each platform or something multi-platform [1] like Tauri or Kotlin Multiplatform? or are you going to copy the Raycast extension model - just run Node, expose some platform integration, and parse React render trees through "Glaze Runtime"? I've been working on a bug in Vicinae [2][3], and I've seen this model in action. it's very hard to make it perform well, but all it takes to achieve native look and feel is to just map React render trees to whatever system component OS offers. (in Vicinae's case, it's Qt. bet that it's done with SwiftUI on macOS and WinUI 3 on Windows.)

[1]: there is a difference between "cross-platform" and "multi-platform". "cross-platform" means "I behave equally across platforms and have no awareness of native look and feel" (e.g. Electron, Unity, Flutter), while "multi-platform" means "I can adapt across platforms to the degree you need" (e.g. C/C++, Rust, KMP)

[2]: https://github.com/vicinaehq/vicinae

[3]: https://github.com/vicinaehq/vicinae/pull/1158
by LollipopYakuza | 2026-03-04 14:14:20+00:00
This is a fallacious argument that has been thoroughly debunked countless times, and frankly it has no place on a platform where we expect a baseline level of digital literacy.
Privacy isn't about hiding crimes, it's about limiting how much power one government has over you.
History has shown stuff that’s totally fine today can be treated like a problem tomorrow. A surveillance system built under a “good” government can be handed to a shady one.
by rayiner | 2026-03-04 14:14:33+00:00
It’s not even remotely similar. We’re talking about countries where (almost) everyone is Muslim and Muslims control the political system, police, etc. Moderate Muslims who can’t reasonably be accused of “Islamophobia” understand that political Islam is a danger and often take extreme measures to keep it in check.

Projecting American racial politics onto other countries is an extremely bad (and bizarrely ethnocentric) way to try to understand how the world works.
by evanjrowley | 2026-03-04 14:14:58+00:00
If I was malware, one of the first things I'd do is check that scratch files directory for secrets.

The default behavior of Notepad++ is a very real security risk. So many system admins and developers will throw passwords and API keys into there and just forget about it. The scratch files are all sitting there unencrypted and with easy to exploit permissions.

Alas, my first thought after seeing TextAdept was that it could serve as a more secure alternative to Notepad++.
by psychoslave | 2026-03-04 14:15:07+00:00
Any system that make rewarding path based on individual contributions as this defect. As opposed to one insuring that the overall result benefits is evenly distributed among all the engaged parties.

The obvious outcome will be that the most skilled pretenders optimizing for their selfish profit narrow view, no matter what the consequences will be for the collectivity on large scale and at long terms.
by iamnothere | 2026-03-04 14:15:08+00:00
This is a bad law and needs to be repealed or struck down on 1A concerns. ASAP.

Repeat after me: you are never, ever, ever going to create an airtight system to force age attestation or verification. Your best opportunity (which will still have many gaps!) is to target only the largest consumer operating systems. This addresses 90% of cases and you have just three companies to deal with.

FOSS will never abide by this, because there will always be people writing and distributing it who are not in your jurisdiction. And, hobby devs will not accept having monetary liability thrust on them. They will move, go underground (pseudonymous), or quit and let devs from other jurisdictions take over.

Noncommercial FOSS must be exempted. Period.
Show HN: VantageKit – a lightweight data room with staging, analytics, & AI Q&A
by xheggs | 2026-03-04 14:15:09+00:00
Hi HN,

I’m the solo developer behind VantageKit. I was a PM for a long time and recently decided to get back into coding. I’ve been building this part-time for just under two months (first commit was Dec 26). I was able to move this fast largely by leaning heavily on Claude Code to accelerate my workflow, and I wanted to share the result here to get your feedback.

THE PROBLEM:
-
Sharing pitch decks, proposals, or due diligence docs is full of friction. You either send PDF attachments (and fly blind on engagement) or you use a tracked data room. But with existing data rooms, version control is a nightmare. If you spot a typo 5 minutes after sending the link, you have to export a new PDF, log in, delete the old file, and upload the new one.

WHAT I BUILT & HOW IT DIFFERENTIATES:
-
VantageKit is a secure deal room wrapper for your documents, designed to sit between lightweight trackers and heavy enterprise Virtual Data Rooms (VDRs).

‣ vs. DocSend / Papermark: While they offer "Spaces" or data rooms, they still treat files as static uploads. VantageKit's core differentiator is a built-in staging workflow with live sync. You connect Google Docs/Slides/Sheets directly. You edit privately in your normal Google workspace, preview the changes in VantageKit's staging environment, and "publish" the update to the live room. No exporting to PDF, no manual re-uploading, and the URL never changes.

‣ vs. Traditional VDRs: Standard VDRs are notoriously clunky, expensive, and overkill for everyday B2B sales or seed rounds. VantageKit provides the necessary security controls (watermarking, domain allow/deny lists, download blocks) but with a modern UI and deep read-tracking.

‣ AI & Intent Layer: It tracks per-page attention and scroll depth. I also added an LLM layer that acts as a deal coach: it powers a viewer Q&A so stakeholders can ask questions directly to the docs, and it calculates an intent score (0-100) based on engagement patterns to help prioritize follow-ups.

‣ Viewer Portal: Standard trackers force recipients to dig through old emails to find specific one-off links. I built a centralized viewer portal (an "Investor Inbox") so stakeholders can securely log in once and access every deal room or document you've ever shared with them in a single dashboard.

TRACTION & ROADMAP:
-
The app is currently handling real data. I have 20+ team (4 paid), and one team is currently relying on it for a large-scale live transaction, which has been an incredible stress test. The roadmap is public here: https://app.vantagekit.com/roadmap

TRY IT OUT:
-
Since HN prefers avoiding sign-up walls, I created a public, read-only demo room so you can see exactly what the recipient experiences without handing over an email: https://share.vantagekit.com/r/vm0gb93g11h8

I would really appreciate your brutal feedback on the UX, the staging architecture, or even the thesis. Also if you’ve used DocSend/Papermark/VDRs, where does it break for you? I’ll be in the comments all day to answer questions.