Someone recently announced a “restaurant listings/menus on atproto so they can own their own data”, and as someone who used to do engineering for OpenTable, let me tell you that project is not solving a problem that restaurants actually have. Owning your own data is an anti-value prop for many orgs.
dame
hard pill to swallow for atproto developers/creators: 99% of potential users either do not care about, value, understand, or want to “own their own data” i see so many apps/projects lead with this “value prop”, but it’s not an important or meaningful consideration for most people
Jul 30, 2026 at 4:49 PM
Plates · Your menu, everywhere
Publish your restaurant's menu once, as structured data you own. Plates gives it a beautiful page, and the open network carries it everywhere else.
Owning group data - meri's missives
Thinking about how communities can manage shared data on and off ATProto
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Permissioned Data Diary 5: What’s in a Name? - Daniel's Leaflets
In this permissioned data diary, we dive deep into the URI structure for permissioned data on atproto and use it to motivate a bunch of the larger design.
Rashid Aziz: Extending ATproto for private data - ATProto Community
From Attention to Intention - The Open Garden
Exploring business models for atproto and the open social web
Permissioned data on atproto — pick your depth
A private room in a place with no walls: how engineers are adding permissioned data to atproto. Read it plain-language or technical.
🪩 Introducing matadisco.org! — a way to discover open datasets via #atproto that doesn't depend on any single institution staying online. 🕺🏼 We have more public data than ever (satellite imagery, climate models, genomic sequences), but finding it is still painfully hard.
Matadisco — Decentralized Data Discovery
matadisco.orgEmerging from being "down in the technical weeds" of #atproto is a little mashup of @semble.so & WayFinder (wayfinders.network) Semble team released "open collections" this week - here we explore the "private & permissioned data" collection, created by @bmann.ca & now with 3 other contributors
This approach to a data commons could extend to so many typically shared things. For businesses to easily and authoritatively publish things like open hours or product catalogs, discographies, every kind of -ography... creative appmakers could do so much with all that
JB Hutch
Testing an idea that I've had for a while, but I think is even better suited for atproto Internet, meet plts.at
@masnick.com I’m listening to your interview with @reckless.bsky.social. This third party doctrine is interesting. Do you think that atproto data would be considered properly owned by the account individual? Would be interesting implications if that public data fall under search and seizure rights.
ATmospheric Apps
Things that use ATProto to create their own records (NOT Bluesky clients / Appviews)
import.py
Archivers AT
Brickster — Build anything, together.
BlueHarbor
Kimbia - A training journal that belongs to you.
Currents
