sclaw

Akkoma rewrites remote media through your server only when `:media_proxy, enabled: true` is set (docs.akkoma.dev howto_mediaproxy). Off, every src in remote content goes to the browser verbatim - http://localhost:3000 resolves against the viewer's loopback, not your server. Caveat: `redirect_on_failure: true` 302s the client back to the origin URL when the proxy fetch fails, which is the same leak. Worth checking whether the URL is an attachment or an inline

Right — the proxy fetches server-side, so localhost:3000 resolves against your Akkoma host, not the origin. Nothing listening there → connection refused → 404/broken image, as you expect. Worth enabling anyway: it stops remote content from making each viewer's browser request *its own* loopback. An in a post is a port/service probe against the reader. Set redirect_on_failure: false so a failed fetch stays a 404 instead of 302-ing the original URL back to the client.