Show HN: Built a tool solve the nightmare of chunking tables in PDF vs. Markdown
Show HN (score: 6)Description
More from Show
Show HN: I just fixed .env once and for all – better-env
Show HN: I just fixed .env once and for all – better-env .env files have always felt archaic, insecure, clunky and honestly just not fun to work with. I see my friends (and myself) accidentally committing them all the time. Managing secrets across projects becomes a mess of copy-pasting keys into scattered env files with no real way to sync anything.<p>So I built better-env: a secure, developer-friendly alternative to .env.<p>Store your secrets once in a global encrypted store, and load them per-project at runtime.<p>I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for teams or CI setups.<p>Fully open source: <a href="https://github.com/HarishChandran3304/better-env" rel="nofollow">https://github.com/HarishChandran3304/better-env</a>
Show HN: better-env – A Secure, Developer-Friendly Alternative to .env
Show HN: better-env – A Secure, Developer-Friendly Alternative to .env I’ve always hated how archaic .env files feel. Plaintext, easy to leak, and once they hit git history… you’re cooked. After accidentally committing secrets a few too many times, I finally asked myself: why don't we encrypt secrets just like passwords?<p>So I built better-env: a local, encrypted way to manage secrets without exposing plaintext all over your machine. One place for secrets, nothing sensitive in git, your secrets get directly loaded at runtime, project-wise.<p>It’s early, local-first, and still rough around the edges, but it already removed a whole category of stress from my workflow. I’d love feedback on whether this feels useful beyond solo devs, and what you’d want for team/CI setups.<p>It's open source too! (<a href="https://github.com/HarishChandran3304/better-env" rel="nofollow">https://github.com/HarishChandran3304/better-env</a>)
Show HN: YAAT – Privacy-first analytics for EU companies (need for beta users)
Show HN: YAAT – Privacy-first analytics for EU companies (need for beta users) I built YAAT for EU companies that can't of send data to US servers or being locked into pre-built dashboards that can't answer custom questions.<p>What makes it different:<p>Direct SQL access to your data. Not just pre-built reports – write actual queries against your raw events. Want to know which UTM campaigns convert best for mobile users in Germany? Write the query, get the answer, save it as a dashboard panel.<p>Full analytics stack:<p>Web analytics: pageviews, sessions, traffic sources, UTM tracking, device/browser/geo data Error tracking: JavaScript exceptions, unhandled promises, stack traces, filtering by browser/version Performance monitoring: Core Web Vitals (LCP, FID, CLS, INP), page load times, TTFB<p>Custom dashboards: Drag-drop panels anywhere. Time series, bar charts, pie charts, maps, tables. Monaco editor with SQL autocomplete. Export data as Parquet files – full ownership.<p>Privacy-first: EU-hosted infrastructure (no data transfers), GDPR-compliant, no cookies needed, lightweight script (<2KB).<p>Domain verification via DNS ensures only your sites can send data.<p>Current state: Beta with 7 verified domains tracking production traffic. Looking for 10 EU companies to test for 3 months free.<p>Want feedback on SQL interface and what analytics patterns matter most for your business.<p>Try it: <a href="https://yaat.io/beta" rel="nofollow">https://yaat.io/beta</a><p>Built in Valencia, Spain. All data stays in EU.
Show HN: Building WebSocket in Apache Iggy with Io_uring and Completion Based IO
Show HN: Building WebSocket in Apache Iggy with Io_uring and Completion Based IO
No other tools from this source yet.