News for hackers. Stuff that matters.

arturogoosnargh

Author here. Overslash is an authorization gateway for AI agents (or any programmatic user, really).

Overslash can register as a service any HTTP API or MCP server, defined as an OpenAPI document with some small extensions. Once that's done you can share access to those services with agents or teammates. Agents start with no write permissions (and no read permissions either, if you choose). Every time an agent attempts an action, a set of permission keys based on the action and its fields is generated; if the agent is missing any, an approval request is created. The approver can inspect the request — which has human-readable descriptions for the action and fields, taken from the OpenAPI doc — and deny or approve, either just this time or for similar requests in the future (choosing coarser or finer permission keys to remember).

Overslash itself can be used as an MCP server, via REST, via CLI, or via the dashboard (think of it as an authenticated, shareable, auditable Postman).

It's a single Rust binary, persistence on Postgres. Self-hosting will always be free; cloud at https://app.overslash.com is free for individuals, cheap for teams.

I wrote a longer post (with a video demo) on the origins of Overslash: https://www.angelmartin.name/2026/05/29/why-did-i-build-an-a...

Repo: https://github.com/overfolder/overslash

Note: had to use an old HN account since i dont have enough karma on my new one

Seems useful for interactivity on sites using static site generators like Jekyll.
Re:GHC Parser Principles on Tuesday May 15, 2018 @04:30AM (#17072491)
I'm writing a Haskell compiler in C as a hobby. I didn't take a look at GHC code but now I find the way they deal with optional indentation interesting. Nonetheless I implemented the same thing in a simpler way having a function in my parser that checks for the presence or absence of curly braces and sets some state on the parser.

My implementation: https://github.com/angel-manuel/schc/blob/c1fa77b332a765b476...