ads
Wednesday, January 14, 2026
Show HN: A 10KiB kernel for cloud apps https://ift.tt/6aIhWiA
Show HN: A 10KiB kernel for cloud apps https://ift.tt/VOy1zqw January 14, 2026 at 11:04PM
Tuesday, January 13, 2026
Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever https://ift.tt/nmIuLTe
Show HN: Self-host Reddit – 2.38B posts, works offline, yours forever Reddit's API is effectively dead for archival. Third-party apps are gone. Reddit has threatened to cut off access to the Pushshift dataset multiple times. But 3.28TB of Reddit history exists as a torrent right now, and I built a tool to turn it into something you can browse on your own hardware. The key point: This doesn't touch Reddit's servers. Ever. Download the Pushshift dataset, run my tool locally, get a fully browsable archive. Works on an air-gapped machine. Works on a Raspberry Pi serving your LAN. Works on a USB drive you hand to someone. What it does: Takes compressed data dumps from Reddit (.zst), Voat (SQL), and Ruqqus (.7z) and generates static HTML. No JavaScript, no external requests, no tracking. Open index.html and browse. Want search? Run the optional Docker stack with PostgreSQL – still entirely on your machine. API & AI Integration: Full REST API with 30+ endpoints – posts, comments, users, subreddits, full-text search, aggregations. Also ships with an MCP server (29 tools) so you can query your archive directly from AI tools. Self-hosting options: - USB drive / local folder (just open the HTML files) - Home server on your LAN - Tor hidden service (2 commands, no port forwarding needed) - VPS with HTTPS - GitHub Pages for small archives Why this matters: Once you have the data, you own it. No API keys, no rate limits, no ToS changes can take it away. Scale: Tens of millions of posts per instance. PostgreSQL backend keeps memory constant regardless of dataset size. For the full 2.38B post dataset, run multiple instances by topic. How I built it: Python, PostgreSQL, Jinja2 templates, Docker. Used Claude Code throughout as an experiment in AI-assisted development. Learned that the workflow is "trust but verify" – it accelerates the boring parts but you still own the architecture. Live demo: https://online-archives.github.io/redd-archiver-example/ GitHub: https://ift.tt/8jpNDb0 (Public Domain) Pushshift torrent: https://ift.tt/pzYdDac... https://ift.tt/8jpNDb0 January 13, 2026 at 10:35PM
Show HN: Ayder – HTTP-native durable event log written in C (curl as client) https://ift.tt/OKyrMuR
Show HN: Ayder – HTTP-native durable event log written in C (curl as client) Hi HN, I built Ayder — a single-binary, HTTP-native durable event log written in C. The wedge is simple: curl is the client (no JVM, no ZooKeeper, no thick client libs). There’s a 2-minute demo that starts with an unclean SIGKILL, then restarts and verifies offsets + data are still there. Numbers (3-node Raft, real network, sync-majority writes, 64B payload): ~50K msg/s sustained (wrk2 @ 50K req/s), client P99 ~3.46ms. Crash recovery after SIGKILL is ~40–50s with ~8M offsets. Repo link has the video, benchmarks, and quick start. I’m looking for a few early design partners (any event ingestion/streaming workload). https://ift.tt/fEwTGlO January 14, 2026 at 12:55AM
Show HN: Data from a mixed-brand LiFePO₄ battery bank https://ift.tt/6NhRK34
Show HN: Data from a mixed-brand LiFePO₄ battery bank Hi HN — I’m sharing an empirical, long-term dataset from a DIY energy-storage project that ended up testing a common assumption in battery design. Conventional advice says never mix battery brands. That guidance is well-founded for series strings, but there’s surprisingly little data on purely parallel configurations. I built a 12 V, 500 Ah LiFePO₄ battery bank (1S5P) using mixed-brand cells and instrumented it for continuous monitoring over 73+ days, including high-frequency voltage sampling. The goal was to see whether cell-level differences actually manifest over time in a parallel topology. What the data shows No progressive voltage divergence across the observation period Voltage spread remained within ~10–15 mV Measured Peukert exponent ≈ 1.00 Thermal effects were small relative to instrumentation noise In practice, the parallel architecture appears to force electrical convergence when interconnect resistance is low. I’ve been referring to this as “architectural immunity” — the idea that topology can dominate cell-level mismatch under specific conditions. This is not a recommendation to mix batteries casually, and it’s not a safety guarantee. It’s an attempt to replace folklore with measurements and to define the boundary conditions where this does or does not hold. Everything is public: Raw CSV data Analysis scripts Full PDF report Replication protocol Repo: https://ift.tt/pmk0A4K I’m posting this to invite critique — especially around failure modes, instrumentation limits, or cases where this model would break down (e.g., higher C-rates, aging asymmetry, thermal gradients, different chemistries). Happy to answer technical questions. January 14, 2026 at 12:53AM
Show HN: DebtBomb – Make TODOs expire and automatically create Jira tickets https://ift.tt/Vv1uqHR
Show HN: DebtBomb – Make TODOs expire and automatically create Jira tickets Hi HN, In most codebases I’ve worked on, temporary hacks (“TODO: remove later”, “just for this release”) slowly become permanent. Nobody remembers why they exist, but they keep shipping to production. I built a small CLI called DebtBomb to make that explicit. Instead of free-form TODOs, you attach an expiry date to temporary code. When the date passes, CI fails until the code is removed or the expiry is intentionally extended. Recently I added integrations so expired debt bombs don’t just fail CI — they become visible and owned: When a debt bomb expires, DebtBomb can automatically create a Jira ticket with file path, owner, reason, and code snippet. It can also notify Slack, Discord, or Microsoft Teams. You can configure “expiring soon” warnings (e.g., 7 days before) so it’s not just a surprise break. Repo: https://ift.tt/no2G1Jw This is still early and I’m mainly trying to validate whether this actually improves how teams handle “temporary” code compared to TODOs, linters, or just creating tickets manually. I’d especially love feedback from people who’ve dealt with tech debt in long-lived codebases or CI-heavy environments. Thanks for reading. https://ift.tt/no2G1Jw January 13, 2026 at 11:59PM
Monday, January 12, 2026
Show HN: AI in SolidWorks https://ift.tt/2KCHUdB
Show HN: AI in SolidWorks Hey HN! We’re Will and Jorge, and we’ve built LAD (Language-Aided Design), a SolidWorks add-in that uses LLMs to create sketches, features, assemblies, and macros from conversational inputs ( https://www.trylad.com/ ). We come from software engineering backgrounds where tools like Claude Code and Cursor have come to dominate, but when poking around CAD systems a few months back we realized there's no way to go from a text prompt input to a modeling output in any of the major CAD systems. In our testing, the LLMs aren't as good at making 3D objects as they are are writing code, but we think they'll get a lot better in the upcoming months and years. To bridge this gap, we've created LAD, an add-in in SolidWorks to turn conversational input and uploaded documents/images into parts, assemblies, and macros. It includes: - Dozens of tools the LLM can call to create sketches, features, and other objects in parts. - Assembly tools the LLM can call to turn parts into assemblies. - File system tools the LLM can use to create, save, search, and read SolidWorks files and documentation. - Macro writing/running tools plus a SolidWorks API documentation search so the LLM can use macros. - Automatic screenshots and feature tree parsing to provide the LLM context on the current state. - Checkpointing to roll back unwanted edits and permissioning to determine which commands wait for user permission. You can try LAD at https://www.trylad.com/ and let us know what features would make it more useful for your work. To be honest, the LLMs aren't great at CAD right now, but we're mostly curious to hear if people would want and use this if it worked well. https://www.trylad.com January 12, 2026 at 11:56PM
Show HN: Pane – An agent that edits spreadsheets https://ift.tt/Ie5FJ6o
Show HN: Pane – An agent that edits spreadsheets Hi HN, I built Pane, a spreadsheet-native agent that operates directly on the grid (cells, formulas, references, ranges) instead of treating spreadsheets as text. Most spreadsheet AI tools fail because they: - hallucinate formulas - lose context across edits - can't reliably modify existing models Pane runs inside the spreadsheet environment and uses the same primitives a human would: selecting cells, editing formulas, inserting ranges, reconciling tables. I launched it on Product Hunt this weekend and it unexpectedly resonated, which made me curious whether this approach actually holds up under scrutiny. I'd love feedback on: - obvious failure modes you expect - whether this is fundamentally better than scripts + formulas + copilots Happy to answer technical questions. https://paneapp.com January 12, 2026 at 10:41PM
Show HN: words.zip – Massively infinite word search https://ift.tt/k4JdxUb
Show HN: words.zip – Massively infinite word search Hi HN! This is a word search game I launched in the beginning of this year - didn't get much traction then, but it's been posted around a bit (right now getting some traffic from kottke.org) and now has over 12,000 words found! Now that it's a little more filled out I figured I'd share it again. Really enjoying seeing what everyone is making on it - it appears most people start by just adding a few words to the big clump in the middle, then adding to other people's projects (or ruining them) and finally working on their own little concepts. My favorite is the kitty to the north. Hope you enjoy! https://words.zip/ January 12, 2026 at 09:22PM
Sunday, January 11, 2026
Show HN: A MCP for controlling terminal UI apps built with bubbletea and ratatui https://ift.tt/jZKSnbk
Show HN: A MCP for controlling terminal UI apps built with bubbletea and ratatui so you can start vibe-coding your ad-hoc terminal dashboard. With session replay and mouse click support built-in. https://ift.tt/2bC3qLW January 12, 2026 at 02:54AM
Show HN: Epstein IM – Talk to Epstein clone in iMessage https://ift.tt/NKlEefS
Show HN: Epstein IM – Talk to Epstein clone in iMessage https://epstein.im/ January 11, 2026 at 07:58AM
Saturday, January 10, 2026
Show HN: Persistent Memory for Claude Code (MCP) https://ift.tt/1KdZgsA
Show HN: Persistent Memory for Claude Code (MCP) This is my attempt in building a memory that evolves and persist for claude code. My approach is inspired from Zettelkasten method, memories are atomic, connected and dynamic. Existing memories can evolve based on newer memories. In the background it uses LLM to handle linking and evolution. I have only used it with claude code so far, it works well with me but still early stage, so rough edges likely. I'm planning to extend it to other coding agents as I use several different agents during development. Looking for feedbacks! https://ift.tt/tmo7evK January 11, 2026 at 03:34AM
Show HN: I used Claude Code to discover connections between 100 books https://ift.tt/xTGtQRe
Show HN: I used Claude Code to discover connections between 100 books I think LLMs are overused to summarise and underused to help us read deeper. I built a system for Claude Code to browse 100 non-fiction books and find interesting connections between them. I started out with a pipeline in stages, chaining together LLM calls to build up a context of the library. I was mainly getting back the insight that I was baking into the prompts, and the results weren't particularly surprising. On a whim, I gave CC access to my debug CLI tools and found that it wiped the floor with that approach. It gave actually interesting results and required very little orchestration in comparison. One of my favourite trail of excerpts goes from Jobs’ reality distortion field to Theranos’ fake demos, to Thiel on startup cults, to Hoffer on mass movement charlatans ( https://ift.tt/A2jurdt ). A fun tendency is that Claude kept getting distracted by topics of secrecy, conspiracy, and hidden systems - as if the task itself summoned a Foucault’s Pendulum mindset. Details: * The books are picked from HN’s favourites (which I collected before: https://ift.tt/5Z7dqtS ). * Chunks are indexed by topic using Gemini Flash Lite. The whole library cost about £10. * Topics are organised into a tree structure using recursive Leiden partitioning and LLM labels. This gives a high-level sense of the themes. * There are several ways to browse. The most useful are embedding similarity, topic tree siblings, and topics cooccurring within a chunk window. * Everything is stored in SQLite and manipulated using a set of CLI tools. I wrote more about the process here: https://ift.tt/XZ7IBGS I’m curious if this way of reading resonates for anyone else - LLM-mediated or not. https://ift.tt/9AoT0pn January 10, 2026 at 11:56PM
Show HN: 15 Years of StarCraft II Balance Changes Visualized Interactively https://ift.tt/Hac9n8f
Show HN: 15 Years of StarCraft II Balance Changes Visualized Interactively Hi HN! "Never perfect. Perfection goal that changes. Never stops moving. Can chase, cannot catch." - Abathur ( https://www.youtube.com/watch?v=pw_GN3v-0Ls ) StarCraft 2 is one of the most balanced games ever - thanks to Blizzard’s pursuit of perfection. It has been over 15 years since the release of Wings of Liberty and over 10 years since the last installment, Legacy of the Void. Yet, balance updates continue to appear, changing how the game plays. Thanks to that, StarCraft is still alive and well! I decided to create an interactive visualization of all balance changes, both by patch and by unit, with smooth transitions. I had this idea quite a few years ago, yet LLMs made it possible - otherwise, I wouldn't have had the time to code or to collect all changes from hundreds of patches (not all have balance updates). It took way more time than expected - both dealing with parsing data and dealing with D3.js transitions. Pretty much pure vibe coding with Claude Code and Opus 4.5 - while constantly using Playwright skills and consulting Gemini 3 Pro ( https://ift.tt/eJ8Y5KM ). While Opus 4.5 was much better at executing, it was often essential to use Gemini to get insights, to get cleaner code, or to inspect screenshots. The difference in quality was huge. Still, it was tricky, as LLMs do not know D3.js nearly as well as React. The D3.js transition part is a thing that sometimes I think would be better to do manually, and only use LLMs for details. But it was also a lesson. Enjoy! Source code is here: https://ift.tt/7RewPOi https://ift.tt/7jhzUZf January 11, 2026 at 12:37AM
Subscribe to:
Posts (Atom)