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

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 15, 2026 at 10:47PM

Show HN: GitVolt, open source fast Git GUI (Tauri/CEF) https://ift.tt/tiqspNg

Show HN: GitVolt, open source fast Git GUI (Tauri/CEF) Hi HN! I've been working on this for the past few weeks. I've been using GitKraken for a whole 10 years now, and I've always loved it, but lately I've found it to be a bottleneck, and I haven't seen it improve the features I really care about. So, as many others have done recently, I took a shot at using Opus 5.5 to help me build my dream Git GUI app. I did take massive inspiration from GitKraken (the look and feel is a close match since it's what I feel comfortable with) but everything is built from scratch. I made lots of different UX choices that I think help streamline things. Most importantly, performance was the key thing to get right at the start. I daily-drive Linux so that was first. I went with Tauri to have a really fast Rust core, and after doing performance testing with WebKitGTK it wasn't good enough. So I'm using Tauri's v3 alpha with CEF (Chromium) which made it easy to get a butter smooth 60fps for scrolling a huge list of commits (whereas I would barely get 10fps in my large repo with GitKraken, with tons of hitching). Everything feels so much faster. The website is best viewed on desktop, I included a fully functional web-only version of the app (mocked git and gitlab) so you can try it out! Some cost numbers: ~16 billion tokens, ~$5.4k at API rates, 5.2 full weekly quotas (spread over two 5x plans), ~$120 of subsidized plan cost. https://gitvolt.com/ October 15, 2026 at 04:25AM

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

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/Bm8aA2j October 15, 2026 at 04:18AM

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

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

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

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/QtAIaCH October 14, 2026 at 11:49PM

Show HN: Spotatui, a Spotify TUI/GUI without web API rate limits https://ift.tt/XQPOC1d

Show HN: Spotatui, a Spotify TUI/GUI without web API rate limits About 11 months ago i revived the amazing but unfortunately unmaintained spotify-tui. Since then I have been working on it almost non stop, finding a lot of problems on the way. One of the main issues I ran into were the Spotify web API rate limits. Third party clients like spotatui are dependent on a developer app made in the Spotify developer dashboard, which get rate limited a lot and Spotify has slowly been deprecating endpoints from it. The workaround for this used to be using a shared client id from ncspot but unfortunately that got rate limited too. This is when i started adding other playback sources, including YouTube, Navidrome/Subsonic, Internet radio with +- 30.000 stations, local files, Qobuz for lossless audio and Apple Music for macOS only where it controls the music app remotely. I fixed both the deprecated endpoints and the rate limits with one solution. It still uses librespot in the back, my spotatui specific fork, but gets all data from it instead of only playback. The data comes from the internal API of the official clients, that API gives metadata, playlists, the user library, devices, lyrics and audio analysis. For searching it uses Pathfinder, the internal GraphQL API. There are no web API rate limits because there is no shared app quota. Every user uses their own session as if it was the official client. The only potential problem is that Spotify does not document this API so any change on their side would break it. I intend to fix any of those issues as soon as they pop up. It all started as a TUI back in 2019 but since then I've added a GUI to it too. The GUI is still a bit behind the TUI in terms of features, it only ships Spotify for now, but full parity between the TUI and GUI is coming soon. After that full parity with the official client is next. That is also why I made the GUI looks almost the same as the official client. That way its easier for me and users to find missing features. Spotatui also has lua scripting support, a optional Web companion on spotatui.com, and if you have a AI coding agent like ChatGPT codex or Claude Code you can enable the MCP tools, which lets AI become your personal DJ just by talking to it. Its written in Rust, uses ratatui for the terminal UI and Tauri 2 for the GUI. The Rust core starts a small web server with localhost that only your pc can reach which the GUI then serves. Both frontends share the same playback logic, the same login and the same Spotify code. The only difference is how you interact with it. On first launch it opens a web browser where you need to login with your Spotify premium account (premium is not optional), that is the whole setup done. I would love any feedback about bugs you encounter or features you would like to see. GitHub: https://ift.tt/CF0qkDu Releases: https://ift.tt/83ZUEL2 Website: https://spotatui.com/ Thanks to librespot for making this all possible https://ift.tt/CF0qkDu October 13, 2026 at 03:32PM

Show HN: Brickbrag – A multiplayer brick-building world in the browser https://ift.tt/10xGu4q

Show HN: Brickbrag – A multiplayer brick-building world in the browser https://brickbrag.com/ October 13, 2026 at 01:03AM