







[MIRROR ONLY] A correct and efficient ATProto blob proxy for secure content delivery.
Blooym/porxie
[Mirror] A correct and efficient ATProto blob proxy for secure content delivery.
Porxie - a correct, fast ATProto blob proxy - Blooym
Building a self-hostable ATProto blob proxy for apps and communities, furthering the decentralised web.

tholian-network/stealth
:rocket: Stealth - Secure, Peer-to-Peer, Private and Automateable Web Browser/Scraper/Proxy
What is atproto?
What is atproto? atproto is two things: A protocol for creating open social networks An open social network atproto, the open social network Today the atproto network has 36+ million users and powers Bluesky and a handful of other apps. Almost all atproto data is public. Content like posts, likes, follows, and photos/videos are publicly accessible to any network participant in a permissionless way. As an example of how open the network is, here’s how easy it is to stream all public data on the network using a public atproto Relay like bsky.network:

Hey, I'm imgproxy!
Hey, I'm imgproxy—a fast and secure server for processing images!
Building More Resilient Local-First Software with atproto | jakelazaroff.com
atproto has the potential to become a rock-solid replacement for the most fragile part of any local-first app: the sync server.

About Atproto w/ Dan Abramov | Wireframe Live
About Atproto w/ Dan Abramov | Wireframe Live
An ATProto-aware blob proxy! What a sensational idea. github.com/Blooym/porxie
GitHub - Blooym/porxie: [Mirror] A correct and efficient ATProto blob proxy for secure content delivery.
github.comLyna
I'm now running a public instance of Porxie for anyone to use for within their application for evaluation purposes or as a replacement for Bluesky's CDN in the event of downtime or otherwise. 🦋 Bluesky CDN Compatible: porxie-bsky.dollware.net 🔗 General Purpose: porxie.dollware.net
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.com