Show HN: JeffTube https://ift.tt/irswZlP

Show HN: JeffTube https://jmail.world/jefftube February 16, 2026 at 01:09AM

Show HN: GPU Perpetual Futures Prototype https://ift.tt/1vL4tig

Show HN: GPU Perpetual Futures Prototype GPU rental prices are super volatile but there's no derivatives market to hedge. I built a perpetual futures platform to see what this could look like. The idea is airlines hedge jet fuel, starbucks hedges coffee beans - as GPU compute becomes critical infrastructure the same hedging tools should exist. Not sure if anyone actually needs this but it was interesting to build. How it works: - Pulls live H200 spot prices from Vast.ai every 15s into a tradeable index - Full perp mechanics: funding rates, mark price calc, real-time P&L - Event-driven Rust backend with supervisor pattern and circuit breakers - Next.js frontend with TradingView charts, real-time WebSocket updates What's real vs simulated: - Real: Index construction, funding rate engine, forward curve, state persistence - Simulated: Order book depth and trade matching (its a single-client demo) The backend is the part I'm most proud of - isolated tasks coordinated by a supervisor, each has it's own state machine so if one component fails it doesn't take down the others. Tried to build it with production patterns in mind even though its just a demo. Also made a 15-page derivatives pricing doc that covers the economic model and hedging scenarios. Basically: rental prices = f(CAPEX, utilization, depreciation) so futures pricing reveals market expectations about GPU supply/demand. GitHub: https://ift.tt/zCIVfsx Would love feedback on the architecture or if the market mechanics actually make sense. First time building something like this. https://ift.tt/zCIVfsx February 15, 2026 at 04:21PM

Show HN: Katipo is a minimal alternative internet with a Vulkan based browser https://ift.tt/4I6kT1j

Show HN: Katipo is a minimal alternative internet with a Vulkan based browser I’m nervous, announcing this, as it isn’t ready to ship out to the general public yet, and I haven’t had any feedback at all from anyone, I’m out on my own here. I think this concept itself is kind of dismissed outright a lot too, and I understand why, I wouldn’t believe me either actually. But, I do believe this is very much worth your time to check out, I am not aware of anything else very much like it. I won’t repeat what is already written on the github README here, but some info: I am a successful semi-retired solo game developer, I have been making my own bespoke game engines since 2003 for all of my games across a number of platforms and languages. Last year, I ripped out the engine of my latest game, and stripped it back with the goal to start a new project, as I have done a number of times before. But this time, I decided to ditch lua and make my own programming language, and that was sort of the tipping point. Once I thought about multiplayer, and realized I wanted a general purpose network that didn't exist, I was on my way down this extremely deep rabbit hole. I want to just make a few things clear, then I hope that some of you might have some questions or feedback. - I'm disillusioned by capitalism and the AI transition, and that influences my motives - I have made all of this open source and free not because I am overly altruistic, but because it is the only way something like this can succeed - I don’t think it can or should replace the internet, I see it as a cycleway alternative to the internet highway, they have different purposes - I have no real desire to run an open source project or lead anyone, I mostly just want software that works for me and my family and friends. I love coding and I like to make nice things and share them. - There is still a lot to do, I'm very excited about messaging and the whole client-side data thing in particular, but for now there are only a few weeks of work to go until a bare bones browser will be functional enough to release and ship. You can have a play and build it all yourself though right now, host sites, and build apps. https://ift.tt/1evLfZ2 February 15, 2026 at 11:57PM

Show HN: Tufte Editor – Local Markdown Editor with Tufte CSS Live Preview https://ift.tt/mH593LM

Show HN: Tufte Editor – Local Markdown Editor with Tufte CSS Live Preview A split-pane Markdown editor that renders live preview with Tufte CSS. Sidenotes, margin notes, epigraphs, full-width figures, and BibTeX citations with autocomplete — all in standard Markdown extensions. Documents are .md files on disk. Images are regular files. Exports to standalone HTML with Tufte CSS baked in — my use case is writing essays and uploading them directly to my personal site. Zero dependencies, no npm install, no accounts, no build step. Just `node server.js`. ~7 files total. Full disclosure in the README: I'm a researcher, not a JS developer, and the code was AI-generated. Contributions and code review welcome. https://ift.tt/izTJvIY February 15, 2026 at 05:22AM

Show HN: PlanOpticon – Extract structured knowledge from video recordings https://ift.tt/V76aMvQ

Show HN: PlanOpticon – Extract structured knowledge from video recordings We built PlanOpticon to solve a problem we kept hitting: hours of recorded meetings, training sessions, and presentations that nobody rewatches. It extracts structured knowledge from video — transcripts, diagrams, action items, key points, and a knowledge graph — into browsable outputs (Markdown, HTML, PDF). How it works: - Extracts frames using change detection (not just every Nth frame), with periodic capture for slow-evolving content like screen shares - Filters out webcam/people-only frames automatically via face detection - Transcribes audio (OpenAI Whisper API or local Whisper — no API needed) - Sends frames to vision models to identify and recreate diagrams as Mermaid code - Builds a knowledge graph (entities + relationships) from the transcript - Extracts key points, action items, and cross-references between visual and spoken content - Generates a structured report with everything linked together Supports OpenAI, Anthropic, and Gemini as providers — auto-discovers available models and routes each task to the best one. Checkpoint/resume so long analyses survive failures. pip install planopticon planopticon analyze -i meeting.mp4 -o ./output Also supports batch processing of entire folders and pulling videos from Google Drive or Dropbox. Example: We ran it on a 90-minute training session: 122 frames extracted (from thousands of candidates), 6 diagrams recreated, full transcript with speaker diarization, 540-node knowledge graph, and a comprehensive report — all in about 25 minutes. Python 3.10+, MIT licensed. Docs at https://planopticon.dev . https://ift.tt/1AOpxy9 February 15, 2026 at 03:10AM

