Recent submissions

Comment · 1 month ago
I created an ai cross-stitch pattern generating tool: https://stitchwink.com/admin

If you try to use image generation directly, you don't get real patterns. StitchWink makes real patterns that you can also edit manually or through text/images with AI.

Comment · 1 month ago
Comment · 1 month ago
Comment · 3 months ago
It's absolutely wrong. We also have: Alexander Fleming, Howard Florey & Ernst Chain who contributed significantly to antibiotics.

You could even add politicians. How much wealth did FDR create?

Comment · 3 months ago
It sounds like they gave you a feature for free you didn't want, and now are trying to charge for it. Very much a dark pattern.
Comment · 3 months ago
Have you tried creating skills for your agents to follow your patterns?
Comment · 3 months ago
Will organizations want to control their own proxy or use OpenRouter?
Comment · 4 months ago
I'm working on Ito.ai : https://www.ito.ai/

It's Agentic QA + auto-provisioning sandboxes. Makes it plug and play to do code reviews that actually run your code instead of looking at it really hard. B/c the agents control all of the environment (ie running all of the services), it's able to collect runtime evidence about pretty much everything.

A couple open source examples: (Excalidraw) https://app.ito.ai/share/d1cb1475-fbe5-4c71-901b-409ba2aa6d6... & (n8n) https://app.ito.ai/share/bb7d73aa-fd08-482d-9938-87938e2a232...

Comment · 7 months ago
If the question is storage, bitcoin itself provides a perfectly good mechanism. idk the exact costs but it'd be in the range of ~$0.45 to store a commitment. That's cheap enough to enable good users with small numbers of keys but also expensive enough to prevent spam. It's kind of the whole point of blockchains.

As for verification being expensive, it sounds like you don't know the actual costs. It's basically a hash. Finding the pre-image of a hash is very expensive to the point of being impossible. Verifying a pre-image + hash function = a hash is extremely cheap. That's the whole point of 1-way functions. Bitcoin itself is at ~1000 EH/s (exahashes per second)

Again, this isn't a technical problem. It's a coordination problem.

Comment · 7 months ago
I don't think you're understanding how cryptography works. A commitment is basically a hash that is both binding and hiding. In this example it's probably easiest to think of it as a hash. So you hash your post-quantum public key (something like falcon-512) and then sign that hash with your actual bitcoin private key (ecdsa, discrete-log, not quantum safe) and then publish that message to the bitcoin network. Then quantum happens at some point and bitcoin needs to migrate but where do funds go? Well you reveal the post-quantum public key and then you can prove that funds from the ecdsa key should go there. From a technical perspective, this is a complete and fool proof system. DoSing isn't really a concern if you publish to the actual bitcoin network and it's impossible for someone to use up the key space (2^108 combinations at least).

The reason this is a dumb idea is because coordination and timing. When does the cutover happen? Who decides which transactions no longer count as they were "broken" b/c of quantum computing? The idea is broken but not from technical fundamentals.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton