Article URL: https://mvakde.github.io/blog/44-on-arc-1/ Comments URL: https://news.ycombinator.com/item?id=49519939 Points: 16 # Comments: 2
This is an AI-generated summary. ShortSingh links to the original source for the complete article.
A developer has released x402-micro-tollgate, an open-source Express-based tool that acts as both an HTTP 402 reverse proxy and an MCP server. The project was built to enable per-call payments for existing HTTP APIs without distributing API keys. Ungated routes return a 402 Payment Required response, and requests are only forwarded to the upstream URL after payment is settled. The tool also exposes MCP tools, with some available for free and others requiring payment. It can be self-hosted via npx and is available on both GitHub and npm.
AnkiDroid, the open-source flashcard app for Android, has reported that Google Play is no longer permitting it to include a link to its Open Collective donation page within the app. The issue was flagged publicly on the AnkiDroid GitHub repository, indicating a policy enforcement action by Google. Open Collective is a platform commonly used by open-source projects to receive community funding transparently. Google Play's developer policies restrict certain external payment and donation links, which appears to be the basis for this removal. The situation raises concerns among open-source developers about their ability to solicit community support through mainstream app distribution platforms.
Proxies are critical tools in network infrastructure, but reverse and forward proxies serve fundamentally different purposes. A forward proxy sits between internal users and the internet, masking outbound requests and enabling compliance enforcement, content filtering, and IP rotation. A reverse proxy sits between external clients and backend servers, handling load balancing, SSL termination, caching, and API gateway functions. Choosing the wrong type can introduce bottlenecks, security gaps, or unnecessary infrastructure complexity. Cost structures also differ significantly, ranging from free self-hosted options like NGINX or Squid to enterprise cloud solutions charging per user, data volume, or concurrent connections.
A developer's website went offline for over eight hours after nginx failed to restart during a routine unattended Ubuntu upgrade. The upgrade included systemd itself, which triggered a brief self-reexecution that temporarily disrupted the local DNS resolver. During that window, nginx attempted a config test that required resolving a hardcoded upstream hostname, failed, and never came back up — even though the server hardware remained healthy throughout. The outage was only discovered when a syndication job flagged repeated 521 errors around 10:00, more than three hours after the site had gone down at 06:49. The fix involves using a nginx variable for the upstream hostname so DNS resolution is deferred to request time, limiting any future DNS failure to a single endpoint rather than the entire server.
Discussion (0)
Log in to join the discussion and vote.
Log in