Show HN: Git Navigator – Use Git Without Learning Git https://ift.tt/a3ivb7D

Show HN: Git Navigator – Use Git Without Learning Git Hey HN, I built a VS Code extension that lets you do Git things without memorizing Git commands. You know what you want to do, move this commit over there, undo that thing you just did, split this big commit into two smaller ones. Git Navigator lets you just... do that. Drag a commit to rebase it. Cherry-pick (copy) it onto another branch. Click to stage specific lines. The visual canvas shows you what's happening, so you're not guessing what `git rebase -i HEAD~3` actually means. The inspiration was Sapling's Interactive Smartlog, which I used heavily at Meta. I wanted that same experience but built specifically for Git. A few feature callouts: - Worktrees — create, switch, and delete linked worktrees from the graph. All actions are worktree-aware so you're always working in the right checkout. - Stacked workflows — first-class stack mode if you're into stacked diffs, but totally optional. Conflict resolution — block-level choices instead of hunting through `<<<<<<<` markers. Works in VS Code, Cursor, and Antigravity. Just needs a Git repo. Site: https://gitnav.xyz VSCode Marketplace: https://marketplace.visualstudio.com/items?itemName=binhongl... Open VSX: https://open-vsx.org/extension/binhonglee/git-navigator https://gitnav.xyz February 14, 2026 at 11:43PM

Show HN: Verify-before-release x402 gateway for AI agent transactions https://ift.tt/uKWxIRG

Show HN: Verify-before-release x402 gateway for AI agent transactions Hey HN, I built Settld because I kept running into the same problem: AI agents can call APIs, pay for services, and hire other agents - but there's no way to prove the work was actually done before the money moves. The problem in one sentence: x402 tells you "payment was sent". Settld tells you "the work was worth paying for". What it does Settld sits between your agent and the APIs/agents it pays. It: 1. Intercepts HTTP 402 (Payment Required) responses 2. Creates an escrow hold instead of paying immediately 3. Collects evidence that the work was completed 4. Runs deterministic verification (same evidence + same terms = same payout, every time) 5. Releases payment only after verification passes 6. Issues a cryptographically verifiable receipt If verification fails or the work is disputed, the hold is refunded. The agent gets a receipt either way - a permanent, auditable record of what happened. Why this matters now We're at a weird inflection point. Coinbase shipped x402 (50M+ transactions). Google shipped A2A. Anthropic shipped MCP. Agents can discover each other, communicate, and pay each other. But nobody built the layer that answers: "was the work actually done correctly, and how much should the payout be?" That's the gap. Right now, every agent-to-agent transaction is either "trust and hope" or "don't transact." Neither scales. The x402 gateway (the fastest way to try it) We ship a drop-in reverse proxy that you put in front of any API: docker run -e UPSTREAM_URL= https://your-api.com \ -e SETTLD_API_URL= https://api.settld.dev \ -e SETTLD_API_KEY=sk_... \ -p 8402:8402 \ settld/x402-gateway Everything flows through normally - except 402 responses get intercepted, escrowed, verified, and settled. Your agent gets a receipt with a hash-chained proof of what happened. What's under the hood The settlement kernel is the interesting part (and where we spent most of our time): - Deterministic policy evaluation - machine-readable agreements with release rates based on verification status (green/amber/red). No ambiguity. - Hash-chained event log - every event in a settlement is chained with Ed25519 signatures. Tamper-evident, offline-verifiable. - Escrow with holdback windows - configurable holdback basis points + dispute windows. Funds auto-release if unchallenged. - Dispute → arbitration → verdict → adjustment - full dispute resolution pipeline, not just "flag for human review." - Append-only reputation events - every settlement produces a reputation event (approved, rejected, disputed, etc.). Agents build verifiable economic track records. - Compositional settlement - agents can delegate work to sub-agents with linked agreements. If a downstream agent fails, refunds cascade deterministically back up the chain. The whole protocol is spec'd with JSON schemas, conformance vectors, and a portable oracle: https://ift.tt/0YPr21W... What this is NOT - Not a payment processor - we don't move money. We decide "if" and "how much" money should move, then your existing rails (Stripe, x402, wire) execute it. - Not a blockchain - deterministic receipts and hash chains, but no consensus mechanism or token. Just cryptographic proofs. - Not an agent framework - we don't care if you use LangChain, CrewAI, AutoGen, or raw API calls. We're a protocol layer. Tech stack Node.js, PostgreSQL (or in-memory for dev), Ed25519 signatures, SHA-256 hashing, RFC 8785 canonical JSON. ~107 core modules, 494 tests passing. What I want from HN Honest feedback on whether this problem resonates. If you're building agent workflows that involve money, I want to know: what breaks? What's missing? What would make you actually install this? GitHub: https://ift.tt/xPfIy4A Docs: https://docs.settld.work/ Quickstart (10 min): https://docs.settld.work/quickstart February 14, 2026 at 01:17AM