Show HN: Summle – A little maths Game https://ift.tt/EDOQC51

Show HN: Summle – A little maths Game https://summle.net June 26, 2025 at 05:58PM

Show HN: Ciara – Securely deploy any application on any server https://ift.tt/NMUD2O0

Show HN: Ciara – Securely deploy any application on any server Hey HN! Coolify and Kamal were "nice" (Kamal docs are pretty bad, actually), but I still had to configure firewalls, unattended-upgrades, and Fail2ban every single time. Ciara does all of this from a single configuration file. Features: Integrated Firewall Automatic System Updates Zero-Config OS Ready Zero-Downtime Deployments Automatic HTTPS support Multiple Servers Deployments Would love your feedback and happy to answer any questions! https://ift.tt/12ZMQsw June 30, 2025 at 03:00AM

Show HN: Sharpe Ratio Calculation Tool https://ift.tt/q7XlODb

Show HN: Sharpe Ratio Calculation Tool I built a simple but effective Sharpe Ratio calculator that gives the full historical variation of it. Should I add other rations like Calmar and Sortino? https://ift.tt/ah9u4At June 30, 2025 at 12:38AM

Show HN: A tool to benchmark LLM APIs (OpenAI, Claude, local/self-hosted) https://ift.tt/qD6pyCl

Show HN: A tool to benchmark LLM APIs (OpenAI, Claude, local/self-hosted) I recently built a small open-source tool to benchmark different LLM API endpoints — including OpenAI, Claude, and self-hosted models (like llama.cpp). It runs a configurable number of test requests and reports two key metrics: • First-token latency (ms): How long it takes for the first token to appear • Output speed (tokens/sec): Overall output fluency Demo: https://llmapitest.com/ Code: https://ift.tt/c0l5yOp The goal is to provide a simple, visual, and reproducible way to evaluate performance across different LLM providers, including the growing number of third-party “proxy” or “cheap LLM API” services. It supports: • OpenAI-compatible APIs (official + proxies) • Claude (via Anthropic) • Local endpoints (custom/self-hosted) You can also self-host it with docker-compose. Config is clean, adding a new provider only requires a simple plugin-style addition. Would love feedback, PRs, or even test reports from APIs you’re using. Especially interested in how some lesser-known services compare. https://llmapitest.com/ June 29, 2025 at 10:33PM

Show HN: Open-Source outcome- / usage-based billing engine for AI Agents https://ift.tt/rOXNdT5

Show HN: Open-Source outcome- / usage-based billing engine for AI Agents https://ift.tt/PrQeg81 June 29, 2025 at 01:42AM

Show HN: A Go service that exposes a FIFO message queue in RAM https://ift.tt/WbxauvK

Show HN: A Go service that exposes a FIFO message queue in RAM https://ift.tt/ipmbUTo June 25, 2025 at 06:34PM

Show HN: eKilo – Super lightweight terminal text editor based https://ift.tt/uacUEpy

Show HN: eKilo – Super lightweight terminal text editor based https://ift.tt/7p1KEMx June 28, 2025 at 10:43PM

Show HN: Do You Know RGB? https://ift.tt/cAoY2ZG

Show HN: Do You Know RGB? https://ift.tt/MHCYgdy June 24, 2025 at 03:19PM

Show HN: IssuePay – Get paid for open-source contributions https://ift.tt/DfUgpRv

Show HN: IssuePay – Get paid for open-source contributions Hi HN! I’m Mario, and I’m about to launch IssuePay. Problem: Open-source contributors don’t get direct financial recognition for their work. Solution: IssuePay lets maintainers post bounties on GitHub/GitLab issues. Contributors pick tasks, merge code, and get paid automatically. You can then withdraw your earnings directly to your Bank Account. Try it out: https://issuepay.app Questions: Would love feedback on our UX, payout reliability, or any scaling tips. Note: Open to partnerships with OSS communities! Thank you, guys ! <3 https://issuepay.app June 28, 2025 at 01:31AM

Show HN: Gobsmacked - A tool to convert any recipe to an easy to read notation https://ift.tt/i32CRAT

Show HN: Gobsmacked - A tool to convert any recipe to an easy to read notation Hi HN, I have been working on a project which can automatically convert a recipe to the tree/graph/tabular style notation that pops up on HN every now and then. It's still early days but I am keen to hear about improvements I can make to the recipe presentation. For reference, the earliest example I have seen of this style of notation is from 'Cooking For Engineers' ( https://ift.tt/6ZRyUAe ) but I have seen other, similar notations from time to time. This is my take on the notation, as well as the ability to convert recipes automatically. In the future, I would like to see it become my own personal kitchen/recipe management system but I would first like to improve the recipe display options. It uses ChatGPT to format the recipe into a JSON tree structure, which is then rendered with CSS grid. So far it works well enough but there is definitely some recipes that are impossible to render, and of course ChatGPT will occasionally spit out less-than-useful trees. I have been using AppWrite for the backend. Curious to hear everyone's thoughts and what people might like to see! https://gobsmacked.io June 28, 2025 at 12:40AM

