最新

Fully built with Claude Code. Hook into Claude Code sessions to sync session data to <a href="https:&#x2F;&#x2F;confabulous.dev" rel="nofollow">https:&#x2F;&#x2F;confabulous.dev</a>. From there, you can explore the transcript, create share links, calculate productivity metrics.<p>CLI piece is open source at <a href="https:&#x2F;&#x2F;github.com&#x2F;ConfabulousDev&#x2F;confab" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;ConfabulousDev&#x2F;confab</a><p>Free while in beta. Likely there will be a free tier forever.<p>Give it a spin at <a href="https:&#x2F;&#x2F;confabulous.dev" rel="nofollow">https:&#x2F;&#x2F;confabulous.dev</a>

What is the most straightforward way to write a technical book that needs to contain nicely formatted code snippets and images.<p>I&#x27;ve seen people using markdown, but how do you get a nice workflow where multiple markdown files gets converted into a single nicely formatted pdf&#x2F;epub with a clickable table of contents and pagination.

There is also a little command line tool to search jobs from command line. You can also use the web interface at <a href="https:&#x2F;&#x2F;jobswithgpt.com" rel="nofollow">https:&#x2F;&#x2F;jobswithgpt.com</a>

Hi HN,<p>I’m working on an experimental 3D FPS game engine in C++20, aiming to deeply understand engine internals from first principles rather than just using existing frameworks.<p>Currently I&#x27;m strictly following LearnOpenGL docs.<p>This project focuses on: Entity-Component-System (ECS) architecture for high performance. OpenGL 4.1 rendering with a PBR pipeline, material system, HDR, SSAO, and shadow mapping. Modular systems: input, physics (Jolt), audio (miniaudio), assets, hot reload. A sample FPS game &amp; debug editor built into the repo.<p>Repo: <a href="https:&#x2F;&#x2F;github.com&#x2F;jackthepunished&#x2F;horizon-engine" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;jackthepunished&#x2F;horizon-engine</a><p>This isn’t intended to be a commercial rival to any commercial game engines.<p>it’s a learning and exploration project: understanding why certain engine decisions are made, and how to build low-level engine systems from scratch.<p>I’m especially looking for feedback on: Architecture choices (ECS design, render loop, module separation) Your thoughts on modern C++ engine patterns<p>What you’d build vs stub early in a homemade engine<p>Tips from experienced graphics&#x2F;engine developers Criticism and suggestions are very welcome — it’s early days and meant to evolve. Thanks for checking it out!

Main tools on Kliga.com:<p>1) AI Music Detector<p>- Detects with 99.9% accuracy with smart models attuned to latest AI models. - You can upload an audio file or paste a Spotify track URL and Kliga analyzes whether the music is likely AI-generated or human-made. - It uses spectral + temporal analysis and gives a probability breakdown instead of a simple yes&#x2F;no.<p>2) Audio Mastering<p>- 100% private, your songs never hit our servers - Preview with 12 Studio-grade presets designed by industry experts. - Download in HD-WAV 24 bit, MP3 320kbps for FREE. - No audio engineering required.<p>There are other useful tools like video compressor, audio cutter, etc. Do check them out.<p>Why I built this:<p>- AI-generated music is everywhere now, but it’s hard to quickly verify authenticity accurately.<p>- Most artists want to master their songs privately before releasing. They want one-click processing happening in their own device without having to download an expensive software.<p>Direct Links to main tools:<p>- AI Detector: <a href="https:&#x2F;&#x2F;kliga.com&#x2F;ai-music-detector" rel="nofollow">https:&#x2F;&#x2F;kliga.com&#x2F;ai-music-detector</a><p>- Audio Mastering: <a href="https:&#x2F;&#x2F;kliga.com&#x2F;mastering" rel="nofollow">https:&#x2F;&#x2F;kliga.com&#x2F;mastering</a><p>Happy to answer any questions. Thanks for checking it out!

Hi all, I am designing an AWS-based unstructured document ingestion platform (PDF&#x2F;DOCX&#x2F;PPTX&#x2F;XLSX) for large-scale enterprise repositories, using vision-language models to normalize pages into layout-aware markdown and then building search&#x2F;RAG indexes or extract structured data.<p>For those who have built something similar recently, what approach did you use to preserve document structure reliably in the normalized markdown (headings, reading order, nested tables, page boundaries), especially when documents are messy or scanned? Did you do page-level extraction only, or did you use overlapping windows &#x2F; multi-page context to handle tables and sections spanning pages?<p>On the indexing side, do you store only chunks + embeddings, or do you also persist richer metadata per chunk (page ranges, heading hierarchy, has_table&#x2F;contains_image flags, extraction confidence&#x2F;quality notes, source pointers) and if so, what proved most valuable? How does that help in the agent retrieval process?<p>What prompt patterns worked best for layout-heavy pages (multi-column text, complex tables, footnotes, repeated headers&#x2F;footers), and what failed in practice?<p>How did you evaluate extraction quality at scale beyond spot checks (golden sets, automatic heuristics, diffing across runs&#x2F;models, table-structure metrics)?<p>Any lessons learned, anti-patterns, or “if I did it again” recommendations would be very helpful.

I wanted to control the browser from the terminal so I made buse:<p>buse browser-1 # open chrome<p>buse browser-1 navigate &quot;<a href="https:&#x2F;&#x2F;example.com" rel="nofollow">https:&#x2F;&#x2F;example.com</a>&quot;<p>buse browser-2 # open a second browser<p>buse browser-2 search &quot;cat&quot;<p>buse browser-1 observe # returns JSON about the page<p>buse browser-1 click 16 # clicks on the learn more link<p>I&#x27;ve been reading about agentic computer use and I tried to use MCPs and Browserbase, but there was just a lot of friction for me. So, I brought it to the CLI instead.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;rinvii&#x2F;buse" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;rinvii&#x2F;buse</a>