Rate Limiting with NGINX – NGINX Community Blog
One of the most useful, but often misunderstood and misconfigured, features of NGINX is rate limiting. It allows you to limit the amount of HTTP requests a user can make in a given period of time. A request can be as simple as a GET request for the homepage of a website or a POST request on a log‑in form.
Pipedream MCP
Access MCP servers for more than 3,000 APIs with 10,000 prebuilt tools
Adversarial ATProto PDS Migration | Blog
An ATProto account lives on a Personal Data Server (PDS), and that service needs to be hosted somewhere by someone. There are a lot of options here, like a Raspberry Pi in your closet, a rented VPS in a datacentre, or a batteries-included service like bsky.social.
Question: For a service that generates blobs for a user, there’s a daily per-IP limit of 1000. What’s the best way to work around this limitation? I suppose each PDS operator adding that service’s IP address to the bypass list isn’t a viable option.
Sep 18, 2026 at 6:49 PM
random atproto sync notes - for whole-network backfill, you have to spread your `getRepo` requests across PDS hosts to get reasonable throughput, so it's a scheduling problem. it's also a spec-SHOULD to make these requests directly to your upstream (not PDSes directly) and follow its redirects.
Anyone else building on atproto hit the 1000-blobs/day-per-IP limit on uploadBlob? It's shared across all your users if your backend proxies uploads, so a few bulk imports on @currents.is ate up the whole quota and blocked unrelated users from saving images
Been thinking about how we could support access-controlled blobs in ATProtocol. Right now, all blobs are public - anyone can fetch them with a CID. But what if we could gate them? #atproto #atdev 🧵
private_blobs.md
gist.github.comupdate your PDS Operator 💞 latest version has support for multiple admins, rate limit alerts, and per user stats pages 🥰 maybe some other stuff too i can’t remember.
Brookie
PDS Operator it's a self hosted dashboard for your PDS. watches labelers and dms you when an account gets flagged. accounts, takedowns, pwd resets, invites, relay status, passkey sign-in, audit log, setup wizard with a qr code. deploy in minutes. tangled.org/brookie.blog/pds-operator
Am I missing something or is the Bluesky new-PDS daily relay limit for an _entire PDS_ lower than the limits they give to a _one single repo_ on their hosted PDSses? docs.bsky.app/docs/advanced-guides/rate-lim…
It's 100mb now in the reference PDS installer: github.com/bluesky-social/pds/blob/main/… Though each PDS may be configured with different limits, and I'm not sure if the actual limit is advertised anywhere.