Show HN: I'm 15 and built Gofer, an AI that gets actual terminal work done https://ift.tt/zOEKkRH

Show HN: I'm 15 and built Gofer, an AI that gets actual terminal work done Gofer is a side-project I wrote at 15 because I was sick of these so-called CLI agents. Claude Code, Codex, Gemini CLI, they're all wonderful if you're coding. But for those just wanna automate their stuff, it's a dud. Gofer solves this by being terminal-first, meant to accomplish any task a command line can. It can also watch your desktop so you can avoid waiting for downloads to finish, and can text you via. Telegram! Happy to answer any questions :D! -J https://ift.tt/xzJfShI June 27, 2025 at 11:08PM

Show HN: Pocket2Linkding – Migrate from Mozilla Pocket to Linkding https://ift.tt/AWpl0DK

Show HN: Pocket2Linkding – Migrate from Mozilla Pocket to Linkding With the Mozilla Pocket shutdown coming up in about two weeks, I thought I'd share this quick tool to migrate to linkding in case it's helpful to others. After reviewing self-hosted options to Pocket, I decided linkding has the best combination of features. (The creator/author of linkding has done a great job -- however, I plan to eventually create a new tool that is based on linkding but adds some new features that the author has indicated he doesn't want to include [I’m currently using a fork, but I want to expand on it further].) HN thread about shutdown announcement: https://ift.tt/2jqebPB Mozilla announcement: https://ift.tt/CKY12qM linkding: https://linkding.link/ Note that Pocket is shutting down July 8, 2025, but the export service will remain available until October 8, 2025. [edit] fix typo in title & formatting https://ift.tt/oRKsgvk June 27, 2025 at 12:03AM

Show HN: Magnitude – open-source AI browser automation framework https://ift.tt/HT4komC

Show HN: Magnitude – open-source AI browser automation framework Hey HN, Anders and Tom here. We had a post about our AI test automation framework 2 months ago that got a decent amount of traction ( https://ift.tt/ZmTSR1c ). We got some great feedback from the community, with the most positive response being about our vision-first approach used in our browser agent. However, many wanted to use the underlying agent outside the testing domain. So today, we're releasing our fully featured AI browser automation framework. You can use it to automate tasks on the web, integrate between apps without APIs, extract data, test your web apps, or as a building block for your own browser agents. Traditionally, browser automation could only be done via the DOM, even though that’s not how humans use browsers. Most browser agents are still stuck in this paradigm. With a vision-first approach, we avoid relying on flaky DOM navigation and perform better on complex interactions found in a broad variety of sites, for example: - Drag and drop interactions - Data visualizations, charts, and tables - Legacy apps with nested iframes - Canvas and webGL-heavy sites (like design tools or photo editing) - Remote desktops streamed into the browser To interact accurately with the browser, we use visually grounded models to execute precise actions based on pixel coordinates. The model used by Magnitude must be smart enough to plan out actions but also able to execute them. Not many models are both smart *and* visually grounded. We highly recommend Claude Sonnet 4 for the best performance, but if you prefer open source, we also support Qwen-2.5-VL 72B. Most browser agents never make it to production. This is because of (1) the flaky DOM navigation mentioned above, but (2) the lack of control most browser agents offer. The dominant paradigm is you give the agent a high-level task + tools and hope for the best. This quickly falls apart for production automations that need to be reliable and specific. With Magnitude, you have fine-grained control over the agent with our `act()` and `extract()` syntax, and can mix it with your own code as needed. You also have full control of the prompts at both the action and agent level. ```ts // Magnitude can handle high-level tasks await agent.act('Create an issue', { // Optionally pass data that the agent will use where appropriate data: { title: 'Use Magnitude', description: 'Run "npx create-magnitude-app" and follow the instructions', }, }); // It can also handle low-level actions await agent.act('Drag "Use Magnitude" to the top of the in progress column'); // Intelligently extract data based on the DOM content matching a provided zod schema const tasks = await agent.extract( 'List in progress issues', z.array(z.object({ title: z.string(), description: z.string(), // Agent can extract existing data or new insights difficulty: z.number().describe('Rate the difficulty between 1-5') })), ); ``` We have a setup script that makes it trivial to get started with an example, just run "npx create-magnitude-app". We’d love to hear what you think! Repo: https://ift.tt/E0Unfky https://ift.tt/E0Unfky June 27, 2025 at 01:30AM