Show HN: What 180k words look like as a temporal knowledge graph (Oz series) https://ift.tt/uEeJAPN

Show HN: What 180k words look like as a temporal knowledge graph (Oz series) The graph is free to explore and requires no registration. SynapTale builds a model of a story as a temporal graph made up of nodes (entities) and edges (their actions and relationships). The graph is not a visualization of the wiki. The wiki, timelines, relationship histories, and analytics are projections of the graph. The current demo contains 232 entities, 1,852 edges, and a snapshot of the story’s state at every chapter. By chapter 100, it still remembers a promise made in chapter 8 and turns the story into a set of source-verifiable facts. The most interesting things can be found in the graph itself and in the Analytics tab. A few things I found: 1. The character with the highest kill count is the Tin Woodman—the same character who cries over a beetle he accidentally crushed. Dorothy comes second, with three killing events. 2. Dorothy never deceives anyone during the first 100 chapters of the series. 3. The Scarecrow’s debt to the stork has remained active for 92 chapters, starting in chapter 8. 4. The Cowardly Lion ranks third by number of threats. 5. The first 100 chapters contain 60 secrets and 254 dialogue events. Technical details 1. Five different multi-agent pipelines combining LLMs and NLP: a prescan, ontology construction, chapter-by-chapter graph extraction, retrospective validation over spans of dozens of chapters, and a linguistic prescan for speech profiles and linguistic edges. 2. A living story needs a living graph. It has to account for time, because entities and the relationships between them evolve. A simple is_active field is not enough. I ended up with three types of edges: event: an instantaneous action; identity: a fact; state: a persistent action whose termination requires justification and a supporting quote from the text. The vast majority of edges are events and end in the same chapter in which they began. This allows the system to scale well, since only a minority of state and identity edges remain continuously active. 3. Ontology. You cannot simply ask an LLM to extract entities and relationships into a graph. With every chapter, even the smartest model will keep inventing unimportant fields, creating new aliases for existing fields, and representing the same fields inconsistently. Before extracting the graph, the system therefore performs an ontology scan across the entire story. It captures story-specific entity and edge types, along with their fields and descriptions. 4. Epistemics. Events are only one part of a story. It is also important to understand how information is distributed, which is difficult to represent using event edges alone. I addressed this by introducing a new node type: epistemic nodes, which capture different entities’ perspectives on the same fact. Subtle hints can still be missed, the system is not yet perfect in this area. https://ift.tt/1EM49dm July 25, 2026 at 11:18PM

Show HN: Nostalgia – A shareable Windows 98 desktop builder https://ift.tt/kyVdUiG

Show HN: Nostalgia – A shareable Windows 98 desktop builder https://ift.tt/YMdHuv7 July 25, 2026 at 05:57AM

Show HN: WhipDesk – Control your full dev machine from your phone https://ift.tt/OqkjJB3

Show HN: WhipDesk – Control your full dev machine from your phone Hi HN, I built WhipDesk, an open-source, mobile-friendly remote desktop tool for controlling your full development machine and managing AI coding agents from your phone’s browser. It gives you access to the entire desktop while also adding workflows for monitoring and managing tools such as Claude Code, Codex, GitHub Copilot, and others The two questions I hear most are: How is it secured, and how is it different from existing tools? Security Following the modern approach taken by open-source remote access tools such as RustDesk, WhipDesk is fully open source, so its client, agent, protocol, and security model can be inspected rather than trusted as a black box. Local connections can run entirely within your network without an account. Remote connections use end-to-end encrypted WebRTC. Most connections are peer-to-peer; when a TURN relay is required, it only forwards encrypted traffic. Each connection also requires the machine’s access PIN as an additional security layer. More details are available in the GitHub README. Why not Claude Code, Codex, or other agent remote-control tools? Those tools are useful for interacting with the agent session, but sometimes I need access to the rest of the machine: the IDE, browser preview, emulator, logs, desktop applications, or the UI the agent just changed. WhipDesk gives you access to the full development environment directly from your mobile browser, regardless of which coding agent is running. That is why I built it: I did not want to be limited to a single agent interface. Why not TeamViewer, RDP, or RustDesk? Traditional remote desktop tools work, but they are usually designed for controlling one large desktop from another computer. On a phone, text can become difficult to read, and they do not include workflows specifically designed for monitoring and managing coding agents. WhipDesk is designed specifically for mobile browsers. It can stream only the selected mobile viewport, keeping text crystal clear when zoomed in and allowing it to work well on lower-bandwidth connections. I built it because I often need to step away from my desk while agents are still working. I use it to answer prompts, inspect UI changes, review progress, and course-correct from my phone. Source and installation: https://ift.tt/xE5F8DN npm install -g whipdesk I’d especially appreciate feedback on your first impression. Building a tool that requires this level of user trust has been challenging, and I would love to improve it based on honest feedback. https://ift.tt/xE5F8DN July 24, 2026 at 11:49PM

Show HN: Forje Studio – data-driven design and motion, entirely client-side https://ift.tt/Th7N3i4

Show HN: Forje Studio – data-driven design and motion, entirely client-side https://ift.tt/qPi2bMf July 24, 2026 at 05:36AM

Show HN: I built a native macOS terminal with Git integration in 5 days https://ift.tt/42aLA1B

Show HN: I built a native macOS terminal with Git integration in 5 days https://kero.sh/ July 24, 2026 at 02:51AM

Show HN: I built a local Node.js conduit for the BorgIOS network https://ift.tt/IaWoA9P

Show HN: I built a local Node.js conduit for the BorgIOS network https://ift.tt/iPHdREt July 24, 2026 at 12:12AM

Show HN: I created a catalog with embeds for your projects https://ift.tt/8xdQrzO

Show HN: I created a catalog with embeds for your projects Hello HN! Today I would like to introduce my new open-source project called EmbedCatalog. It's free and you can add yours and get interesting and practical embeds there. So far, not many embeds have been done, only three, but in the future I will create more. I would also like to make an editor, but I don’t know how to implement it to make it look better. You may ask “how is this project different from others?” In fact, I wanted to combine the two ideas of a list and the usual README images into one. It turned out how it turned out, but the idea seems like a good one I would appreciate your feedback ^ ^ https://ift.tt/xLn2YvN July 23, 2026 at 08:43AM