Show HN: Forwarder.cc – Static-site forms sent to your inbox, pay per message https://ift.tt/LKd1fzT

Show HN: Forwarder.cc – Static-site forms sent to your inbox, pay per message TL;DR: 12 years ago I built a service that forwards simple HTML forms to an email address. I've been procrastinating on finishing it ever since, until today. You point your form at it and every submission lands in your inbox. It runs on credits, 1 credit = 1 message, no subscription. Perfect for static websites. — Hey folks, back around 2014, alongside my job as a software engineer, I was building a lot of static websites for my own clients, mostly small businesses that just wanted a simple site. To avoid headaches, I went fully static, often hosted on GitHub Pages and similar. But most clients also wanted a contact form, and a form needs a server running somewhere. I had my own weekend-hacked service for this, which literally just forwarded the form to the client's email. I didn't invent anything here: one service I particularly remember was FormKeep by thoughtbot, that I really liked. So I started building my own, mostly because I loved losing myself in side projects like this, and also because I was a cheap ass and thought I could do something similar for less, and without a subscription. By 2016 I had done about 90% of what I'm showing you today. I called it "The Great Forwarder". Everything was ready: backend, frontend, hosting, Stripe, landing page. I even had a designer friend help with the design (sorry, Valentin, if I've botched it since). Then I started another project, which took off right away and took all my attention for a while. Fun fact: that project has been using this service ever since, and almost every message ever sent through it came from there. So for years, I kept Forwarder.cc up to date, upgrading libraries and trying new ones: axios, got, Redux, Zustand, create-react-app, webpack, Vite… It became my laboratory for everything I wanted to explore, while always staying up and maintained (again, for my own use only). The only thing that ever held me back from launching it was a missing help center, and, more honestly, the fear of putting it in front of people. So today's the day: after 12 years of procrastination, I finally finished the help center. I know there are a ton of similar services nowadays, but anyway, what do you think of that help center? https://forwarder.cc October 16, 2026 at 12:17AM

Show HN: RDST – A local agent that watches Postgres/MySQL for query regressions https://ift.tt/JgoQ2wL

Show HN: RDST – A local agent that watches Postgres/MySQL for query regressions We noticed during the course of many many years of DBA related work that fixes to database issues and queries are always reactive. An entire database can fall over extremely quickly when an unbounded query grows without warning. Traditionally, DBAs hear complaints of slowness and follow a methodical process: - manually browse pg_stats or other database related performance internal tables - see which queries are slowest - figure out what indexes are missing - figure out which indexes are actually bad and slowing down writes - painstakingly implement a fix In the age of cheap intelligence, we decided that there is no reason we can’t have an always-on agent that is designed to do this job for you. Databases need something or someone that is always watching with a massive amount of contextual understanding to be able to take quick actions. We’ve watched the alternative play out repeatedly. One of our users’s checkout page went from loading instantly to taking 11 seconds in a single night with no code change. How? Well somehow their order table grew by 40M rows because BI team had injected historical data and suddenly postgres started doing full table scans. Sometimes routine operations have unintended results and can easily destroy your database. We wanted to catch these kinds of regressions instantly. So we built RDST. RDST is a desktop agent that runs on your PC and connects to PostgreSQL / MYSQL (read only) and compares every query against its own performance every minute. Every expensive query is automatically EXPLAIN ANALYZED, stripped of PII and sent to U.S. based frontier or open model providers to analyze which indexes are missing, how the query could be rewritten, and provides the fix. We then run a classifier model (JEV) to decide if you should be notified (is this standard behavior for this particular query?), and the full history of the query performance is kept for years. RDST also keeps track of your entire database health in general, and recommends more fixes than simply bad queries. Since it runs locally we can keep the database credentials stored in your OS Keychain (RDST never keeps them in its own storage layer), and the connection goes straight to your database (using a jump host or SSH tunnel for private connections). You can read more about how we handle data especially as it pertains to LLM use here. https://ift.tt/kCFrxKR We really want feedback from the community from people running Postgres and MySQL in production. We are giving inference away completely for free. Just as a reminder, RDST will NOT run any updates or indexes against your database at this time. We are considering a fully autonomous auto-pilot mode in the future, but for now we are leaving the actual fixes in your hands. Let us know what you think! https://ift.tt/dKXJQW7 October 15, 2026 at 11:39PM

Show HN: I think Apple should have built this a long time ago https://ift.tt/4DwL0oK

Show HN: I think Apple should have built this a long time ago Built this little tool a while ago and shared it with a few friends. The feedback I got was great that I decided to release it publicly. It's not just another 'clipboard'... Honestly, would love you guys to try it out! This is my first public release of a product with a price tag! I have 0 expectations for it... but I genuinely love using it myself. https://ift.tt/lfEUR8L October 15, 2026 at 05:48AM

Show HN: Ask a technical question, get an animated explainer you can interrupt https://ift.tt/go7x9W0

Show HN: Ask a technical question, get an animated explainer you can interrupt https://ift.tt/zlX69wn October 15, 2026 at 04:10AM

Show HN: Dub Anything – Dub videos in each actor's own voice https://ift.tt/mjFCfBa

Show HN: Dub Anything – Dub videos in each actor's own voice There are many movies and shows out there with neither subtitles or dubs in English (or any other language). Pretty much impossible to watch. With SOTA AI now directing the process, you can do it locally on your machine. You basically just clone the repo, open up Codex or Claude and tell it to dub the video you want in the language you want. The repo contains all the scripts and guidance I've developed over the past few weeks to create dubs that are watchable, as an added bonus the voices in the dub are the actors own voices which is really nice. Also it's self improving, each dub may modify the scripts for better fidelity. So feel free to push them back to the repo so everyone benefits. Thanks. https://ift.tt/KSmbkja October 15, 2026 at 01:19AM

Show HN: Petal, open-source CoScreen/ScreenHero finally free https://ift.tt/Qckiluw

Show HN: Petal, open-source CoScreen/ScreenHero finally free Hi HN! I’m Jason Thomas, one of the founders of CoScreen. As some of you may know, Datadog sunset the CoScreen service on July 31st. Four of us from the original CoScreen team have spent the last couple months building a free and open source pair programming tool inspired by those that came before us: It’s called Petal ( https://ift.tt/pCaBqz4 ) Some history first, because when we started CoScreen we had hoped to break the sad and established pattern of this industry. Screenhero was an exceptional tool that a lot of us loved for pairing. Multiple cursors, low latency, you could click your partner’s editor, and just start typing. It felt like magic while we had it. Then Slack bought it in 2015, and shut down the standalone app in December 2017. When Till, Max, and I started CoScreen, we were aware of this history, and wanted to build an even more magical collaboration and screen sharing experience: the entire concept was “throw a window from your laptop up on someone else’s screen, and start collaborating with zero friction.” Datadog acquired us in 2022, and thus began the great adventure of adapting our real-time technology into Datadog products, while also continue developing CoScreen as a standalone tool from the Datadog ecosystem. Datadog invested in the product for years and we’re thankful for that. But CoScreen itself proved, like so many other screen sharing tool acquisitions, to be too tangential from the customer base and core mission. We instead built other communication features in Datadog, the integrations with other video platforms, and also its wildly successful MCP server. We weren't the only ones. Around was bought by Miro and shut down in March 2025. Multi (formerly Remotion) was acqui-hired by OpenAI in 2024 and shut down about a month later. It's nearly always the same story: a small team builds something hard that people love, a platform buys it for the team or the feature, and the standalone product doesn't survive the integration. So we decided firmly to do things differently this time. Petal is completely free and open source and we aren't monetizing it. If we lose interest or get hit by a bus, you can self-host it or fork it, and nobody can sunset it on you. Honestly it's a love letter to everyone in this community that supported us, believed in us, and to liberate collaborative screen sharing from this vicious cycle. We hope through this we can help foster a large and vibrant community around innovating in this product sector. What Petal does: shared windows show up as real windows on your desktop, movable and resizable, not tiles in a grid. Several people can share at once, everyone gets a labeled cursor, and you can click into any shared window to type and scroll. Rooms are persistent, so you click once to join "eng-sync" instead of passing links around. It runs on macOS and Windows (Linux is next, this time for real and you can help us!), plus a web app. Media goes over LiveKit. You can use our hosted instance with zero config, or point the app at your own LiveKit server with one docker-compose if you want the traffic to stay on your network or even use an entirely different video backend if you want to. The part that still feels strange to us: CoScreen took almost six years to build. The first version of Petal took under eight weeks, from scratch, with frontier models like Fable and Astra doing a lot of the work. Real-time video and window capture is some of the most unforgiving code we have ever written, so we didn't expect that. We will do a proper writeup on what worked and what didn't, and are happy to answer questions about it here. Till, Darren, Max and I will be in the thread. https://petal.live/ October 14, 2026 at 11:53PM

Show HN: Sayso, free open source dictation for Mac, Windows, and Linux https://ift.tt/jSxaVhg

Show HN: Sayso, free open source dictation for Mac, Windows, and Linux https://ift.tt/wc0DrJA October 13, 2026 at 09:26PM