Many osf.io features could be built on #atproto: your project repos would be hosted on your PDS (eg your bluesky acct). Institutions could host PDSs, distributing costs. Every record would have a unique id (analogous to a doi). Multiple apps could access the records in multiple ways @atproto.science
Brian Nosek
Over the next several months, we will phase out some popular OSF features. These changes do not affect current public content, which remains safe and accessible. We have prepared support material to help users adapt. I am very sorry for the disruption to your work. Please read this post for details.
Aug 11, 2026 at 7:28 PM
ATProto Apps with their own records as of 2025-11-20 - grouped by some general types - Hilary's Leaflet
This is not a comprehensive list but it is pretty thorough. There are at least 10 more I need to dig into and probably add here later today maybe. This does NOT include PDSs, Appviews, and clients. The goal was for it to be a list of apps that have their own records in the PDS.
ATProto Apps with their own records as of 2025-11-20 - grouped by some general types - Hilary's Leaflet
This is not a comprehensive list but it is pretty thorough. There are at least 10 more I need to dig into and probably add here later today maybe. This does NOT include PDSs, Appviews, and clients. The goal was for it to be a list of apps that have their own records in the PDS.
com.atproto.repo.listRecords | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
How do we talk about atproto to non-developers?
The beauty of AT Protocol is that all of your data from different apps is available on your PDS, your own folder on the internet containing your stuff as JSON. This means that you can switch which app you use to view that data, without losing anything. It also makes it very easy to make connections between data stored using different lexicons, or just display activity in one place. Sifa does a nice job of this on your profile page. For web developers, and people who understand webhosting, the concept is reasonably easy to understand. I know that any atproto app I join is going to store data in my PDS, any other people will be able to see it.
com.atproto.repo.createRecord | Bluesky
*This endpoint is part of the atproto PDS repository management APIs. Requests usually require authentication (unlike the `com.atproto.sync.*` endpoints), and are made directly to the user's own PDS instance.*
Deep Dive into Wafrn: How One Platform Self-Hosts Both ActivityPub and Bluesky Identities
Deep Dive into Wafrn: How One Platform Self-Hosts Both ActivityPub and Bluesky Identities 26 February 2026 ActivityPub ATproto self-hosting architecture A technical analysis of Wafrn's dual-protocol a...
Introducing Tap: Repository Synchronization Made Simple | Bluesky
Just about every app built on AT needs data from a repository at some point. For many use cases – feed generators, labelers, bots – streaming live data through a Relay or Jetstream works well. But some applications need to go beyond what Jetstream was designed for, like tracking specific subsets of a repo, automatically backfilling a database when adding new repos to monitor, or even mirroring the entire Atmosphere.
third-party apis: community infrastructure on atproto - Keith's Thoughts
you can just build things from an open set of tools
ATProto User Intents Demo
This is a demo tool which allows atproto accounts to configure a reuse declaration for their public data. You can read more about this atproo mechanism in the "User Intents for Data Reuse" proposal from March 2025. Any account in the atproto network (including Bluesky accounts) can use this tool via OAuth. The source code for this demo is linked above.
Exploring the idea of self-hosting a Bluesky PDS alongside my Indiekit instance — turning it into a dual-protocol server that federates over both ActivityPub and AT Protocol simultaneously. Inspired by Wafrn’s approach, adapted to Indiekit’s plugin architecture and Cloudron deployment. The goal: ow…
Ricardo Mendes
rmendes.netthe single most important part of atproto is the PDS as a user-controlled auth and storage layer to which clients can connect directly. death to appviews
Authenticated Transfer Enables Orchestration - nekomimi
blog.nekomimi.petI recently got super into the ATProto spec and how different services use PDS to store the data, I put together a quick client-only website that presents all those records in a single, consolidated feed of all my activity: at.diego.codes
at.diego.codes — Diego Vicente
at.diego.codesAre there any atproto apps that use records from competitors? This ecosystem won't feel open to me until @bsky.app uses something from outside the `app.bsky` namespace as part of its core experience
ATProto, Activitypub and FOSS applications
Two protocols, and an acronym. Directories, servers, services and tools that support one or more of these namesakes' or these namestakes' ideals [decentralized, federated etc]. Plus a few wikis for further reading.
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
A quick look at every link that's been added thus far.
Session | Send Messages, Not Metadata. | Private Messenger
NextGraph - Decentralized, encrypted and local-first platform and framework, towards the better internet we all deserve!
Freenet
Berty · Berty Technologies
p2panda
AT Protocol apps
Apps and services on ATProto (aside from Bluesky). See “AT Protocol” collection for links related to the protocol itself, as well as “Bluesky” for Bluesky clients etc.
import.py
Archivers AT
Brickster — Build anything, together.
BlueHarbor
Kimbia - A training journal that belongs to you.
Currents
ATLoop
Zeens — Photography, undiluted.
A Markdown Editor on AT Protocol — Diffdown
atmoBB Forums
Your files. Your account.
Home - Blacksky Cash
