graphpilled

6 ms·

1. 1.▲
   by graphpilled 7mo ago

   Hi HN, I've been obsessed with the idea of visual ML model building since mid-2024. I experimented with a bunch of approaches: Three.js to PyTorch, a Three.js to OCaml compiler with a custom Lisp-inspired IR targeting CUDA. None of the
2. 2.▲
   Show HN: Neural network compiler targeting WebGPU – runs in browser(graphpilled.github.io)

   2 points by graphpilled 7mo ago|1 comments
3. 3.▲
   by graphpilled 7mo ago

   That's a cool setup. An API that returns the branching structure as JSON would fit your use case well—you'd feed in a prompt, get back the graph, and integrate it into your knowledge tree however you want. I'll keep this in m
4. 4.▲
   by graphpilled 7mo ago

   That's wild. Hard to say for sure—could be that your scenario's structure pattern-matched something in Qwen's training data, or it picked up on implicit episodic cues in your writing. The base model has seen a lot of serializ
5. 5.▲
   by graphpilled 7mo ago

   Interesting use case. I don't have a public API yet, but it's something I'd consider if there's demand. What kind of integration are you imagining—feeding prompts in and getting branches back, or something else?
6. 6.▲
   by graphpilled 7mo ago

   The Oblique Strategies comparison is exactly the vibe I was going for—generative constraints that open up possibilities rather than closing them down. Node editing is the top priority right now. You're right that the loop isn't co
7. 7.▲
   by graphpilled 7mo ago

   Good point—you're right, there should be a way to mark a branch as an endpoint instead of forcing more branches. Adding that to the list. Thanks.
8. 8.▲
   by graphpilled 7mo ago

   Not yet, but both are on the roadmap. Manual node editing is the next priority—letting you tweak branches or add your own directions. The script evaluation idea is interesting—you're not the first to suggest it. The extraction pipeline
9. 9.▲
   by graphpilled 7mo ago

   Thanks for flagging that—the node overlap issue is a known bug when the graph gets dense. I'm working on better auto-layout. Appreciate the report.
10. 10.▲
    by graphpilled 7mo ago

    There's a demo on the landing page that walks through it. Basically you input any idea—no matter how vague—and the system generates branching directions you could take it. You explore the branches, and when you're satisfied you ca
11. 11.▲
    by graphpilled 7mo ago

    Thanks! Here's the full list: 2001: A Space Odyssey, 8½, Aguirre the Wrath of God, Ali: Fear Eats the Soul, All That Heaven Allows, Apocalypse Now, Ashes and Diamonds, A Woman Under the Influence, Barry Lyndon, Bicycle Thieves, Breathl
12. 12.▲
    Show HN: Fine-tuned Qwen2.5-7B on 100 films for probabilistic story graphs(cinegraphs.ai)

    101 points by graphpilled 7mo ago|20 comments
13. 13.▲
    by graphpilled 8mo ago

    Good point! Here's a quick demo showing how it works: https://www.youtube.com/watch?v=b66ZHznBvEM
14. 14.▲
    by graphpilled 8mo ago

    Hi HN, I'm a computer systems engineering student in Mexico who switched from film school. I built CineGraphs because my filmmaker friends and I kept hitting the same wall—we'd have a vague idea for a film but no structured way to