Rashid Aziz: Extending ATproto for private data - ATProto Community
Bitesize Proto: Upserting ATProto Records - Hitchhiker's Guide to the Atmosphere
Tired of creating duplicate records in a repo from your atproto app?
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:
Towards Inserting One Billion Rows in SQLite Under A Minute - blag
This is a chronicle of my experiment where I set out to insert 1B rows in SQLite
A Full-Network Relay for $34 a Month | bryan newbold
This is an update to a Summer 2024 blog post. At the time, atproto relays required a cache of the full network on local disk to validate data structures. With the Sync v1.1 updates, relays don't need all that disk I/O. What impact does that have on hosting setup and operating costs? Turns out the d...
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
Imagine all the times you’ve downloaded a one-off app for a conference where you made all valuable connections with colleagues only to never use the app again. We could integrate the conference experience into your professional networks on the Atmosphere. ATproto can make networking so much better.
Ariel M. (she/her)
conferences conferences conferences cc @richferro.com @mariaa.bsky.social we deserve better than 2-star rating conference apps lmao
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.
Self-hosting your own atproto infrastructure is very much attainable and after going through the process, I wanted to do a little series of write ups on how to go about it. Starting with the PDS! jola.dev/posts/self-hosting-your-pds
Self-hosting your PDS
jola.devthe critical thing that got me on board with atproto is relays incrementalize sync of the entire dataset, which eliminates polling when crawling the old web is currently being crushed under crawler load and I don't think it's going away, so I think atproto is the only way to save the open web
I'm building on atproto because building infrastructure like "Drafts and Scheduled Posts for every atproto app" is easy as 1-2-3 and as cool as alf. Announcing alf, the atproto Latency Fabric: leaflet.pub/p/did:plc:3vdrgzr2zybocs45yfh…
a stuffed animal wearing sunglasses and a shirt is sitting at a keyboard .
media.tenor.com
