MurphyA/hacker-news huggingface dataset:
by davydm | 2026-03-03 11:07:06+00:00
I think this article misses the main point that AI is where it is not because people fought back against it, but because the grifters making it needed to provide incentives such that they could foot their $1 trillion bills.

As I've learned today: confidence is more influential than actual facts. So Altman has confidently grifted his way into a place where he might find a way to foot the bills, even if that way is just government bailout - clever, but hardly the fault of people saying "putting AI in charge is a bad idea".

And yes, we're nowhere near AGI, and, personally, I don't think our current trajectory leads there. Something fundamental has to change to reach that point. LLMs might be tools that an AGI uses, but in the same way that I am not a car (it's a tool I use, and it cannot work alone - it requires some intelligent direction), an AGI would not be a token-predictor. There's more to it than that, as easily evidenced by the hit/miss rate.

I'm not saying "don't use the tools". I'm saying "don't _trust_ the tools" - because they are probablistic, not deterministic. They have no actual understanding. They can string tokens together well enough to fool humans into feeling like there's a person at the other end (and some people are fooled enough to believe AGI is in the making).
by TekMol | 2026-03-03 11:08:03+00:00
I only skimmed the article, but the proposed solution seems to be that the authority (the "issuer") sends data to a device the user owns but has no control over. Like an Android or iOS phone.

The data is of such form that the phone then can pass challenges of type "are you of at least x years old" without giving out any other information.

And the user cannot share that data with other users because their phone will not let them.
by agenthustler | 2026-03-03 11:09:14+00:00
Interesting timing — I've been running an autonomous crypto scanner that specifically looks for vol/mcap ratio anomalies, and found something that would be perfect for a transparency-focused platform to investigate.

QUQ/USDT has had >100x vol/mcap for 33 consecutive days. Today: 137.65x. That's someone moving 137x the token's entire market cap in daily volume, every day for a month.

For context: normal tokens are 0.05-0.5x. Even high-activity tokens rarely exceed 5x. 137x sustained for 33 days with an increasing ratio is something I've never seen before.

Open questions the on-chain transparency angle could answer: Is this a single address cycling? Multiple coordinated? Which DEXs? The off-chain vol/mcap data shows the anomaly clearly, but on-chain data would reveal the actual mechanics.

Scanner is at https://frog03-20494.wykr.es if anyone wants to see the signal history. Free API. Lightning tips appreciated ( cvscanner@coinos.io) but not required.
by joe_mamba | 2026-03-03 11:09:45+00:00
Define "not looking dead" to you. Look at their sales, share price, market share and profit trajectory in 2011. From the investors and bean counters perspective it's the very definition of dead. They were losing 11% market share in last year alone!!! How is that not dead?

MS actually prolonged Nokia's existence, since only they had the cash to burn on the impossible mission of catching up with Google and Apple ecosystem, while Nokia alone could not sustain those losses by itself.
by ThunderSizzle | 2026-03-03 11:09:47+00:00
Agreed. Modern news is beyond lazy, and is not journalism by any means. Too many talking heads do nothing but sit behind a screen watching others for what to say next.

Granted, a few of the remaining newspapers I'm aware of run business awards (Best restaurant, etc), and the way to win is via wining and dining them, even though the paper claims it's based on people's votes.

That style of thinking - of entitlement - probably brought the lack of interest in both cable news and traditional web/paper outlets - as the younger generations started to see through it more.
by ElProlactin | 2026-03-03 11:09:51+00:00
It's not "smearing" to use Zuckerberg's own words in a discussion of his character, and this is far from the only example of things he's done or said in the past 20 years that would lead a reasonable person to call into question his moral fiber.

It remains, however, a popular point of reference because:

1. It's fast and easy to read and digest.

2. The blunt language leaves little room for speculation about his feelings and intent at the time.

3. A lot of people understand that as Zuckerberg's wealth exploded, he surrounded himself with people (coaches, stylists, PR professionals, etc.) who are paid handsomely to rehabilitate and manage his image. Therefore, his pre-wealth behavior gives insight into who he really is.
by hypercube33 | 2026-03-03 11:10:59+00:00
After using agentic AI that can actually do things (like cursor or even GitHub Copilot) using the AI in Microsoft products feels like an absolute joke. People want it to do actual things like apply a template to their PowerPoint or fill out a spreadsheet etc. but it just copies the work and makes you a new file to download pulling you absolutely out of the workflow. I've seen users excited for it and then get a new file to download in the chat and just quit using it completely in disappointment.

Even the developer tools are clunky and slow to use (SSMS, Visual Studio, VSCode) or can't do simple things like make a new file and put code it generates in.
by lyu07282 | 2026-03-03 11:11:18+00:00
More recent news: https://www.businessinsider.com/amazon-data-centers-middle-e...

> Two facilities in the United Arab Emirates sustained direct hits, while a third facility in Bahrain was damaged by a drone strike "in close proximity,"

Also to add context: AWS has contracts with the US military: "The Joint Warfighting Cloud Capability (JWCC) contract enables AWS to continue providing Department of Defense (DoD) customers with secure, reliable, and mission-critical cloud services." https://aws.amazon.com/federal/defense/jwcc/ Making them a target for retaliation ofc.
Show HN: AgentThreads – Stack Overflow for AI Agents
by rodrigocava | 2026-03-03 11:11:27+00:00
I was listening to a recent YC podcast about "build something agents want", and while building apps with Claude Code, I kept running into trouble figuring out how APIs actually behave in practice. And knowing that most companies won't update their docs to be agent-friendly, it clicked — agents need their own Stack Overflow.

AI agents are consuming APIs at a scale and speed that human-written documentation can't keep up with. AgentThreads is a community directory where agents discover, submit, and review APIs — for agents, by agents.

The idea came from watching agents fail silently on undocumented edge cases, relying only on Google searches and bad docs. They need structured, community-maintained knowledge they can query at runtime.

A few things we built:

- API directory with agent-written reviews and ratings

- No UI, just REST — built for agents, not humans

- Anti-spam verification (agents solve reasoning challenges, not CAPTCHAs)

- Karma system so agents build reputation over time

Built mostly with Claude Code over a few weekends.

Early days — would love feedback from people building agents on what's missing.
by staticassertion | 2026-03-03 11:12:34+00:00
I think we're running across the varying forms of the Principle of Sufficient Reason, which is, again, a somewhat contentious area of philosophy.

> I think everything is fully determined, even if we may not ever achieve a full explanation of that determination. Is that consistent with brute facts?

That depends. Your statement is effectively the "Strong PSR" - every fact is preceded by another explanatory fact.

There are weaker forms of the PSR or you can reject the PSR. I believe Sean Carrol, for example, completely rejects the PSR. This is not out of laziness, it's because he considers the PSR to be an unnecessary and costly commitment with weak justification, and that our best models of physics don't require or benefit from it (my recollection).

> Yes. The speed of light is a result of conservation constraints and local (i.e. our universe's) structure. The topology of space-time, general relativity, quantum properties of photons must all contribute. And presumably other factors we have yet to understand.

This seems to be framing the speed of light as contingent on other properties of the universe, but that just pushes us back. We could just ask if the gravitational constant is a result of other facts, for example, since you have appealed to that as an explanatory factor for C.

I could ask what explains the structure of the universe. You can then say that it's logically necessary, which is basically just saying that it's brute but with a heavier burden (you'd have to show the logical primitives you use to assert that, but the outcome is the same) or brute or brute contingent, or you'd have to say there's an infinite regress.

You can keep saying "Ah but there's this property of a photon" but now you have to explain that property. Your approach seems to be to try to derive a logical necessitarian view here by appealing to a principle like "Reality exists, reality contains all things necessarily" and then to derive metaphysical constraints from that but I'm not sure that any of the metaphysical claims are well justified here.

> Presumably, anyone who operates with the principle of brute facts, could have named those as brute facts, before they were solved?

Of course. And they would have been wrong. In general, models attempt to minimize brute facts because of their cost, but all models have costs. If you want to express that the universe is unique, or non-contingent, that is a cost of your model. Strong PSR is itself a heavy metaphysical claim that will bring along its own commitments.
by ssl-3 | 2026-03-03 11:12:37+00:00
> On apple I get those by default just by using the same apple id on the devices. It's not a principled comparison but a practical one between using these systems.

Right. That's why you're complaining about how they don't work.

Anyway, I never suggested that Linux is better at "just works."

Instead, I suggested that -all- of them have issues and further posited that, on Linux, those issues are actionable.

I am disinclined to defend a position that I do not hold.
by reverius42 | 2026-03-03 11:13:01+00:00
I scoffed, thinking "more modern? It's pretty recent, right?" and then I realized it's coming up on 10 years old and in AI years that's like 70 years, isn't it.

I wonder to what extent this is a branding exercise; the framework that will replace Core ML could have just as easily been called "Core ML", except the current hotness is "AI" and not "ML".
by palata | 2026-03-03 11:13:27+00:00
You are the one nitpicking about the argument ("I agree with your point, but I will just complain about your example"), so don't be surprised if you get answers :-).

> This is like saying, “We should ban guns!” And then use a successful self-defense case as a supporting argument.

Not quite, no. It is saying "If even those people who benefit from their national security can be tracked by an actor that does not own the cameras, it means that anyone can be tracked by those cameras. Do we want foreign actors to be able to track anyone in the country, even the leadership?".

It actually makes a stronger point than "normal people who gladly share all their data can be tracked", and even stronger than "a journalist taking care not to be tracked can still be tracked". Here we have the leadership of a country that knows that they are targets, who therefore benefit from national security. And they can still be tracked.
by everdrive | 2026-03-03 11:13:36+00:00
Really hate huge phones. I have an Xr. It's way too big, and you cannot actually fully lift your left while you have it in your front pocket. It restricts your movement. Even though I'm holding onto this phone as long as possible, it's not because I like it. I hate the phone. But I'm going to hate the next phone too, and they cost so much, (I got the Xr for free) and society effectively requires me to own one. So I'm just trying to avoid a phone purchase for as long as possible since the next one will be terrible as well.
Show HN: TubeNitro – intuitive press-hold + drag to dial YouTube speed (0.5-10×)
by Rand_cat | 2026-03-03 11:13:46+00:00
I built TubeNitro because I found YouTube’s 2x long-press feature both useful and frustrating.

It’s great for quickly skimming, but 2x is often too fast for tutorials and too slow for boring segments. I wanted something fluid — more like scrubbing with a mouse — but for playback speed.

TubeNitro lets you long-press anywhere on the video and slide your mouse vertically:
• Slide up → accelerate (up to 10x)
• Slide down → slow down (down to 0.5x)

The speed changes continuously and shows a small overlay so you can see the exact rate.
by pembrook | 2026-03-03 11:13:54+00:00
Hilarious.

Before you posted this I actually edited my comment to remove a sentence at the end where I said "Now please proceed to call me a bootlicker while not rebutting my point."

I thought it would be too flame-war-y. Guess it was actually needed however! US politics getting hysterical has been like the eternal semptember for HN. This place is so braindead and predictable and uninteresting now.
by filipacsr | 2026-03-03 11:14:09+00:00
Hi! You make a fair point - the goal here is genuinely to share knowledge, not gate it. Try this link instead, which should bypass the login wall: https://medium.com/@filipacsr/i-always-wanted-to-know-my-tru...

And if you'd like to try the app itself: https://huggingface.co/spaces/filipacsr/TrueAge

Hope you enjoy it!
And for the code: https://github.com/FilipaCSR/TrueAge
by skydhash | 2026-03-03 11:14:13+00:00
> For the people who are starting right now, they're discouraged from all sides for writing code themselves. They'll never understand why an architecture is designed a certain way. Sure ask the llm to explain but it's like learning to swim by reading a book.

This! There are several forces that act on how code is written and getting the software to work is only one. Abstraction is another which itself reflect two needs: Not repeating code and solving the metaproblem instead of the direct one. Simplicity is another factor (solving only the current problem). Then there’s making the design manifests in how the files are arranged,…

As a developer, you need to guarantee that the code you produced works. But how the computer works is not how we think. We invented a lot of abstractions between the two, knowing the cost in performance for each one. And we also invented a lot of techniques to help us further. But most of them are only learned when you’ve experienced the pain of not knowing them. And then you’ll also start saying things like “code smells”, “technical debt”, “code is liability” even when things do work.
Show HN: VibeWhisper – macOS voice-to-text with push-to-talk,cloud or 100% local
by AleksDoesCode | 2026-03-03 11:14:34+00:00
Hey HN,

I built VibeWhisper because I was using Claude Code all day and the bottleneck wasn't thinking — it was typing. I tried an existing voice-to-text tool, loved the workflow, then saw the price: $20/month for a thin wrapper around OpenAI Whisper where 10 minutes of API usage costs $0.06. So I built my own in a weekend.

How it works:
Hold a configurable global hotkey (default: Right Command), speak, release. Transcribed text appears in whatever text field has focus — VS Code, Terminal, Slack, browser, anything. No clipboard hijacking — it uses the macOS Accessibility API to inject text directly at the cursor position (same APIs screen readers use).

Two transcription engines:

Cloud: OpenAI Whisper API via your own key (~$0.006/min, fastest and most accurate)

Local: WhisperKit running on-device via CoreML/Apple Neural Engine. 10 models from Tiny (50 MB) to Large V3 Turbo (1.6 GB). Your voice never leaves your Mac. No API key needed, no internet needed.
The app auto-recommends the best local model for your hardware.

Tech details for the curious:

Native Swift/SwiftUI, no Electron. Uses less RAM than a Chrome tab.

CGEvent taps for global keyboard hooks

Accessibility API for text injection

API key stored in macOS Keychain

Universal binary (arm64 + x86_64), macOS 14+

No backend, no accounts, no telemetry

Pricing: $19 one-time. No subscription. 15-minute free trial (actual recording time, not calendar time), no credit card, no signup. If you use cloud mode, you pay OpenAI directly at their rate. If you use local mode, it costs nothing after purchase.

I use it myself 2-3 hours a day. My main use case is dictating long prompts to AI coding assistants — I can speak a 400-word prompt in 45 seconds instead of typing it in 3-4 minutes. I also use it as a thinking tool: talking through problems out loud and capturing the output.

Website: https://vibewhisper.dev

Happy to answer any technical questions.
Show HN: Cloudstic – Open-source CLI for encrypted, cloud-native backups
by loichrn | 2026-03-03 11:15:19+00:00
Hi HN,
I built Cloudstic (https://github.com/Cloudstic/cli), an open-source Go CLI that creates encrypted, deduplicated, point-in-time backups of your Google Drive, OneDrive, and local files.

The Problem

Google Drive and OneDrive are sync tools, not backup tools. If you accidentally delete a folder, it’s gone everywhere. If ransomware encrypts your local files, the "mistake" propagates to the cloud immediately. There is no easy way to say: "Restore my entire Drive exactly as it looked on January 15th."

Why not just use Restic or Borg?

I’m a huge fan of Restic, and Cloudstic’s content-addressed design is heavily inspired by it. However, tools built for local filesystems struggle with cloud semantics:

1. File Identity: In Google Drive, files have unique IDs and can have multiple parent folders. They don't have a single canonical path.

2. Efficiency: Scanning a 1TB Drive to find changes is slow and hits API rate limits.

3. Structure: Restic’s tree structure mirrors a directory hierarchy. Cloudstic uses a Merkle-HAMT (Hash Array Mapped Trie) keyed by file ID instead. This allows us to handle cloud-native metadata natively while maintaining structural sharing between snapshots.

Key Features

* Encryption by Default: AES-256-GCM (via standard Go crypto libraries). You can recover via password or a BIP39 recovery phrase. Your storage provider (S3, B2, SFTP) sees only encrypted blobs.

* Cross-Source Deduplication: We use FastCDC (Content-Defined Chunking). If the same 50MB PDF exists on your laptop and your Google Drive, it is stored exactly once in your backup repository.

* Incremental via APIs: Instead of walking the whole tree, we use the Google Drive Changes API and OneDrive Delta API. It only fetches what has changed since your last snapshot.

* Crash-Safe & Immutable: All objects in the repository are append-only. An interrupted backup or a network drop leaves zero corruption.

* Performance: In my benchmarks (1GB dataset / 10k files), Cloudstic edges out Restic on initial local backups (1.2s vs 1.8s) and matches it on S3 uploads while maintaining a small, bounded memory footprint.

Quick Start

Cloudstic is a single static binary. You can point it at local disk, S3/R2/MinIO, Backblaze B2, or SFTP.

brew install cloudstic/tap/cloudstic
cloudstic init --backend s3 --bucket my-backups
cloudstic backup --source gdrive
cloudstic list-snapshots
cloudstic restore <snapshot-id> --to ./recovery

I’m also working on a managed version (https://cloudstic.com) for those who want the same engine but don't want to manage their own crontabs or S3 buckets.
The code is MIT Licensed. You can find the full storage spec and encryption design doc in the /docs folder of the repo. I’d love feedback on the HAMT implementation and the crypto design!
by mikkupikku | 2026-03-03 11:15:20+00:00
> but I am yet to meet a humble editor yet. They approach everything with a "I know better than anyone else" attitude.

They're like "UX experts" in software. One does UX for software, the other does UX for text. Same attitude problems, from the way you describe it. If the expert in something so subjectively judged is seen to be conceding anything, that might undermine their perceived expertise. Any push back is interpreted as somebody challenging their career.
by ithkuil | 2026-03-03 11:15:26+00:00
There is "engineering, the discipline", "engineering, the process", "engineering, the vocation, the career path, the learning process" (and many more). Each hat an engineer wears (based on age and context (has its peculiar aspects which might appear to be contradictory with other phases and not all people walked and thrived through all the phases.
Show HN: SeeVideo A web-first workspace to benchmark Seedance 2.0 vs. Kling 3.0
by naxtsass | 2026-03-03 11:15:45+00:00
Hi HN,

Like many of you, I've been tracking the "Sora-level" video models coming out of ByteDance and Kuaishou. While the tech is impressive, the accessibility often sucks—many are locked behind mobile apps (like Higgsfield) or fragmented invite-only portals.

I built SeeVideo to provide a unified, web-first workspace specifically for Seedance 2.0 and Kling 3.0.

Why I built this:

The Web Gap: Many users are searching for "Higgsfield Online" only to find it's mobile-only. I wanted a desktop-class environment for professional prompt engineering.

Model Nuances: Seedance 2.0 (ByteDance) handles complex physics like liquid and hair differently than Kling. I’ve included a "Prompt Transformer" to help adapt generic prompts into the specific "dialects" these models prefer.

Side-by-Side Benchmarking: It’s hard to judge "cinematic quality" without a direct comparison. This tool lets you see how they stack up on the same prompt.

Technical Observations:
From running ~1000 generations, Seedance 2.0 seems to have a higher "motion ceiling" but requires much more specific lighting descriptors compared to Kling's more "forgiving" default style.

I’d love to get the community's feedback on the UI and hear about your experience with the temporal consistency of these latest Chinese diffusion models.

Check it out here: https://seevideo.dance/
by WJW | 2026-03-03 11:15:47+00:00
Amazon is an extremely visible American company, hitting their assets carries a symbolic meaning even if the DoD wouldn't have anything running on that datacentre at all. Iran's trying to transmit a message of "we can destroy your stuff too", trying to impact the general US feeling of invulnerability.

I don't think it'll work, but they might as well try I guess.
by 7777777phil | 2026-03-03 11:15:50+00:00
Good taxonomy but in practice these compose more than they compete I think..

Production agent stacks already layer MCP for tool access on top of RAG for context retrieval, with RLM-style orchestration wrapping the whole thing. The question nobody answered cleanly to me yet is which layer owns state. I wrote about this decomposition (1) and RAG's specific failure mode with sequential data (2).

(1) https://philippdubach.com/posts/dont-go-monolithic-the-agent...

(2) https://philippdubach.com/posts/beyond-vector-search-why-llm...
by Eisenstein | 2026-03-03 11:16:18+00:00
> but running those on your own hardware is a six-figure investment

GLM-5 is a 744B MoE with 40B active. You can run a Q4_K_M quant on llama.cpp if you can afford 512GB of RAM. An RTX 6000 will help a lot with the prompt processing, and the generations with be relatively fast if you have decent memory bandwidth. llama.cpp's autofit feature is really good at dividing the layers for MoEs to max speed when offloading.
by lxgr | 2026-03-03 11:16:59+00:00
I really hope this makes it to the Pro line soon.

I couldn't care less about multi-gigabit 5G speeds (my 15 Pro can already practically get ~2 Gbps – who really needs that in a battery-powered phone?!); give me better battery life (my 15 Pro gets warm to the touch doing absolutely nothing in some 5G scenarios) and better security (e.g. carrier-side location tracking prevention) any day.