Spain blocks prediction markets Polymarket, Kalshi over lack of gambling licence

The worst job interview I ever had

A few interesting modern pixel fonts

That Methyl Methacrylate Tank

I'm Tired of Talking to AI

I built a Git-tracked book production pipeline

Cloudflare Flagship

Rosalind: A genomics toolkit in Rust running whole-genome pipelines on a laptop

The Melancholy of Slaying Monsters

Claude Code as a Daily Driver: Claude.md, Skills, Subagents, Plugins, and MCPs

A portentous reunion

C array types are weird

Hey we’re Faiz and Saheed and we built Minicor so AI companies who need to integrate to desktop systems with no API can quickly build scalable desktop RPAs. Demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=MD0GHZIJ1cw" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=MD0GHZIJ1cw</a>Edit: RPA is an acronym for Robotic Process Automation - things like triggering mouse clicks and key strokes to perform tasks programmatically. Sorry if this wasn&#x27;t clear!We were working on non-RPA integrations when a customer promised to sign a deal in 2 days if we could unblock a sale of theirs that involved integrating with a clinic’s Windows based medical record system. We didn’t know it at the time but it turns out that building desktop RPAs at scale is extremely difficult because scripting is hard (learning the system, defining the automation, UIs changing constantly), orchestration is hard (is the VM up? queuing, parallelizing) and debugging is hard (zero observability, false positives, cascading failures). 30%+ failure rates are not uncommon. At scale we’ve seen cases of failed RPAs leading to thousands of support tickets a month.To solve the problems we were facing, we built an MCP that Claude Code&#x2F;Codex can use to navigate a virtual machine running desktop software with Python to create RPA workflows. The RPA workflows run as Python scripts for speed, cost, and determinism. These workflows can be triggered by API following any input&#x2F;output schema specified, with video replays and logs stored with each run. The MCP can debug RPAs and make changes to the underlying code, all of which are version controlled. We also built tools for cloning VMs for parallelizing RPAs, and handling 2FA&#x2F;OTP challenges. Plus since workflows are code based: we were also able to add triggers for Slack notifications, human-in-the-loop steps, or call an LLM to verify the state of a VM by passing a screenshot.Would love to hear your feedback and if you have any RPA horror stories! (:

Launch HN: Minicor (YC P26) – Windows desktop automations at scale

<a href="https:&#x2F;&#x2F;arstechnica.com&#x2F;information-technology&#x2F;2026&#x2F;05&#x2F;millions-of-ai-agents-imperiled-by-critical-vulnerability-in-open-source-package&#x2F;" rel="nofollow">https:&#x2F;&#x2F;arstechnica.com&#x2F;information-technology&#x2F;2026&#x2F;05&#x2F;milli...</a>

BadHost – CVE-2026-48710: Starlette Host-Header Auth Bypass

Mini Micro Fantasy Computer

What I've Learned (So Far) Building Online Mini Games with Elixir and Swift

Raft Consensus with a Minority of Nodes

Tunecat: Simple Internet Radio

IBM Confidential: System/360 File Organization [video]

Introducing Posthorn, a self hosted email gateway. One docker container (or Go binary) between every self hosted app on your VPS and your transactional email provider. Set up Posthorn once, point your apps to it, done.I was trying to deploy Ghost on a DigitalOcean droplet and found that DO and many different VPS services have started to block the default SMTP ports to try to combat the various types of abuse they get. To actually configure my app, I had to hack together a Postfix relay.In another project, I had a static site which had a contact form, but my free Formspree account was occasionally hitting usage limits and I desperately wanted some of the anti-spam features they had gated behind their paid accounts so I put together a caddy module to catch HTTP POSTs and bounce them to my provider.I kept bumping into these same email issues. Many of the services I wanted to host (Gitea, Mastodon, Umami, Comentario) ran into the same limitations. This felt like a really common issue that had no good solution.Posthorn is what I built to solve this. It&#x27;s a small Go binary (or 10 MB docker image) that sits between your self hosted apps and your transactional email provider of choice (shipping with support for Postmark, Resend, Mailgun, Amazon SES or an outbound SMTP relay). It also accepts POSTs from HTML forms to support static site needs while adding security layers such as honeypot fields, origin checks and IP rate limiting. There&#x27;s also a JSON HTTP API that supports Bearer auth for backend scripts or cron jobs that just want a &#x2F;send endpoint.I now use this personally in multiple scenarios and I&#x27;ve spent a lot of time beating this up and testing against what I can validate. I&#x27;d love to hear how this might be useful for you, what breaks and any feedback you might have. It&#x27;s open source under Apache 2.0 and I&#x27;d love contributions. I&#x27;m planning to support and grow this for the long haul.Code: <a href="https:&#x2F;&#x2F;github.com&#x2F;craigmccaskill&#x2F;posthorn" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;craigmccaskill&#x2F;posthorn</a>Docs: <a href="https:&#x2F;&#x2F;posthorn.dev&#x2F;" rel="nofollow">https:&#x2F;&#x2F;posthorn.dev&#x2F;</a>Longer write up: <a href="https:&#x2F;&#x2F;craigmccaskill.com&#x2F;introducing-posthorn&#x2F;" rel="nofollow">https:&#x2F;&#x2F;craigmccaskill.com&#x2F;introducing-posthorn&#x2F;</a>Previous HN discussion on the exact issue I&#x27;m trying to solve: <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43620318">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=43620318</a>

Show HN: Posthorn, self-hosted mail without the mail server